From: Ssunk <ssunkkan@gmail.com>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: Ssunk <ssunkkan@gmail.com>,
Takahiro.Kuwano@infineon.com, jagan@amarulasolutions.com,
pratyush@kernel.org, trini@konsulko.com,
tudor.ambarus@linaro.org, u-boot@lists.denx.de, vigneshr@ti.com
Subject: [PATCH v3] spi-nor: add support for XM25QH01D
Date: Thu, 4 Dec 2025 18:53:12 +0800 [thread overview]
Message-ID: <20251110203000.9999-1-ssunkkan@gmail.com> (raw)
In-Reply-To: <4cd587dc-da4d-4645-9a6a-fd14dcf15de8@mailbox.org>
Hi Marek,
Thanks for the clarification.
As discussed, I am not reordering the XMC flash list. This v3 only adds
the new XM25QH01D entry in the appropriate alphabetical position, without
touching the rest of the list.
I welcome feedback from the SPI-NOR subsystem maintainers as well.
Thanks again for the guidance!
Regards,
Ssunk
---
[PATCH v3] spi-nor: add support for XM25QH01D
Add support for the XMC XM25QH01D SPI NOR flash.
This device has 1Gbit (128MB) capacity, with 64KB sectors and supports
4KB erase, dual/quad read, and 4-byte opcodes.
Datasheet:
https://www.xmcwh.com/uploads/958/XM25QH01D_Ver1.0.pdf
Changes in v3:
- Do NOT reorder the XMC flash list (per Marek’s feedback)
- Only add the XM25QH01D entry in the correct sorted position
Changes in v2:
- Attempted to reorder the list; reverted in v3
Signed-off-by: Ssunk <ssunkkan@gmail.com>
---
drivers/mtd/spi/spi-nor-ids.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mtd/spi/spi-nor-ids.c b/drivers/mtd/spi/spi-nor-ids.c
index 0383175beb5..00f78c2aaae 100644
--- a/drivers/mtd/spi/spi-nor-ids.c
+++ b/drivers/mtd/spi/spi-nor-ids.c
@@ -595,6 +595,7 @@ const struct flash_info spi_nor_ids[] = {
#endif
#ifdef CONFIG_SPI_FLASH_XMC
/* XMC (Wuhan Xinxin Semiconductor Manufacturing Corp.) */
+ { INFO("XM25QH01D", 0x204021, 0, 64 * 1024, 2048, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
{ INFO("XM25QH64A", 0x207017, 0, 64 * 1024, 128, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
{ INFO("XM25QH64C", 0x204017, 0, 64 * 1024, 128, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
{ INFO("XM25QH128A", 0x207018, 0, 64 * 1024, 256, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
--
2.34.1
next prev parent reply other threads:[~2025-12-04 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 10:58 [PATCH] spi-nor: add support for XM25QH01D Ssunk
2025-11-02 11:14 ` Ssunk
2025-11-02 13:58 ` Marek Vasut
2025-11-03 11:12 ` [PATCH v2] " Ssunk
2025-11-03 12:38 ` Marek Vasut
2025-11-04 11:03 ` Ssunk
2025-11-09 19:01 ` Marek Vasut
2025-12-04 10:53 ` Ssunk [this message]
2026-01-29 12:12 ` [PATCH v3] " Ssunk
2026-01-29 13:04 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2025-11-02 11:20 [PATCH] mtd: spi-nor: Add support for Dosilicon DS25Q4CB/DS25Q4DN Ssunk
2026-01-29 12:26 ` [PATCH v3] spi-nor: add support for XM25QH01D Ssunk
2026-01-29 13:05 ` Marek Vasut
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=20251110203000.9999-1-ssunkkan@gmail.com \
--to=ssunkkan@gmail.com \
--cc=Takahiro.Kuwano@infineon.com \
--cc=jagan@amarulasolutions.com \
--cc=marek.vasut@mailbox.org \
--cc=pratyush@kernel.org \
--cc=trini@konsulko.com \
--cc=tudor.ambarus@linaro.org \
--cc=u-boot@lists.denx.de \
--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