From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Michael Walle <mwalle@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Richard Weinberger <richard@nod.at>,
linux-kernel@vger.kernel.org,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Pratyush Yadav <pratyush@kernel.org>
Subject: Re: [PATCH] mtd: spi-nor: atmel: add at25sf321b entry
Date: Tue, 29 Oct 2024 09:00:52 +0100 [thread overview]
Message-ID: <ZyCWNK_xMIsW4Ibq@gmail.com> (raw)
In-Reply-To: <239d2425-52f6-4deb-964e-e22d1a1f6637@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-10-29 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 9:51 [PATCH] mtd: spi-nor: atmel: add at25sf321b entry Marcus Folkesson
2024-10-29 7:16 ` Tudor Ambarus
2024-10-29 8:00 ` Marcus Folkesson [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=ZyCWNK_xMIsW4Ibq@gmail.com \
--to=marcus.folkesson@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@linaro.org \
--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).