From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Michael Walle" <mwalle@kernel.org>
Cc: "Pratyush Yadav" <pratyush@kernel.org>,
"Takahiro Kuwano" <takahiro.kuwano@infineon.com>,
"Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Steam Lin" <STLin2@winbond.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/30] mtd: spi-nor: Clean Winbond W25QxxJV family
Date: Wed, 22 Jul 2026 14:45:58 +0200 [thread overview]
Message-ID: <87ecgvjipl.fsf@bootlin.com> (raw)
In-Reply-To: <DJRK4HNYJ2LP.KDV5AMR7FCE4@kernel.org> (Michael Walle's message of "Mon, 06 Jul 2026 16:27:33 +0200")
Hello Michael,
On 06/07/2026 at 16:27:33 +02, "Michael Walle" <mwalle@kernel.org> wrote:
> On Fri May 29, 2026 at 5:22 PM CEST, Miquel Raynal wrote:
>> Thanks to Winbond collaboration, I was able to test almost the entire JV
>> SPI NOR family. A few chips could not be sourced, I decided to apply the
>> very same logic than the other chips, all of them behave identically as
>> shown in all the logs that I am sharing in each and every commit.
>>
>> This series is pretty straightforward, it is here to cleanup the JV
>> entries by:
>> - Removing the useless part names (which are going to become a problem)
>> - Aligning the comments and "fixing" the chip names in them
>> - Reordering the chips by density and family
>> - Testing and showing all the SFDP content and passing all the SPI NOR
>> tests to ensure a good level of support.
>> - Describing only what needs to be described, parsing the SFDP tables
>> otherwise.
>> - Adding all the locking information when it is missing.
>>
>> This work is necessary because I am about to propose the addition of the
>> W25QxxRV family, whose IDs actually collide with the JV chips. The chips
>> are similar, they have been "improved" (especially the silicon/engraving
>> smoothness) and we have a way to differentiate them based on their SFDP
>> content, but that will be for a following series.
>
> Why do you need to remove the no_sfdp_flags? I have only looked at
> some of the patches, but overall it seems we'd be dropping support
> for older chips - which we don't know if they are in use or not.
>
> So although the comment might only point to one chip, there can be
> many more with that very same id. And now.. with the RV family even
> more. Ugh.
I wanted to follow the spi-nor direction which-nor was to move away from
these, when they were relevant. But you are right, I gathered more
information, Winbond has transitioned to SFDP between 2012 and 2016, no
chip without SFDP has been manufactured for more than a decade. I guess
it is still possible to find chips with no SFDP support then.
Since removing the no_sfdp_flags field would mean dropping support for
those old chips, I guess we are stuck with this data. At this point, I
do not identify problems with keeping the no_sfdp data and adding
support for the RV chips.
However I will keep removing the names, which get wrong-er and
wrong-er...
Thanks,
Miquèl
prev parent reply other threads:[~2026-07-22 12:46 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 15:22 [PATCH 00/30] mtd: spi-nor: Clean Winbond W25QxxJV family Miquel Raynal
2026-05-29 15:22 ` [PATCH 01/30] mtd: spi-nor: winbond: Move W25Q01NW to its right place Miquel Raynal
2026-07-06 13:54 ` Michael Walle
2026-05-29 15:22 ` [PATCH 02/30] mtd: spi-nor: winbond: Normalize names Miquel Raynal
2026-07-06 13:57 ` Michael Walle
2026-07-22 12:52 ` Miquel Raynal
2026-07-22 13:07 ` Michael Walle
2026-07-22 15:19 ` Miquel Raynal
2026-05-29 15:22 ` [PATCH 03/30] mtd: spi-nor: winbond: Stop filling the .name entry Miquel Raynal
2026-07-06 13:59 ` Michael Walle
2026-07-22 12:56 ` Miquel Raynal
2026-07-22 13:23 ` Michael Walle
2026-07-22 15:51 ` Miquel Raynal
2026-05-29 15:22 ` [PATCH 04/30] mtd: spi-nor: winbond: Make the RDCR fixup Winbond wide Miquel Raynal
2026-07-06 14:11 ` Michael Walle
2026-05-29 15:22 ` [PATCH 05/30] mtd: spi-nor: winbond: W25Q32JV-Q/N: Drop redundant data Miquel Raynal
2026-07-06 14:13 ` Michael Walle
2026-07-22 13:00 ` Miquel Raynal
2026-05-29 15:22 ` [PATCH 06/30] mtd: spi-nor: winbond: W25Q64JV-Q/N: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 07/30] mtd: spi-nor: winbond: W25Q512JV-Q/N: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 08/30] mtd: spi-nor: winbond: W25Q32JV-Q/N: Add quad page program capability Miquel Raynal
2026-07-06 14:16 ` Michael Walle
2026-07-22 13:01 ` Miquel Raynal
2026-05-29 15:22 ` [PATCH 09/30] mtd: spi-nor: winbond: W25Q64JV-Q/N: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 10/30] mtd: spi-nor: winbond: W25Q128JV-Q/N: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 11/30] mtd: spi-nor: winbond: W25Q32JV-Q/N: Fill locking information Miquel Raynal
2026-07-06 14:21 ` Michael Walle
2026-07-22 15:00 ` Miquel Raynal
2026-05-29 15:22 ` [PATCH 12/30] mtd: spi-nor: winbond: W25Q64JV-Q/N: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 13/30] mtd: spi-nor: winbond: W25Q128JV-Q/N: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 14/30] mtd: spi-nor: winbond: W25Q512JV-Q/N: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 15/30] mtd: spi-nor: winbond: W25Q01JV-Q/N: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 16/30] mtd: spi-nor: winbond: W25Q32JV-M: Drop redundant data Miquel Raynal
2026-07-06 14:23 ` Michael Walle
2026-07-22 15:09 ` Miquel Raynal
2026-05-29 15:22 ` [PATCH 17/30] mtd: spi-nor: winbond: W25Q64JV-M: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 18/30] mtd: spi-nor: winbond: W25Q128JV-M: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 19/30] mtd: spi-nor: winbond: W25Q32JV-M: Add quad page program capability Miquel Raynal
2026-05-29 15:22 ` [PATCH 20/30] mtd: spi-nor: winbond: W25Q64JV-M: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 21/30] mtd: spi-nor: winbond: W25Q128JV-M: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 22/30] mtd: spi-nor: winbond: W25Q32JV-M: Fill locking information Miquel Raynal
2026-05-29 15:22 ` [PATCH 23/30] mtd: spi-nor: winbond: W25Q64JV-M: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 24/30] mtd: spi-nor: winbond: W25Q128JV-M: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 25/30] mtd: spi-nor: winbond: W25Q02JV-M: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 26/30] mtd: spi-nor: winbond: W25Q512JV-M: New chip Miquel Raynal
2026-05-29 15:22 ` [PATCH 27/30] mtd: spi-nor: winbond: W25Q01JV-M: " Miquel Raynal
2026-05-29 15:22 ` [PATCH 28/30] mtd: spi-nor: winbond: W25QxxJV-Q/N/M: Drop redundant data Miquel Raynal
2026-05-29 15:22 ` [PATCH 29/30] mtd: spi-nor: winbond: W25QxxJV-Q/N/M: Add quad page program capability Miquel Raynal
2026-05-29 15:22 ` [PATCH 30/30] mtd: spi-nor: winbond: W25QxxJV-Q/N/M: Fill locking information Miquel Raynal
2026-07-06 14:27 ` [PATCH 00/30] mtd: spi-nor: Clean Winbond W25QxxJV family Michael Walle
2026-07-22 12:45 ` Miquel Raynal [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=87ecgvjipl.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=STLin2@winbond.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=takahiro.kuwano@infineon.com \
--cc=thomas.petazzoni@bootlin.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