From: Anshul Dalal <anshuld@ti.com>
To: Ssunk <ssunkkan@gmail.com>, <u-boot@lists.denx.de>, <vigneshr@ti.com>
Cc: <takahiro.kuwano@infineon.com>
Subject: Re: [PATCH] mtd: spi-nor: Update XM25QH512C to XM25QH512D
Date: Wed, 29 Apr 2026 12:51:41 +0530 [thread overview]
Message-ID: <DI5GHDQSZVJL.2WY7OPMAER9IA@ti.com> (raw)
In-Reply-To: <20260424102343.1087-1-ssunkkan@gmail.com>
Hi Ssunk,
On Fri Apr 24, 2026 at 3:53 PM IST, Ssunk wrote:
> The XM25QH512C has been replaced by XM25QH512D. Both share the same
> JEDEC ID (0x204020) and have identical parameters. Update the flash
> name to reflect the current part in use.
Please provide a Signed-off-by here along with datasheet or the product
page referencing the change to the product's name. As I see now, both
the parts are listed on XMCWH's website[1] with unique names.
[1]: https://www.xmcwh.com/en/site/product_con/960
https://www.xmcwh.com/en/site/product_con/671
Regards,
Anshul
> ---
> drivers/mtd/spi/spi-nor-ids.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/spi/spi-nor-ids.c b/drivers/mtd/spi/spi-nor-ids.c
> index c0fa98424aa..3b8e309e0f2 100644
> --- a/drivers/mtd/spi/spi-nor-ids.c
> +++ b/drivers/mtd/spi/spi-nor-ids.c
> @@ -672,7 +672,7 @@ const struct flash_info spi_nor_ids[] = {
> { INFO("XM25QU128C", 0x204118, 0, 64 * 1024, 256, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
> { INFO("XM25QH256C", 0x204019, 0, 64 * 1024, 512, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
> { INFO("XM25QU256C", 0x204119, 0, 64 * 1024, 512, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
> - { INFO("XM25QH512C", 0x204020, 0, 64 * 1024, 1024, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
> + { INFO("XM25QH512D", 0x204020, 0, 64 * 1024, 1024, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
> { INFO("XM25QU512C", 0x204120, 0, 64 * 1024, 1024, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
> { INFO("XM25QH01D", 0x204021, 0, 64 * 1024, 2048, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
> #endif
next prev parent reply other threads:[~2026-04-29 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 10:23 [PATCH] mtd: spi-nor: Update XM25QH512C to XM25QH512D Ssunk
2026-04-29 7:21 ` Anshul Dalal [this message]
2026-05-06 10:30 ` [PATCH v2] " Ssunk
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=DI5GHDQSZVJL.2WY7OPMAER9IA@ti.com \
--to=anshuld@ti.com \
--cc=ssunkkan@gmail.com \
--cc=takahiro.kuwano@infineon.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.