From: Haibo Chen <haibo.chen@nxp.com>
To: Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <mwalle@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Haibo Chen <haibo.chen@nxp.com>,
imx@lists.linux.dev
Subject: [PATCH v4 5/5] mtd: spi-nor: micron-st: add comment for mt35xu02gcba
Date: Wed, 12 Nov 2025 19:05:13 +0800 [thread overview]
Message-ID: <20251112-nor-v4-5-e4637be82a0a@nxp.com> (raw)
In-Reply-To: <20251112-nor-v4-0-e4637be82a0a@nxp.com>
The MT35XU02GCBA flash device does not support chip erase,
according to its datasheet. It supports die erase, which
means the current driver implementation will likely need
to be converted to use die erase.
Furthermore, similar to the MT35XU01GBBA, the
SPI_NOR_IO_MODE_EN_VOLATILE flag probably needs to be enabled.
Link: https://datasheet.octopart.com/MT35XU02GCBA1G12-0AAT-Micron-datasheet-138896808.pdf
Reviewed-by: Tudor Ambarus <tudor.ambarus@linaro.org>
Signed-off-by: Haibo Chen <haibo.chen@nxp.com>
---
drivers/mtd/spi-nor/micron-st.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/mtd/spi-nor/micron-st.c b/drivers/mtd/spi-nor/micron-st.c
index c89c06b1fc61a581fea2e18732be2501a15715f9..f94e9d2d17bf4aa7c36ba3aa37d34f767a9f93ac 100644
--- a/drivers/mtd/spi-nor/micron-st.c
+++ b/drivers/mtd/spi-nor/micron-st.c
@@ -204,6 +204,16 @@ static const struct flash_info micron_nor_parts[] = {
.fixup_flags = SPI_NOR_IO_MODE_EN_VOLATILE,
.fixups = &mt35xu01gbba_fixups,
}, {
+ /*
+ * The MT35XU02GCBA flash device does not support
+ * chip erase, according to its datasheet.
+ * It supports die erase, which means the current
+ * driver implementation will likely need to be
+ * converted to use die erase.
+ * Furthermore, similar to the MT35XU01GBBA, the
+ * SPI_NOR_IO_MODE_EN_VOLATILE flag probably needs
+ * to be enabled.
+ */
.id = SNOR_ID(0x2c, 0x5b, 0x1c),
.name = "mt35xu02g",
.sector_size = SZ_128K,
--
2.34.1
next prev parent reply other threads:[~2025-11-12 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 11:05 [PATCH v4 0/5] mtd: spi-nor: micron-st: few clean up for micron spi nor chip Haibo Chen
2025-11-12 11:05 ` [PATCH v4 1/5] mtd: spi-nor: micron-st: rename the die_late_init functions Haibo Chen
2025-11-12 11:05 ` [PATCH v4 2/5] mtd: spi-nor: micron-st: move set_octal_dtr to late_init() Haibo Chen
2025-11-12 11:05 ` [PATCH v4 3/5] mtd: spi-nor: micron-st: use SFDP of mt35xu512aba Haibo Chen
2025-11-12 11:05 ` [PATCH v4 4/5] mtd: spi-nor: micron-st: add mt35xu01gbba support Haibo Chen
2025-11-12 12:14 ` Tudor Ambarus
2025-11-12 11:05 ` Haibo Chen [this message]
2025-11-13 14:47 ` [PATCH v4 5/5] mtd: spi-nor: micron-st: add comment for mt35xu02gcba Pratyush Yadav
2025-11-13 15:42 ` Tudor Ambarus
2025-11-14 15:14 ` Pratyush Yadav
2025-11-18 12:12 ` [PATCH v4 0/5] mtd: spi-nor: micron-st: few clean up for micron spi nor chip Pratyush Yadav
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=20251112-nor-v4-5-e4637be82a0a@nxp.com \
--to=haibo.chen@nxp.com \
--cc=imx@lists.linux.dev \
--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=tudor.ambarus@linaro.org \
--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