From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Nathan Barrett-Morrison <nathan.morrison@timesys.com>
Cc: greg.malysa@timesys.com,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <michael@walle.cc>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
"open list:SPI NOR SUBSYSTEM" <linux-mtd@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 3/3] mtd: spi-nor: Add support for IS25LX256 operating in 1S-8S-8S octal read mode
Date: Mon, 26 Dec 2022 10:17:07 +0200 [thread overview]
Message-ID: <eafebda5-7342-dfa9-7745-543d5f7d6f3d@linaro.org> (raw)
In-Reply-To: <9927a8c3-40cf-2c69-46c6-f660ff2422b1@linaro.org>
On 26.12.2022 10:04, Tudor Ambarus wrote:
> Hi, Nathan,
>
> The series is starting to look good, but I'll need another version,
> please.
>
> On 02.12.2022 15:55, Nathan Barrett-Morrison wrote:
>> This adds the IS25LX256 chip into the ISSI flash_info parts table
>
> Describe your changes in imperative mood, e.g. "Add support for
> S25LX256" instead of "This adds ..."
>
> It may worth to re-read
> https://www.kernel.org/doc/html/latest/process/submitting-patches.html
> once in a while.
>
>>
>> Signed-off-by: Nathan Barrett-Morrison <nathan.morrison@timesys.com>
>> ---
>> drivers/mtd/spi-nor/issi.c | 32 ++++++++++++++++++++++++++++++++
>> 1 file changed, 32 insertions(+)
>>
>> diff --git a/drivers/mtd/spi-nor/issi.c b/drivers/mtd/spi-nor/issi.c
>> index 89a66a19d754..362bc3603d8f 100644
>> --- a/drivers/mtd/spi-nor/issi.c
>> +++ b/drivers/mtd/spi-nor/issi.c
>> @@ -29,6 +29,35 @@ static const struct spi_nor_fixups is25lp256_fixups
>> = {
>> .post_bfpt = is25lp256_post_bfpt_fixups,
>> };
>> +static int
>> +is25lx256_post_bfpt_fixups(struct spi_nor *nor,
>> + const struct sfdp_parameter_header *bfpt_header,
>> + const struct sfdp_bfpt *bfpt)
>> +{
>> + /*
>> + * IS25LX256 supports both 1S-1S-8S and 1S-8S-8S.
>> + * However, the BFPT does not contain any information denoting this
>> + * functionality, so the proper fast read opcodes are never setup.
>> + * We're correcting this issue via the fixup below. Page program
>> + * commands are detected and setup properly via the 4BAIT lookup.
>> + */
Why don't you set the READ support when parsing the 4bait table? We need
to see the SFDP dump to determine how we treat this. I'm not sure a
post_bfpt hook is the right thing to do for this flash.
Thanks,
ta
next prev parent reply other threads:[~2022-12-26 8:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 13:55 [PATCH v4 0/3] mtd: spi-nor: Extend SFDP to support additional octal modes as per latest JEDEC standard Nathan Barrett-Morrison
2022-12-02 13:55 ` [PATCH v4 1/3] mtd: spi-nor: Extend SFDP 4byte address instruction lookup table with new octal modes as per JEDEC JESD216F Nathan Barrett-Morrison
2022-12-02 15:13 ` Michael Walle
2022-12-26 8:12 ` Tudor Ambarus
2022-12-02 13:55 ` [PATCH v4 2/3] mtd: spi-nor: Add additional octal-mode page program flags to be checked during SFDP 4BAIT parsing Nathan Barrett-Morrison
2022-12-02 15:16 ` Michael Walle
2022-12-26 8:14 ` Tudor Ambarus
2022-12-02 13:55 ` [PATCH v4 3/3] mtd: spi-nor: Add support for IS25LX256 operating in 1S-8S-8S octal read mode Nathan Barrett-Morrison
2022-12-02 15:20 ` Michael Walle
2022-12-03 4:32 ` kernel test robot
2022-12-03 7:44 ` kernel test robot
2022-12-26 8:04 ` Tudor Ambarus
2022-12-26 8:17 ` Tudor Ambarus [this message]
2022-12-27 12:37 ` Michael Walle
2022-12-27 13:24 ` Tudor Ambarus
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=eafebda5-7342-dfa9-7745-543d5f7d6f3d@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=greg.malysa@timesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=nathan.morrison@timesys.com \
--cc=pratyush@kernel.org \
--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
all inboxes | Powered by JetHome®