linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] mtd: spinand: esmt: fix id code for F50D1G41LB
@ 2025-05-15 17:46 George Moussalem via B4 Relay
  2025-05-16 14:55 ` Miquel Raynal
  0 siblings, 1 reply; 2+ messages in thread
From: George Moussalem via B4 Relay @ 2025-05-15 17:46 UTC (permalink / raw)
  To: Miquel Raynal, Richard Weinberger, Vignesh Raghavendra,
	Martin Kurbanov, Ezra Buehler
  Cc: linux-mtd, linux-kernel, robimarko, George Moussalem

From: George Moussalem <george.moussalem@outlook.com>

Upon detecting the ID for the ESMT F50D1G41LB chip, the fifth byte
returned is always 0x00 instead of the expected JEDEC continuation code
of 0x7f. This causes detection to fail:

[    0.304399] spi-nand spi0.0: unknown raw ID c8117f7f00
[    0.508943] spi-nand: probe of spi0.0 failed with error -524

So let's revert back to the 4 byte ID code for this chip
specifically.

Fixes: 4bd14b2fd8a8 ("mtd: spinand: esmt: Extend IDs to 5 bytes")
Signed-off-by: George Moussalem <george.moussalem@outlook.com>
---
drivers/mtd/nand/raw/nand_esmt.c mentions that the 5th byte is used to
set ECC strength requirements for the detected chip, so no JEDEC
continuation code is actually expected. I don't know if this there was
a change in design or approach somewhere along the way, hence I fixed
the ID for this chip only.
---
 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 299d0e507c29fcde1c38d2fdebc0cc755825dade..9e286612a296c75831f7b95a010a5fe47579c36d 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,

---
base-commit: 484803582c77061b470ac64a634f25f89715be3f
change-id: 20250515-spinand-esmt-76fc6aaa7019

Best regards,
-- 
George Moussalem <george.moussalem@outlook.com>



^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] mtd: spinand: esmt: fix id code for F50D1G41LB
  2025-05-15 17:46 [PATCH] mtd: spinand: esmt: fix id code for F50D1G41LB George Moussalem via B4 Relay
@ 2025-05-16 14:55 ` Miquel Raynal
  0 siblings, 0 replies; 2+ messages in thread
From: Miquel Raynal @ 2025-05-16 14:55 UTC (permalink / raw)
  To: Richard Weinberger, Vignesh Raghavendra, Martin Kurbanov,
	Ezra Buehler, George Moussalem
  Cc: linux-mtd, linux-kernel, robimarko

On Thu, 15 May 2025 21:46:05 +0400, George Moussalem wrote:
> Upon detecting the ID for the ESMT F50D1G41LB chip, the fifth byte
> returned is always 0x00 instead of the expected JEDEC continuation code
> of 0x7f. This causes detection to fail:
> 
> [    0.304399] spi-nand spi0.0: unknown raw ID c8117f7f00
> [    0.508943] spi-nand: probe of spi0.0 failed with error -524
> 
> [...]

Applied to nand/next, thanks!

[1/1] mtd: spinand: esmt: fix id code for F50D1G41LB
      commit: dd26402642a0899fde59ea6b0852fad3d799b4cc

Patche(s) should be available on mtd/linux.git and will be
part of the next PR (provided that no robot complains by then).

Kind regards,
Miquèl


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2025-05-16 14:55 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-05-15 17:46 [PATCH] mtd: spinand: esmt: fix id code for F50D1G41LB George Moussalem via B4 Relay
2025-05-16 14:55 ` Miquel Raynal

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).