From: Ssunk <ssunkkan@gmail.com>
To: mwalle@kernel.org
Cc: hhlee@google.com, linux-mtd@lists.infradead.org,
miquel.raynal@bootlin.com, pratyush@kernel.org, richard@nod.at,
roccochen@google.com, ssunkkan@gmail.com,
tudor.ambarus@linaro.org, vigneshr@ti.com
Subject: [PATCH v3] Add support for XM25LU64C
Date: Mon, 7 Jul 2025 20:14:28 +0800 [thread overview]
Message-ID: <20250707121428.3683-1-ssunkkan@gmail.com> (raw)
In-Reply-To: <DAZUMXW900R8.196NNPD9CWDCJ@kernel.org>
The device is produced by Wuhan Xinxin Semiconductor Manufacturing Corp. (XMC)
and found on some routers from Chinese manufactures.
We need to add this chip to google's AVL
The flash ID was incorrectly set to 0x16 0x41 0x17.
Update to 0x20 0x41 0x17 as per the datasheet.
The data sheet can be found here:
https://www.xmcwh.com/uploads/954/XM25LU64C_V1.5.pdf
Signed-off-by: Kankan Sun <ssunkkan@gmail.com>
---
Changes since v3:
- Our xm25lu64c is not working properly with flashrom, we need to add the following SPI_NOR_HAS_LOCK, SPI_NOR_HAS_TB flags to make the flashrom work normally.
v2->v3: Add SPI_NOR_HAS_LOCK, SPI_NOR_HAS_TB flags to make the flashrom work normally.
v1->v2: Update the flash ID to 0x20 0x41 0x17 as per the datasheet.
drivers/mtd/spi-nor/xmc.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/mtd/spi-nor/xmc.c b/drivers/mtd/spi-nor/xmc.c
index d5a06054b0dd..f1f2a9ba353e 100644
--- a/drivers/mtd/spi-nor/xmc.c
+++ b/drivers/mtd/spi-nor/xmc.c
@@ -19,6 +19,12 @@ static const struct flash_info xmc_nor_parts[] = {
.name = "XM25QH128A",
.size = SZ_16M,
.no_sfdp_flags = SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ,
+ }, {
+ .id = SNOR_ID(0x20, 0x41, 0x17),
+ .name = "XM25LU64C",
+ .size = SZ_8M,
+ .flags = SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB,
+ .no_sfdp_flags = SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ,
},
};
--
2.34.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2025-07-07 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250526121148.9417-1-ssunkkan@gmail.com>
2025-05-27 16:37 ` [PATCH] Add support for XM25LU64C Pratyush Yadav
2025-06-30 10:55 ` [PATCH v2] " Ssunk
2025-06-30 11:59 ` Michael Walle
2025-07-07 12:14 ` Ssunk [this message]
2025-07-07 12:57 ` [PATCH v3] " Michael Walle
2025-07-07 16:25 ` Ssunk
2025-07-11 8:43 ` [PATCH v4] mtd: spi-nor: " Ssunk
2025-07-16 13:42 ` Tudor Ambarus
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=20250707121428.3683-1-ssunkkan@gmail.com \
--to=ssunkkan@gmail.com \
--cc=hhlee@google.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=roccochen@google.com \
--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;
as well as URLs for NNTP newsgroup(s).