From: Michael Walle <michael@walle.cc>
To: Jae Hyun Yoo <quic_jaehyoo@quicinc.com>
Cc: clg@kaod.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, p.yadav@ti.com,
quic_ggregory@quicinc.com, quic_jiles@quicinc.com,
tudor.ambarus@microchip.com
Subject: Re: [PATCH] mtd: spi-nor: winbond: add support for W25Q512NW-IQ/IN
Date: Sat, 16 Jul 2022 01:20:51 +0200 [thread overview]
Message-ID: <00bdb7304cf479d21b87d4a35e908fb4@walle.cc> (raw)
In-Reply-To: <2e0f02f3-0e0e-8690-a58e-bb74a21ab63e@quicinc.com>
Hi,
>> diff --git a/drivers/mtd/spi-nor/core.c b/drivers/mtd/spi-nor/core.c
>> index ce5d69317d46..a2c8de250e01 100644
>> --- a/drivers/mtd/spi-nor/core.c
>> +++ b/drivers/mtd/spi-nor/core.c
>> @@ -2113,6 +2113,10 @@ spi_nor_select_uniform_erase(struct
>> spi_nor_erase_map *map,
>>
>> tested_erase = &map->erase_type[i];
>>
>> + /* Skip masked erase types. */
>> + if (!tested_erase->size)
>> + continue;
>
> Yes, it also works. Do you want me to update this patch with adding
> this
> fix? Or is it good to go as is so that the INFO table can be replaced
> with SNOR_ID3 later after the fix is merged?
Please add this as a separate preceding patch to your original one
where you add the flash. Keep the INFO(0xef6020, 0, 0, 0). Then we
will replace it later with the SNOR_ID3().
Thanks for debugging!
-michael
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-07-15 23:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 14:57 [PATCH] mtd: spi-nor: winbond: add support for W25Q512NW-IQ/IN Jae Hyun Yoo
2022-07-11 6:24 ` Cédric Le Goater
2022-07-11 9:50 ` Michael Walle
2022-07-13 14:26 ` Jae Hyun Yoo
2022-07-13 14:32 ` Michael Walle
2022-07-13 21:01 ` Jae Hyun Yoo
2022-07-14 7:41 ` Michael Walle
2022-07-14 13:47 ` Jae Hyun Yoo
2022-07-14 14:16 ` Michael Walle
2022-07-14 14:21 ` Michael Walle
2022-07-14 14:30 ` Jae Hyun Yoo
2022-07-15 20:15 ` Jae Hyun Yoo
2022-07-15 22:35 ` Jae Hyun Yoo
2022-07-15 23:03 ` Michael Walle
2022-07-15 23:15 ` Jae Hyun Yoo
2022-07-15 23:20 ` Michael Walle [this message]
2022-07-15 23:26 ` Jae Hyun Yoo
2022-07-15 22:52 ` Michael Walle
2022-07-15 23:04 ` Jae Hyun Yoo
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=00bdb7304cf479d21b87d4a35e908fb4@walle.cc \
--to=michael@walle.cc \
--cc=clg@kaod.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=p.yadav@ti.com \
--cc=quic_ggregory@quicinc.com \
--cc=quic_jaehyoo@quicinc.com \
--cc=quic_jiles@quicinc.com \
--cc=tudor.ambarus@microchip.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