From: <Takahiro.Kuwano@infineon.com>
To: <nuno.sa@analog.com>, <linux-mtd@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <pratyush@kernel.org>, <mwalle@kernel.org>,
<miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>
Subject: RE: [PATCH RESEND v3] mtd: spi-nor: micron-st: Add support for is25wx01g
Date: Thu, 5 Nov 2026 04:44:01 +0000 [thread overview]
Message-ID: <0cbfb61d062b437b8e860a9c93b13e4d@infineon.com> (raw)
In-Reply-To: <20261102-mtd-spi-nor-new-issi-chip-v3-1-f5e38e200fc8@analog.com>
Hi,
> Add support for the ISSI IS25WX01G, a 1 Gbit (128 MiB) octal NOR flash.
> The part is fully described by SFDP, so only the flash ID and a small
> post_bfpt fixup are needed.
>
> WRITE STATUS REGISTER (01h) takes a single data byte and only affects
> status register bits 7:2, so the default 16-bit Write Status assumption
> does not hold. Clear write_sr1_and_sr2 so that the single byte write_sr1
> path is taken; write_sr1 is already set to 01h by the BFPT parsing.
>
> The flash also has no Status Register 2. Configuration registers are read
> with B5h/85h and written with B1h/81h, and the 35h Read Configuration
> Register command does not exist, so clear read_sr2 as well.
>
> Software write protection is done through the block protect bits in the
> status register: BP0-BP2 at bits 4:2, BP3 at bit 6 and a Top/Bottom bit at
> bit 5, which is exactly what SPI_NOR_HAS_LOCK, SPI_NOR_4BIT_BP,
> SPI_NOR_BP3_SR_BIT6 and SPI_NOR_HAS_TB describe, so set those flags to get
> the generic locking support.
>
> Note that given that the Flag Status Register (FSR) handling is the same
> as in some micron devices, were're adding the issi chip directly on the
> micron-st driver.
>
> Signed-off-by: Nuno Sá <nuno.sa@analog.com>
Please add Link: tag as Michael mentioned in [1].
[...]
> @@ -655,6 +680,7 @@ static const struct spi_nor_fixups micron_st_nor_fixups = {
>
> static const struct spi_nor_fixup micron_fixups[] = {
> { .fixups = µn_st_nor_fixups },
> + { .id = SNOR_ID(0x9d, 0x5b, 0x1b), .fixups = &is25wx01g_fixups },
Sashiko's comment [2] looks valid to me as this chip supports 8D-8D-8D.
Could you please take a look?
Thanks,
Takahiro
[1] https://lore.kernel.org/linux-mtd/DLETRRVRUWEP.1VU1EHARD3MSH@kernel.org/
[2] https://sashiko.dev/#/patchset/20261102-mtd-spi-nor-new-issi-chip-v3-1-f5e38e200fc8%40analog.com
next prev parent reply other threads:[~2026-11-05 4:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 12:21 Nuno Sá
2026-11-05 4:44 ` Takahiro.Kuwano [this message]
2026-11-05 11:36 ` 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=0cbfb61d062b437b8e860a9c93b13e4d@infineon.com \
--to=takahiro.kuwano@infineon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=nuno.sa@analog.com \
--cc=pratyush@kernel.org \
--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
all inboxes | Powered by JetHome®