target/linux/generic/backport-6.6/981-mtd-spinand-Add-support-for-5-byte-IDs.patch

   1 From: Ezra Buehler <ezra.buehler@husqvarnagroup.com>
   2
   3 E.g. ESMT chips will return an identification code with a length of 5
   4 bytes. In order to prevent ambiguity, flash chips would actually need to
   5 return IDs that are up to 17 or more bytes long due to JEDEC's
   6 continuation scheme. I understand that if a manufacturer ID is located
   7 in bank N of JEDEC's database (there are currently 16 banks), N - 1
   8 continuation codes (7Fh) need to be added to the identification code
   9 (comprising of manufacturer ID and device ID). However, most flash chip
  10 manufacturers don't seem to implement this (correctly).
  11
  12 Signed-off-by: Ezra Buehler <ezra.buehler@husqvarnagroup.com>
  13 ---
  14  include/linux/mtd/spinand.h | 2 +-
  15  1 file changed, 1 insertion(+), 1 deletion(-)
  16
  17 --- a/include/linux/mtd/spinand.h
  18 +++ b/include/linux/mtd/spinand.h
  19 @@ -169,7 +169,7 @@
  20  struct spinand_op;
  21  struct spinand_device;
  22
  23 -#define SPINAND_MAX_ID_LEN     4
  24 +#define SPINAND_MAX_ID_LEN     5
  25  /*
  26   * For erase, write and read operation, we got the following timings :
  27   * tBERS (erase) 1ms to 4ms