[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d87bf780-f728-e2e0-be6a-1731fddd32c9@microchip.com>
Date: Mon, 5 Aug 2019 07:32:09 +0000
From: <Tudor.Ambarus@...rochip.com>
To: <vigneshr@...com>, <boris.brezillon@...labora.com>,
<marek.vasut@...il.com>
CC: <dwmw2@...radead.org>, <computersforpeace@...il.com>,
<miquel.raynal@...tlin.com>, <richard@....at>,
<linux-mtd@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<boris.brezillon@...tlin.com>
Subject: Re: [PATCH 6/6] mtd: spi-nor: Add the SPI_NOR_XSR_RDY flag
On 08/05/2019 08:14 AM, Vignesh Raghavendra wrote:
> External E-Mail
>
>
>
> On 31/07/19 2:42 PM, Tudor.Ambarus@...rochip.com wrote:
>> From: Boris Brezillon <boris.brezillon@...tlin.com>
>>
>> S3AN flashes use a specific opcode to read the status register.
>> We currently use the SPI_S3AN flag to decide whether this specific
>> SR read opcode should be used, but SPI_S3AN is about to disappear, so
>> let's add a new flag.
>>
>
> I think you can drop SPI_S3AN right away either as separate patch in
> this series or as part of this patch itself.
>
SPI_NOR_XSR_RDY is more generic than SPI_S3AN, and lets other flashes use
SPINOR_OP_XRDSR SR read opcode if needed.
If I drop SPI_S3AN now, I'll have to select the s3an_nor_setup() method based on
SPI_NOR_XSR_RDY/SNOR_F_READY_XSR_RDY which might not be correct. There might be
flashes that use SPINOR_OP_XRDSR but have a different setup call.
Of course there are a lot of "might" here (because I couldn't find some other
NORs that use this opcode), and if you have a strong opinion I can change as you
suggested. I prefer to drop SPI_S3AN when moving the xillinx bits out of the
core, as in https://patchwork.ozlabs.org/patch/1009295/.
Cheers,
ta
Powered by blists - more mailing lists