From: Michael Walle <michael@walle.cc>
To: chf.fritz@googlemail.com
Cc: Tudor Ambarus <tudor.ambarus@microchip.com>,
Pratyush Yadav <p.yadav@ti.com>,
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>,
ClaudiuBeznea <claudiu.beznea@microchip.com>,
linux-mtd@lists.infradead.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: spi-nor: atmel: Add at25ql641 support
Date: Wed, 25 May 2022 00:37:16 +0200 [thread overview]
Message-ID: <0123ee0e70df13b340230a38cb44548f@walle.cc> (raw)
In-Reply-To: <48b49de3712267780916b665d3b2a3323e6f10ce.camel@googlemail.com>
Hi,
Am 2022-05-24 21:20, schrieb Christoph Fritz:
> This patch adds AT25QL641 to the list of supported nor flashs.
Please mention on which spi host controller this flash was
tested.
> Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
> ---
> drivers/mtd/spi-nor/atmel.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/mtd/spi-nor/atmel.c b/drivers/mtd/spi-nor/atmel.c
> index 656dd80a0be7..dfbc12071093 100644
> --- a/drivers/mtd/spi-nor/atmel.c
> +++ b/drivers/mtd/spi-nor/atmel.c
> @@ -186,6 +186,8 @@ static const struct flash_info atmel_nor_parts[] =
> {
> .fixups = &atmel_nor_global_protection_fixups },
> { "at25sl321", INFO(0x1f4216, 0, 64 * 1024, 64)
> NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
> + { "at25ql641", INFO(0x1f4317, 0, 64 * 1024, 128)
> + NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
This flash supports SFDP, please use either SNOR_ID3() (you'll
have to pick my pending patches first [1]) or use
{ "at25ql641", INFO(0x1f4317, 0, 0, 0) PARSE_SFDP },
which will then be replaced with SNOR_ID3() once it is available.
> { "at26f004", INFO(0x1f0400, 0, 64 * 1024, 8)
> NO_SFDP_FLAGS(SECT_4K) },
> { "at26df081a", INFO(0x1f4501, 0, 64 * 1024, 16)
-michael
[1] https://lore.kernel.org/r/966de7ad5f563f9a29db91c5309a71c6@walle.cc/
prev parent reply other threads:[~2022-05-24 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 19:20 Christoph Fritz
2022-05-24 22:37 ` Michael Walle [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=0123ee0e70df13b340230a38cb44548f@walle.cc \
--to=michael@walle.cc \
--cc=alexandre.belloni@bootlin.com \
--cc=chf.fritz@googlemail.com \
--cc=claudiu.beznea@microchip.com \
--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=nicolas.ferre@microchip.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--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
all inboxes | Powered by JetHome®