From: "Nuno Sá" <nuno.sa@analog.com>
To: Michael Walle <mwalle@kernel.org>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Pratyush Yadav <pratyush@kernel.org>,
Takahiro Kuwano <takahiro.kuwano@infineon.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH 2/2] mtd: spi-nor: issi: Add support for is25wx01g
Date: Mon, 14 Sep 2026 09:20:56 +0100 [thread overview]
Message-ID: <aqetgODkt3MhNndd@nsa> (raw)
In-Reply-To: <DLETRRVRUWEP.1VU1EHARD3MSH@kernel.org>
On Mon, Sep 14, 2026 at 08:28:25AM +0200, Michael Walle wrote:
> Hi,
>
> On Fri Sep 11, 2026 at 5:36 PM CEST, Nuno Sá wrote:
> > Add support for the ISSI IS25WX01G, a 1 Gbit octal NOR flash. The part
> > is fully described by SFDP, so only the flash ID and two BFPT fixups are
> > needed.
>
> Adding a new flash involves minimum testing and an SFDP dump, see
> [1].
>
> Also please keep the following Link: tag in your next version:
>
> Link: https://www.issi.com/WW/pdf/25LX-WX01GB.pdf
>
> > The flash has no Status Register 2 and does not implement the 35h Read
> > Configuration Register command, so the default assumption of a 16-bit
> > Write Status command does not hold. Additionally, its BFPT Quad Enable
> > Requirement field carries a reserved value, which makes
> > spi_nor_parse_bfpt() keep the manufacturer default quad enable method;
> > clear it, since this is an octal-only part with no quad mode at all.
> >
> > Signed-off-by: Nuno Sá <nuno.sa@analog.com>
> > ---
> > drivers/mtd/spi-nor/issi.c | 27 +++++++++++++++++++++++++++
> > 1 file changed, 27 insertions(+)
> >
> > diff --git a/drivers/mtd/spi-nor/issi.c b/drivers/mtd/spi-nor/issi.c
> > index 2f057d731df2..aac9d19b90fc 100644
> > --- a/drivers/mtd/spi-nor/issi.c
> > +++ b/drivers/mtd/spi-nor/issi.c
> > @@ -29,6 +29,29 @@ static const struct spi_nor_fixups is25lp256_fixups = {
> > .post_bfpt = is25lp256_post_bfpt_fixups,
> > };
> >
> > +static int is25wx01g_post_bfpt_fixups(struct spi_nor *nor,
> > + const struct sfdp_parameter_header *bfpt_header,
> > + const struct sfdp_bfpt *bfpt)
> > +{
> > + /*
> > + * There is no Status Register 2 and no 35h command. And WRITE STATUS
> > + * REGISTER takes a single data byte.
> > + */
> > + nor->flags &= ~SNOR_F_HAS_16BIT_SR;
> > +
> > + /*
> > + * The BFPT Quad Enable Requirement field is set to a reserved value, so
> > + * spi_nor_parse_bfpt() leaves the quad enable method at its default.
> > + * Make sure we disable it as there is no quad mode anyway.
> > + */
> > + nor->params->quad_enable = NULL;
> > + return 0;
> > +}
> > +
> > +static const struct spi_nor_fixups is25wx01g_fixups = {
> > + .post_bfpt = is25wx01g_post_bfpt_fixups,
> > +};
> > +
> > static int pm25lv_nor_late_init(struct spi_nor *nor)
> > {
> > struct spi_nor_erase_map *map = &nor->params->erase_map;
> > @@ -120,6 +143,10 @@ static const struct flash_info issi_nor_parts[] = {
> > .id = SNOR_ID(0x9d, 0x70, 0x19),
> > .name = "is25wp256",
> > .flags = SPI_NOR_QUAD_PP,
> > + }, {
> > + .id = SNOR_ID(0x9d, 0x5b, 0x1b),
> > + .name = "is25wx01g",
> No .name please.
Yes! I realize now it's obsolete.
>
> -michael
>
> [1] https://docs.kernel.org/driver-api/mtd/spi-nor.html
>
Will do! Sorry for the mess! I over-confidently assumed everything was
the same between 6.18 and spi-nor/next!
- Nuno Sá
> > + .fixups = &is25wx01g_fixups,
> > }
> > };
> >
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2026-09-14 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 15:36 [PATCH 0/2] mtd: spi-nor: issi: add support for the IS25WX01G octal flash Nuno Sá
2026-09-11 15:36 ` [PATCH 1/2] mtd: spi-nor: sfdp: get the 1-1-8 and 1-8-8 page programs from 4BAIT Nuno Sá
2026-09-11 15:36 ` [PATCH 2/2] mtd: spi-nor: issi: Add support for is25wx01g Nuno Sá
2026-09-11 15:44 ` sashiko-bot
2026-09-11 16:09 ` Nuno Sá
2026-09-14 6:28 ` Michael Walle
2026-09-14 8:20 ` Nuno Sá [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=aqetgODkt3MhNndd@nsa \
--to=nuno.sa@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=takahiro.kuwano@infineon.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®