From: <Tudor.Ambarus@microchip.com>
To: <michael@walle.cc>
Cc: vigneshr@ti.com, richard@nod.at, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, miquel.raynal@bootlin.com
Subject: Re: [PATCH] mtd: spi-nor: Add support for at25sl321
Date: Sun, 19 Jan 2020 07:18:29 +0000 [thread overview]
Message-ID: <2121499.oPre2Eb8Qh@192.168.0.113> (raw)
In-Reply-To: <20200116160209.20129-1-michael@walle.cc>
On Thursday, January 16, 2020 6:02:09 PM EET Michael Walle wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> This was tested in single, dual and quad mode on a custom board with the
> NXP FlexSPI controller.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> drivers/mtd/spi-nor/spi-nor.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
> index 8226d6450069..94747059344a 100644
> --- a/drivers/mtd/spi-nor/spi-nor.c
> +++ b/drivers/mtd/spi-nor/spi-nor.c
> @@ -2332,6 +2332,12 @@ static const struct flash_info spi_nor_ids[] = {
>
> { "at45db081d", INFO(0x1f2500, 0, 64 * 1024, 16, SECT_4K) },
>
> + /* Adesto (former Atmel) */
All the atmel flashes from above start with Adesto's manufacturer id, 0x1f.
I dropped this comment, ordered the entry alphabetically and applied to spi-
nor/next. Thanks.
ta
> + {
> + "at25sl321", INFO(0x1f4216, 0, 64 * 1024, 64,
> + SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ)
> + },
> +
> /* EON -- en25xxx */
> { "en25f32", INFO(0x1c3116, 0, 64 * 1024, 64, SECT_4K) },
> { "en25p32", INFO(0x1c2016, 0, 64 * 1024, 64, 0) },
> --
> 2.20.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2020-01-19 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 16:02 [PATCH] mtd: spi-nor: Add support for at25sl321 Michael Walle
2020-01-19 7:18 ` Tudor.Ambarus [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=2121499.oPre2Eb8Qh@192.168.0.113 \
--to=tudor.ambarus@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--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).