Backport "mtd: spinand: Add support for 5-byte IDs" to 6.6, 6.7 and 6.8

[Hauke Mehrtens]

Hi,

Please backport the following commit back to the Linux stable kernels 
6.6, 6.7 and 6.8:

commit 34a956739d295de6010cdaafeed698ccbba87ea4
Author: Ezra Buehler <ezra.buehler at husqvarnagroup.com>
Date:   Thu Jan 25 22:01:07 2024 +0200

     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: Ezra Buehler <ezra.buehler at husqvarnagroup.com>
     Reviewed-by: Martin Kurbanov <mmkurbanov at salutedevices.com>
     Tested-by: Martin Kurbanov <mmkurbanov at salutedevices.com>
     Signed-off-by: Miquel Raynal <miquel.raynal at bootlin.com>
     Link: 
https://lore.kernel.org/linux-mtd/20240125200108.24374-2-ezra@easyb.ch


This will fix a regression introduced between Linux kernel 6.6.22 and 
6.6.23 in OpenWrt. The esmt NAND flash is not detected any more:
<3>[    0.885607] spi-nand spi0.0: unknown raw ID c8017f7f
<4>[    0.890852] spi-nand: probe of spi0.0 failed with error -524
See: https://github.com/openwrt/openwrt/pull/14992


The following commit was backported to 6.6.22, but the commit it depends 
on was not backported.
commit 4bd14b2fd8a83a2f5220ba4ef323f741e11bfdfd
Author: Ezra Buehler <ezra.buehler at husqvarnagroup.com>
Date:   Thu Jan 25 22:01:08 2024 +0200

     mtd: spinand: esmt: Extend IDs to 5 bytes


Hauke