From: <Tudor.Ambarus@microchip.com>
To: <linux-mtd@lists.infradead.org>
Cc: <michael@walle.cc>, <linux-kernel@vger.kernel.org>,
<richard@nod.at>, <vigneshr@ti.com>, <miquel.raynal@bootlin.com>
Subject: Re: [PATCH] mtd: spi-nor: Add support for w25qNNjwim
Date: Sat, 11 Jan 2020 14:19:19 +0000 [thread overview]
Message-ID: <12341010.b9DRC5f9X7@192.168.0.113> (raw)
In-Reply-To: <20200103223423.14025-1-michael@walle.cc>
Hi, Michael,
On Saturday, January 4, 2020 12:34:23 AM EET Michael Walle wrote:
> Add support for the Winbond W25QnnJW-IM flashes. These have a
> programmable QE bit. There are also the W25QnnJW-IQ variant which shares
> the ID with the W25QnnFW parts. These have the QE bit hard strapped to
> 1, thus don't support hardware write protection.
There are few flavors of hw write protection supported by this flash, the Q
version does not disable them all. How about saying just that the /HOLD
function is disabled?
When we receive new flash id patches, we ask the contributors to specify if
they test the flash, in which modes (single, quad), and with which controller.
Ideally all the flash's flags should be tested, but there are cases in which
the controllers do not support quad read for example, and we accept the
patches even if tested in single read mode. SPI_NOR_HAS_LOCK and
SPI_NOR_HAS_TB must be tested as well.
Even if the patches are rather simple, we ask for this to be sure that we
don't add a flash that is broken from day one. So, would you please tell us
what flashes did you test, what flags, and with which controller?
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> drivers/mtd/spi-nor/spi-nor.c | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
> index addb6319fcbb..3fa8a81bdab0 100644
> --- a/drivers/mtd/spi-nor/spi-nor.c
> +++ b/drivers/mtd/spi-nor/spi-nor.c
> @@ -2627,6 +2627,11 @@ static const struct flash_info spi_nor_ids[] = {
> SECT_4K | SPI_NOR_DUAL_READ |
SPI_NOR_QUAD_READ |
> SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB)
> },
> + {
> + "w25q16jwim", INFO(0xef8015, 0, 64 * 1024, 32,
"i" is for the temperature range, which is not a fixed characteristic. Usually
there are flashes with the same jedec-id, but with different temperature
ranges. Let's drop the "i" and rename it to "w25q16jwm"
Cheers,
ta
next prev parent reply other threads:[~2020-01-11 14:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 22:34 [PATCH] mtd: spi-nor: Add support for w25qNNjwim Michael Walle
2020-01-11 14:19 ` Tudor.Ambarus [this message]
2020-01-11 23:16 ` Michael Walle
2020-01-13 9:06 ` Tudor.Ambarus
2020-01-13 10:07 ` Michael Walle
2020-01-13 13:15 ` Michael Walle
2020-01-19 7:13 ` Tudor.Ambarus
2020-01-19 22:24 ` Michael Walle
2020-01-20 11:03 ` Tudor.Ambarus
2020-01-20 15:55 ` Michael Walle
2020-01-21 18:40 ` Tudor.Ambarus
2020-01-21 23:28 ` Michael Walle
2020-01-22 6:48 ` Tudor.Ambarus
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=12341010.b9DRC5f9X7@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