From: Hauke Mehrtens <hauke@hauke-m.de>
To: stable@vger.kernel.org
Cc: John Audia <therealgraysky@proton.me>,
Ezra Buehler <ezra.buehler@husqvarnagroup.com>,
linux-mtd@lists.infradead.org,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Backport "mtd: spinand: Add support for 5-byte IDs" to 6.6, 6.7 and 6.8
Date: Sat, 30 Mar 2024 14:49:56 +0100 [thread overview]
Message-ID: <de171eb5-3e95-4529-9228-9a4ed526ed46@hauke-m.de> (raw)
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@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@husqvarnagroup.com>
Reviewed-by: Martin Kurbanov <mmkurbanov@salutedevices.com>
Tested-by: Martin Kurbanov <mmkurbanov@salutedevices.com>
Signed-off-by: Miquel Raynal <miquel.raynal@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@husqvarnagroup.com>
Date: Thu Jan 25 22:01:08 2024 +0200
mtd: spinand: esmt: Extend IDs to 5 bytes
Hauke
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2024-03-30 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 13:49 Hauke Mehrtens [this message]
2024-03-30 16:25 ` Backport "mtd: spinand: Add support for 5-byte IDs" to 6.6, 6.7 and 6.8 Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de171eb5-3e95-4529-9228-9a4ed526ed46@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=ezra.buehler@husqvarnagroup.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=stable@vger.kernel.org \
--cc=therealgraysky@proton.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).