drivers/mtd/spi-nor/winbond.c | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+)
Here is a series adding support for 6 Winbond SPI NOR chips. Describing
these chips is needed otherwise the block protection feature is not
available. Everything else looks fine otherwise.
In practice I am only adding 6 very similar IDs but I split the commits
because the amount of meta data to show proof that all the chips have
been tested and work is pretty big.
As the commits simply add an ID, I am Cc'ing stable with the hope to
get these backported to LTS kernels as allowed by the stable rules (see
link below, but I hope I am doing this right).
Link: https://elixir.bootlin.com/linux/v6.17.7/source/Documentation/process/stable-kernel-rules.rst#L15
Thanks,
Miquèl
---
Miquel Raynal (6):
mtd: spi-nor: winbond: Add support for W25Q01NWxxIQ chips
mtd: spi-nor: winbond: Add support for W25Q01NWxxIM chips
mtd: spi-nor: winbond: Add support for W25Q02NWxxIM chips
mtd: spi-nor: winbond: Add support for W25H512NWxxAM chips
mtd: spi-nor: winbond: Add support for W25H01NWxxAM chips
mtd: spi-nor: winbond: Add support for W25H02NWxxAM chips
drivers/mtd/spi-nor/winbond.c | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
---
base-commit: 479ba7fc704936b74a91ee352fe113d6391d562f
change-id: 20251105-winbond-v6-18-rc1-spi-nor-7f78cb2785d6
Best regards,
--
Miquel Raynal <miquel.raynal@bootlin.com>
On Wed, Nov 05 2025, Miquel Raynal wrote: > Here is a series adding support for 6 Winbond SPI NOR chips. Describing > these chips is needed otherwise the block protection feature is not > available. Everything else looks fine otherwise. > > In practice I am only adding 6 very similar IDs but I split the commits > because the amount of meta data to show proof that all the chips have > been tested and work is pretty big. > > As the commits simply add an ID, I am Cc'ing stable with the hope to > get these backported to LTS kernels as allowed by the stable rules (see > link below, but I hope I am doing this right). > > Link: https://elixir.bootlin.com/linux/v6.17.7/source/Documentation/process/stable-kernel-rules.rst#L15 > > Thanks, > Miquèl > > --- > Miquel Raynal (6): > mtd: spi-nor: winbond: Add support for W25Q01NWxxIQ chips > mtd: spi-nor: winbond: Add support for W25Q01NWxxIM chips > mtd: spi-nor: winbond: Add support for W25Q02NWxxIM chips > mtd: spi-nor: winbond: Add support for W25H512NWxxAM chips > mtd: spi-nor: winbond: Add support for W25H01NWxxAM chips > mtd: spi-nor: winbond: Add support for W25H02NWxxAM chips > > drivers/mtd/spi-nor/winbond.c | 24 ++++++++++++++++++++++++ > 1 file changed, 24 insertions(+) > --- > base-commit: 479ba7fc704936b74a91ee352fe113d6391d562f > change-id: 20251105-winbond-v6-18-rc1-spi-nor-7f78cb2785d6 > > Best regards, Applied to spi-nor/next. Thanks! -- Regards, Pratyush Yadav
On Wed Nov 5, 2025 at 6:26 PM CET, Miquel Raynal wrote: > Here is a series adding support for 6 Winbond SPI NOR chips. Describing > these chips is needed otherwise the block protection feature is not > available. Everything else looks fine otherwise. > > In practice I am only adding 6 very similar IDs but I split the commits > because the amount of meta data to show proof that all the chips have > been tested and work is pretty big. > > As the commits simply add an ID, I am Cc'ing stable with the hope to > get these backported to LTS kernels as allowed by the stable rules (see > link below, but I hope I am doing this right). > > Link: https://elixir.bootlin.com/linux/v6.17.7/source/Documentation/process/stable-kernel-rules.rst#L15 > > Thanks, > Miquèl > > --- > Miquel Raynal (6): > mtd: spi-nor: winbond: Add support for W25Q01NWxxIQ chips > mtd: spi-nor: winbond: Add support for W25Q01NWxxIM chips > mtd: spi-nor: winbond: Add support for W25Q02NWxxIM chips > mtd: spi-nor: winbond: Add support for W25H512NWxxAM chips > mtd: spi-nor: winbond: Add support for W25H01NWxxAM chips > mtd: spi-nor: winbond: Add support for W25H02NWxxAM chips Nice, for the whole series: Reviewed-by: Michael Walle <mwalle@kernel.org> -michael
Hello, On 05/11/2025 at 18:26:59 +01, Miquel Raynal <miquel.raynal@bootlin.com> wrote: > Here is a series adding support for 6 Winbond SPI NOR chips. Describing > these chips is needed otherwise the block protection feature is not > available. Everything else looks fine otherwise. [...] Sorry for messing up a bit the cover letter, I didn't pay enough attention my first line got taken by b4 as Subject and forgot to put a real title. Subject should have been: "mtd: spi-nor: winbond: Support for chips with block protection capabilities" This will be fixed in case we need a v2. Cheers, Miquèl
Hi, Miquel, On 11/5/25 7:26 PM, Miquel Raynal wrote: > Here is a series adding support for 6 Winbond SPI NOR chips. Describing > these chips is needed otherwise the block protection feature is not > available. Everything else looks fine otherwise. I'm glad to see this, you're an locking expert now :). Do you care to extend the SPI NOR testing requirements [1] with steps on how to test the locking? There's some testing proposed at [2], would you please check and review it? Thanks! ta [1] https://docs.kernel.org/driver-api/mtd/spi-nor.html#minimum-testing-requirements [2] https://lore.kernel.org/linux-mtd/92e99a96-5582-48a5-a4f9-e9b33fcff171@linux.dev/
On 10/11/2025 at 08:54:24 +02, Tudor Ambarus <tudor.ambarus@linaro.org> wrote: > Hi, Miquel, > > On 11/5/25 7:26 PM, Miquel Raynal wrote: >> Here is a series adding support for 6 Winbond SPI NOR chips. Describing >> these chips is needed otherwise the block protection feature is not >> available. Everything else looks fine otherwise. > > I'm glad to see this, you're an locking expert now :). Do you care to > extend the SPI NOR testing requirements [1] with steps on how to test the > locking? There's some testing proposed at [2], would you please check and > review it? Good idea. Let me have a loot at what Sean proposed. > [1] https://docs.kernel.org/driver-api/mtd/spi-nor.html#minimum-testing-requirements > [2] https://lore.kernel.org/linux-mtd/92e99a96-5582-48a5-a4f9-e9b33fcff171@linux.dev/ Thanks, Miquèl
On 11/12/25 11:35 AM, Miquel Raynal wrote: > On 10/11/2025 at 08:54:24 +02, Tudor Ambarus <tudor.ambarus@linaro.org> wrote: > >> Hi, Miquel, >> >> On 11/5/25 7:26 PM, Miquel Raynal wrote: >>> Here is a series adding support for 6 Winbond SPI NOR chips. Describing >>> these chips is needed otherwise the block protection feature is not >>> available. Everything else looks fine otherwise. >> >> I'm glad to see this, you're an locking expert now :). Do you care to >> extend the SPI NOR testing requirements [1] with steps on how to test the >> locking? There's some testing proposed at [2], would you please check and >> review it? > > Good idea. Let me have a loot at what Sean proposed. I proposed to him as well to update the testing requirements if he cares, he said he'll take a look. Sync with him please. Cheers, ta > >> [1] https://docs.kernel.org/driver-api/mtd/spi-nor.html#minimum-testing-requirements >> [2] https://lore.kernel.org/linux-mtd/92e99a96-5582-48a5-a4f9-e9b33fcff171@linux.dev/ > > Thanks, > Miquèl
Hello, >>>> Here is a series adding support for 6 Winbond SPI NOR chips. Describing >>>> these chips is needed otherwise the block protection feature is not >>>> available. Everything else looks fine otherwise. >>> >>> I'm glad to see this, you're an locking expert now :). Do you care to >>> extend the SPI NOR testing requirements [1] with steps on how to test the >>> locking? There's some testing proposed at [2], would you please check and >>> review it? >> >> Good idea. Let me have a loot at what Sean proposed. > > I proposed to him as well to update the testing requirements if he cares, > he said he'll take a look. Sync with him please. > > Cheers, > ta > >> >>> [1] https://docs.kernel.org/driver-api/mtd/spi-nor.html#minimum-testing-requirements >>> [2] https://lore.kernel.org/linux-mtd/92e99a96-5582-48a5-a4f9-e9b33fcff171@linux.dev/ For people who would like to follow, the proposal is here: https://lore.kernel.org/linux-mtd/20251114-winbond-v6-18-rc1-spi-nor-swp-v1-0-487bc7129931@bootlin.com/T/#mbae8b874181eb0401b30142f423b73b6389a0c54 Thanks, Miquèl
© 2016 - 2025 Red Hat, Inc.