From: Ezra Buehler <ezra@easyb.ch>
To: linux-mtd@lists.infradead.org
Cc: Chuanhong Guo <gch981213@gmail.com>,
Dmitry Rokosov <ddrokosov@sberdevices.ru>,
Martin Kurbanov <mmkurbanov@sberdevices.ru>,
Md Sadre Alam <quic_mdalam@quicinc.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Sridharan S N <quic_sridsn@quicinc.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] mtd: spinand: Resolve GigaDevice/ESMT ID clash
Date: Thu, 25 Jan 2024 22:01:06 +0200 [thread overview]
Message-ID: <20240125200108.24374-1-ezra@easyb.ch> (raw)
From: Ezra Buehler <ezra.buehler@husqvarnagroup.com>
Since commit aa08bf187f32 ("mtd: spinand: esmt: add support for
F50D2G41KA") the MT7688-based GARDENA smart Gateway no longer boots.
This is due to an ID clash resulting in the ESMT driver being used
together with our GigaDevice GD5F1GQ5UEYIG.
The following patches resolve the issue for our board. However, I do not
have any ESMT NAND flash chips to further test my changes with.
Ezra Buehler (2):
mtd: spinand: Add support for 5-byte IDs
mtd: spinand: esmt: Extend IDs to 5 bytes
drivers/mtd/nand/spi/esmt.c | 9 ++++++---
include/linux/mtd/spinand.h | 2 +-
2 files changed, 7 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2024-01-25 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 20:01 Ezra Buehler [this message]
2024-01-25 20:01 ` [PATCH 1/2] mtd: spinand: Add support for 5-byte IDs Ezra Buehler
2024-01-26 18:46 ` Martin Kurbanov
2024-02-05 14:28 ` Miquel Raynal
2024-01-25 20:01 ` [PATCH 2/2] mtd: spinand: esmt: Extend IDs to 5 bytes Ezra Buehler
2024-01-26 18:48 ` Martin Kurbanov
2024-01-27 8:26 ` Ezra Buehler
2024-02-05 14:28 ` Miquel Raynal
2024-01-26 11:09 ` [PATCH 0/2] mtd: spinand: Resolve GigaDevice/ESMT ID clash Dmitry Rokosov
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=20240125200108.24374-1-ezra@easyb.ch \
--to=ezra@easyb.ch \
--cc=ddrokosov@sberdevices.ru \
--cc=gch981213@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mmkurbanov@sberdevices.ru \
--cc=quic_mdalam@quicinc.com \
--cc=quic_sridsn@quicinc.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/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
all inboxes | Powered by JetHome®