[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZyCWNK_xMIsW4Ibq@gmail.com>
Date: Tue, 29 Oct 2024 09:00:52 +0100
From: Marcus Folkesson <marcus.folkesson@...il.com>
To: Tudor Ambarus <tudor.ambarus@...aro.org>
Cc: Pratyush Yadav <pratyush@...nel.org>, Michael Walle <mwalle@...nel.org>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Claudiu Beznea <claudiu.beznea@...on.dev>,
linux-mtd@...ts.infradead.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mtd: spi-nor: atmel: add at25sf321b entry
Hi Tudor,
On Tue, Oct 29, 2024 at 07:16:08AM +0000, Tudor Ambarus wrote:
>
>
> On 10/18/24 10:51 AM, Marcus Folkesson wrote:
> > Add entry for the at25sf321b 32Mbit SPI flash which is able to provide
> > SFDP information.
>
> then we could initialize the flash based on SFDP. If you don't need
> locking then probably you won't need a flash entry at all. See
> https://docs.kernel.org/driver-api/mtd/spi-nor.html
Hrmf. It seems like I have been looking into the wrong datasheet.
The actual device is at25sf321, not at25s321b, where the former can not
be identified using the SFDP table.
At25sf321 and at25s321b uses the same JEDEC ID though, probably what got
me wrong in the first place.
Please see page 10 in
https://www.renesas.cn/zh/document/apn/an201-adesto-32mbit-products-overview
for further reading.
I will send a v2 with updated details.
Best regards,
Marcus Folkesson
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists