From: <Tudor.Ambarus@microchip.com>
To: <mika.westerberg@linux.intel.com>, <michael@walle.cc>
Cc: <p.yadav@ti.com>, <miquel.raynal@bootlin.com>, <richard@nod.at>,
<vigneshr@ti.com>, <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] mtd: spi-nor: micron-st: Skip FSR reading if SPI controller does not support it
Date: Tue, 19 Jul 2022 08:55:13 +0000 [thread overview]
Message-ID: <8014065c-2c30-28cd-7f6c-0b9c76f39843@microchip.com> (raw)
In-Reply-To: <Yp4JNGvUzHIuYAHx@lahna>
On 6/6/22 17:03, Mika Westerberg wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Hi SPI-NOR maintainers,
Hi, Mika!
>
> On Mon, May 09, 2022 at 09:12:17AM +0200, Michael Walle wrote:
>> Am 2022-05-06 12:51, schrieb Mika Westerberg:
>>> 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).
>>>
>>> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>>
>> Reviewed-by: Michael Walle <michael@walle.cc>
>
> Gentle ping on this :)
Sorry, I was out of office most of this release cycle.
Looks good to me, I can queue it. But I see in other thread that you requested
to ignore it? Why's that?
https://patchwork.ozlabs.org/project/linux-mtd/patch/20220616121446.293408-1-oocheret@cisco.com/
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-07-19 8:55 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 [this message]
2022-07-19 9:27 ` Tudor Ambarus
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=8014065c-2c30-28cd-7f6c-0b9c76f39843@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).