From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: <mika.westerberg@linux.intel.com>
Cc: Tudor Ambarus <tudor.ambarus@microchip.com>, <michael@walle.cc>,
<richard@nod.at>, <miquel.raynal@bootlin.com>,
<linux-mtd@lists.infradead.org>, <vigneshr@ti.com>,
<p.yadav@ti.com>
Subject: Re: [PATCH] mtd: spi-nor: micron-st: Skip FSR reading if SPI controller does not support it
Date: Tue, 19 Jul 2022 12:27:39 +0300 [thread overview]
Message-ID: <165822280254.54276.15501031299133900909.b4-ty@microchip.com> (raw)
In-Reply-To: <20220506105158.43613-1-mika.westerberg@linux.intel.com>
On Fri, 6 May 2022 13:51:58 +0300, Mika Westerberg wrote:
> The Intel SPI controller does not support low level operations, like
> reading the flag status register (FSR). It only exposes a set of high
> level operations for software to use. For this reason check the return
> value of micron_st_nor_read_fsr() and if the operation was not
> supported, use the status register value only. This allows the chip to
> work even when attached to Intel SPI controller (there are such systems
> out there).
>
> [...]
Applied to spi-nor/next, thanks!
[1/1] mtd: spi-nor: micron-st: Skip FSR reading if SPI controller does not support it
https://git.kernel.org/mtd/c/90c517f435a9
Best regards,
--
Tudor Ambarus <tudor.ambarus@microchip.com>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2022-07-19 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 10:51 [PATCH] mtd: spi-nor: micron-st: Skip FSR reading if SPI controller does not support it Mika Westerberg
2022-05-09 7:12 ` Michael Walle
2022-06-06 14:03 ` Mika Westerberg
2022-07-19 8:55 ` Tudor.Ambarus
2022-07-19 9:27 ` Tudor Ambarus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=165822280254.54276.15501031299133900909.b4-ty@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=mika.westerberg@linux.intel.com \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).