[<prev] [next>] [day] [month] [year] [list]
Message-ID:
<TYZPR01MB55567825EA7348A0482DB916C9D8A@TYZPR01MB5556.apcprd01.prod.exchangelabs.com>
Date: Tue, 2 Dec 2025 23:05:56 +0800
From: Ziyang Huang <hzyitc@...look.com>
To: miquel.raynal@...tlin.com
Cc: richard@....at,
vigneshr@...com,
tudor.ambarus@...aro.org,
mmkurbanov@...utedevices.com,
hzyitc@...look.com,
george.moussalem@...look.com,
linux-mtd@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: [PATCH] Revert "mtd: spinand: esmt: fix id code for F50D1G41LB"
This reverts commit dd26402642a0899fde59ea6b0852fad3d799b4cc.
The issue George met is due to the limit of QPIC, not the issue of the
flash chip.
QPIC only supports 4 bytes ID. So the fifth byte is always 0.
If we use spi-gpio, the fifth byte can be read correctly.
Signed-off-by: Ziyang Huang <hzyitc@...look.com>
---
drivers/mtd/nand/spi/esmt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/spi/esmt.c b/drivers/mtd/nand/spi/esmt.c
index 9a9325c0bc49..c1285d52d458 100644
--- a/drivers/mtd/nand/spi/esmt.c
+++ b/drivers/mtd/nand/spi/esmt.c
@@ -199,7 +199,7 @@ static const struct spinand_info esmt_c8_spinand_table[] = {
SPINAND_FACT_OTP_INFO(2, 0, &f50l1g41lb_fact_otp_ops)),
SPINAND_INFO("F50D1G41LB",
SPINAND_ID(SPINAND_READID_METHOD_OPCODE_ADDR, 0x11, 0x7f,
- 0x7f),
+ 0x7f, 0x7f),
NAND_MEMORG(1, 2048, 64, 64, 1024, 20, 1, 1, 1),
NAND_ECCREQ(1, 512),
SPINAND_INFO_OP_VARIANTS(&read_cache_variants,
--
2.40.1
Powered by blists - more mailing lists