From: Patrick Williams <patrick@stwcx.xyz>
To: Michael Walle <michael@walle.cc>, Potin Lai <potin.lai@quantatw.com>
Cc: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>,
~sircmpwn/email-test-drive@lists.sr.ht, garnermic@fb.com,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Pratyush Yadav <pratyush@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: spi-nor: winbond: add support for w25q01jv-im
Date: Thu, 6 Oct 2022 15:26:56 -0500 [thread overview]
Message-ID: <Yz86ECK3pRyJjAo5@heinlein> (raw)
In-Reply-To: <0dde4fa6ddeefa23314dbdcd1dd1b28b@walle.cc>
[-- Attachment #1.1: Type: text/plain, Size: 1477 bytes --]
On Thu, Oct 06, 2022 at 01:52:33PM +0200, Michael Walle wrote:
> Hi,
>
> Am 2022-10-06 09:08, schrieb Delphine CC Chiu:
> > Add support for winbond w25q01jv-im chip.
> >
> > Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@Wiwynn.com>
> > ---
> > drivers/mtd/spi-nor/winbond.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/mtd/spi-nor/winbond.c
> > b/drivers/mtd/spi-nor/winbond.c
> > index ffaa24055259..2b02b05ceb0a 100644
> > --- a/drivers/mtd/spi-nor/winbond.c
> > +++ b/drivers/mtd/spi-nor/winbond.c
> > @@ -139,6 +139,9 @@ static const struct flash_info winbond_nor_parts[]
> > = {
> > { "w25q512jvq", INFO(0xef4020, 0, 64 * 1024, 1024)
> > NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ |
> > SPI_NOR_QUAD_READ) },
> > + { "w25q01jv-im", INFO(0xef7021, 0, 64 * 1024, 2048)
>
> The name should be w25q01jvm.
>
> > + NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ |
> > + SPI_NOR_QUAD_READ) },
>
> That flash should support SFDP, so please try the following:
> + { "w25q01jvm", INFO(0xef7021, 0, 0, 0) PARSE_SFDP },
>
> Also, we require an SFDP dump for new flash submissions, see [1].
>
> -michael
>
> [1]
> https://lore.kernel.org/linux-mtd/4304e19f3399a0a6e856119d01ccabe0@walle.cc/
It looks like this was already attempted to be added:
https://lore.kernel.org/all/20220222085148.21594-1-potin.lai@quantatw.com/
Potin, do you have an update?
--
Patrick Williams
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 144 bytes --]
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-10-06 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 7:08 [PATCH] mtd: spi-nor: winbond: add support for w25q01jv-im Delphine CC Chiu
2022-10-06 11:52 ` Michael Walle
2022-10-06 20:26 ` Patrick Williams [this message]
2022-10-06 20:40 ` Patrick Williams
2022-10-06 23:04 ` Patrick Williams
-- strict thread matches above, loose matches on Subject: below --
2022-10-06 7:38 Delphine CC Chiu
2022-10-06 7:39 Delphine CC Chiu
2022-10-07 5:21 Delphine CC Chiu
2022-11-21 13:58 ` 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=Yz86ECK3pRyJjAo5@heinlein \
--to=patrick@stwcx.xyz \
--cc=Delphine_CC_Chiu@wiwynn.com \
--cc=garnermic@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=potin.lai@quantatw.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--cc=vigneshr@ti.com \
--cc=~sircmpwn/email-test-drive@lists.sr.ht \
/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