From: <Tudor.Ambarus@microchip.com>
To: <michael@walle.cc>, <linux-mtd@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <p.yadav@ti.com>, <miquel.raynal@bootlin.com>, <richard@nod.at>,
<vigneshr@ti.com>
Subject: Re: [PATCH] mtd: spi-nor: winbond: fix the name of W25Q16JV-IM/-JM
Date: Mon, 28 Feb 2022 08:26:06 +0000 [thread overview]
Message-ID: <2d7ef659-b592-3241-ac7e-36736bd446c4@microchip.com> (raw)
In-Reply-To: <39603d75-f4a5-4bad-d2a5-99050b6b3407@microchip.com>
On 1/20/22 18:14, Tudor Ambarus wrote:
> On 1/20/22 4:57 PM, Michael Walle wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> We don't include the package encoding in the name. Thus, just use
>
> s/package encoding/ temp
>> w25q15jvm as the name for this flash.
If I remember correctly I think that we agreed on u-boot ml that we should rename
all -jvm flashes to -dtr. Let me know if you want to reiterate this or not, I
can add it to a todo list if you don't feel like doing it right now.
Cheers,
ta
>>
>> Signed-off-by: Michael Walle <michael@walle.cc>
>> ---
>> drivers/mtd/spi-nor/winbond.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/mtd/spi-nor/winbond.c b/drivers/mtd/spi-nor/winbond.c
>> index 93b537f4f0cb..3d91888882e4 100644
>> --- a/drivers/mtd/spi-nor/winbond.c
>> +++ b/drivers/mtd/spi-nor/winbond.c
>> @@ -52,7 +52,7 @@ static const struct flash_info winbond_parts[] = {
>> SPI_NOR_QUAD_READ) },
>> { "w25x32", INFO(0xef3016, 0, 64 * 1024, 64)
>> NO_SFDP_FLAGS(SECT_4K) },
>> - { "w25q16jv-im/jm", INFO(0xef7015, 0, 64 * 1024, 32)
>> + { "w25q16jvm", INFO(0xef7015, 0, 64 * 1024, 32)
>> FLAGS(SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB)
>> NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ |
>> SPI_NOR_QUAD_READ) },
>> --
>> 2.30.2
>>
>
prev parent reply other threads:[~2022-02-28 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 14:57 [PATCH] mtd: spi-nor: winbond: fix the name of W25Q16JV-IM/-JM Michael Walle
[not found] ` <39603d75-f4a5-4bad-d2a5-99050b6b3407@microchip.com>
2022-02-28 8:26 ` Tudor.Ambarus [this message]
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=2d7ef659-b592-3241-ac7e-36736bd446c4@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.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