Commit 34a95673 authored by Ezra Buehler's avatar Ezra Buehler Committed by Miquel Raynal

mtd: spinand: Add support for 5-byte IDs

E.g. ESMT chips will return an identification code with a length of 5
bytes. In order to prevent ambiguity, flash chips would actually need to
return IDs that are up to 17 or more bytes long due to JEDEC's
continuation scheme. I understand that if a manufacturer ID is located
in bank N of JEDEC's database (there are currently 16 banks), N - 1
continuation codes (7Fh) need to be added to the identification code
(comprising of manufacturer ID and device ID). However, most flash chip
manufacturers don't seem to implement this (correctly).
Signed-off-by: default avatarEzra Buehler <ezra.buehler@husqvarnagroup.com>
Reviewed-by: default avatarMartin Kurbanov <mmkurbanov@salutedevices.com>
Tested-by: default avatarMartin Kurbanov <mmkurbanov@salutedevices.com>
Signed-off-by: default avatarMiquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20240125200108.24374-2-ezra@easyb.ch
parent c7f0f920
...@@ -169,7 +169,7 @@ ...@@ -169,7 +169,7 @@
struct spinand_op; struct spinand_op;
struct spinand_device; struct spinand_device;
#define SPINAND_MAX_ID_LEN 4 #define SPINAND_MAX_ID_LEN 5
/* /*
* For erase, write and read operation, we got the following timings : * For erase, write and read operation, we got the following timings :
* tBERS (erase) 1ms to 4ms * tBERS (erase) 1ms to 4ms
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment