From: "Nuno Sá" <nuno.sa@analog.com>
To: sashiko-reviews@lists.linux.dev
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <mwalle@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Takahiro Kuwano <takahiro.kuwano@infineon.com>,
Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH 2/2] mtd: spi-nor: issi: Add support for is25wx01g
Date: Fri, 11 Sep 2026 17:09:24 +0100 [thread overview]
Message-ID: <aqQnfFnjnEC6RJUy@nsa> (raw)
In-Reply-To: <20260911154412.B53B01F00893@smtp.kernel.org>
On Fri, Sep 11, 2026 at 03:44:12PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] The patch introduces multiple build failures due to an incomplete forward-port from an older kernel version. It references non-existent struct fields, uses an undeclared flag, and attempts an outdated method to disable 16-bit status register writes.
> --
>
> commit 2a2f93cf391e237e4b5b711cef68cc225e2bc2fe
> Author: Nuno Sá <nuno.sa@analog.com>
>
> mtd: spi-nor: issi: Add support for is25wx01g
>
> This patch adds support for the ISSI IS25WX01G 1 Gbit octal NOR flash. It
> relies on SFDP and provides BFPT fixups to handle the lack of a 35h command
> and to disable the quad enable method.
>
> > diff --git a/drivers/mtd/spi-nor/issi.c b/drivers/mtd/spi-nor/issi.c
> > index 2f057d731df2a..aac9d19b90fcf 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;
>
> [Severity: Low]
> Does this code compile on the target tree? struct spi_nor does not appear
> to have a flags member in the current API, and SNOR_F_HAS_16BIT_SR seems
> to be undeclared.
Ok! It seems I was over confident and it seems things changes in
spi-nor/next! Will fix it and resend!!
- Nuno Sá
>
> > +
> > + /*
> > + * 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,
> > +};
> > +
>
> [ ... ]
>
> > @@ -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",
> > + .fixups = &is25wx01g_fixups,
>
> [Severity: Low]
> Does struct flash_info have a fixups member in the current framework?
> It looks like fixups might need to be registered via struct
> spi_nor_manufacturer and its fixups array instead.
>
> > }
> > };
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260911-mtd-spi-nor-new-issi-chip-v1-0-c54615f8c30f@analog.com?part=2
next prev parent reply other threads:[~2026-09-11 16:08 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á [this message]
2026-09-14 6:28 ` Michael Walle
2026-09-14 8:20 ` Nuno Sá
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=aqQnfFnjnEC6RJUy@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=sashiko-reviews@lists.linux.dev \
--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®