From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Marcus Folkesson <marcus.folkesson@gmail.com>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <mwalle@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>
Cc: linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: spi-nor: atmel: add at25sf321b entry
Date: Tue, 29 Oct 2024 07:16:08 +0000 [thread overview]
Message-ID: <239d2425-52f6-4deb-964e-e22d1a1f6637@linaro.org> (raw)
In-Reply-To: <20241018-spi-nor-v1-1-d725bfb701ec@gmail.com>
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
>
> Link:
> https://www.renesas.com/en/document/dst/at25sf321b-datasheet?r=1608806
>
> Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
> ---
> drivers/mtd/spi-nor/atmel.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/mtd/spi-nor/atmel.c b/drivers/mtd/spi-nor/atmel.c
> index 45d1153a04a07b7c61f46b117311b24ab695038f..e635559711a4b402d23d49da93efc15e6be571dd 100644
> --- a/drivers/mtd/spi-nor/atmel.c
> +++ b/drivers/mtd/spi-nor/atmel.c
> @@ -238,6 +238,12 @@ static const struct flash_info atmel_nor_parts[] = {
> .flags = SPI_NOR_HAS_LOCK,
> .no_sfdp_flags = SECT_4K,
> .fixups = &at25fs_nor_fixups
> + }, {
> + .id = SNOR_ID(0x1f, 0x87, 0x01),
> + .name = "at25sf321b",
> + .size = SZ_4M,
> + .flags = SPI_NOR_HAS_LOCK,
> + .no_sfdp_flags = SECT_4K,
> },
> };
>
>
> ---
> base-commit: 200289db261f0c8131a5756133e9d30966289c3b
> change-id: 20241018-spi-nor-dc29698dea0f
>
> Best regards,
next prev parent reply other threads:[~2024-10-29 7:23 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 [this message]
2024-10-29 8:00 ` Marcus Folkesson
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=239d2425-52f6-4deb-964e-e22d1a1f6637@linaro.org \
--to=tudor.ambarus@linaro.org \
--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=marcus.folkesson@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pratyush@kernel.org \
--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).