From: Yicong Yang <yangyicong@hisilicon.com>
To: <tudor.ambarus@microchip.com>, <broonie@kernel.org>,
<miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>,
<linux-mtd@lists.infradead.org>, <linux-spi@vger.kernel.org>
Cc: <john.garry@huawei.com>, <prime.zeng@huawei.com>,
<yangyicong@hisilicon.com>, <linuxarm@openeuler.org>
Subject: [PATCH 0/2] Add check of 4-byte when parsing SFDP 4bait table
Date: Wed, 27 Jan 2021 17:40:48 +0800 [thread overview]
Message-ID: <1611740450-47975-1-git-send-email-yangyicong@hisilicon.com> (raw)
Add check of 4-byte address mode support when parsing SFDP 4bait. Some
flash will provide a 4bait table and the spi-nor core will convert the
address mode to 4-byte without checking whether it's actually supported
or not by the controller. For example, the 16M s25fs128s1 provides the
4bait and will be convert to 4-byte address mode, which makes it unusable
on hisi-sfc-v3xx on hip08 platform.
Add the check before convert the address mode when parsing the 4bait will
solve this issue.
Yicong Yang (2):
mtd: spi-nor: check 4-byte address support when parsing 4bait
spi: hisi-sfc-v3xx: add address mode check
drivers/mtd/spi-nor/sfdp.c | 48 +++++++++++++++++++++++++++++++++++++++++
drivers/spi/spi-hisi-sfc-v3xx.c | 25 ++++++++++++++++++++-
2 files changed, 72 insertions(+), 1 deletion(-)
--
2.8.1
next reply other threads:[~2021-01-27 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 9:40 Yicong Yang [this message]
2021-01-27 9:40 ` [PATCH 1/2] mtd: spi-nor: check 4-byte address support when parsing 4bait Yicong Yang
[not found] ` <20210129111649.jypytpp7dkywthwh@ti.com>
2021-02-01 12:55 ` Yicong Yang
2021-01-27 9:40 ` [PATCH 2/2] spi: hisi-sfc-v3xx: add address mode check Yicong Yang
2021-01-27 17:15 ` (subset) [PATCH 0/2] Add check of 4-byte when parsing SFDP 4bait table Mark Brown
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=1611740450-47975-1-git-send-email-yangyicong@hisilicon.com \
--to=yangyicong@hisilicon.com \
--cc=broonie@kernel.org \
--cc=john.garry@huawei.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=miquel.raynal@bootlin.com \
--cc=prime.zeng@huawei.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--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;
as well as URLs for NNTP newsgroup(s).