From: Michael Walle <michael@walle.cc> To: Dhananjay Phadke <dphadke@linux.microsoft.com> Cc: Tudor Ambarus <tudor.ambarus@microchip.com>, Pratyush Yadav <p.yadav@ti.com>, 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: Add support for w25q512jvm Date: Mon, 10 Jan 2022 16:10:22 +0100 [thread overview] Message-ID: <262a03e185c29583450180e3dc8c4e6c@walle.cc> (raw) In-Reply-To: <20220109044418.4657-1-dphadke@linux.microsoft.com> Hi, Am 2022-01-09 05:44, schrieb Dhananjay Phadke: > Add support for Winbond 64MB W25Q512JV-DTR NOR flash. > Use PARSE_SFDP flag to init parameters during SFDP parsing. > > Signed-off-by: Dhananjay Phadke <dphadke@linux.microsoft.com> > --- > drivers/mtd/spi-nor/winbond.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/mtd/spi-nor/winbond.c > b/drivers/mtd/spi-nor/winbond.c > index 675f32c136b3..ebc826e21f76 100644 > --- a/drivers/mtd/spi-nor/winbond.c > +++ b/drivers/mtd/spi-nor/winbond.c > @@ -118,6 +118,8 @@ static const struct flash_info winbond_parts[] = { > .fixups = &w25q256_fixups }, > { "w25q256jvm", INFO(0xef7019, 0, 64 * 1024, 512) > PARSE_SFDP }, > + { "w25q512jvm", INFO(0xef7020, 0, 64 * 1024, 1024), OTP_INFO(256, 3, 0x1000, 0x1000) should enable OTP support, could you please test this using the flash_otp_{dump,info,erase,write} tools and add that line? > + PARSE_SFDP }, > { "w25q256jw", INFO(0xef6019, 0, 64 * 1024, 512) > NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ | > SPI_NOR_QUAD_READ) }, -michael
WARNING: multiple messages have this Message-ID (diff)
From: Michael Walle <michael@walle.cc> To: Dhananjay Phadke <dphadke@linux.microsoft.com> Cc: Tudor Ambarus <tudor.ambarus@microchip.com>, Pratyush Yadav <p.yadav@ti.com>, 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: Add support for w25q512jvm Date: Mon, 10 Jan 2022 16:10:22 +0100 [thread overview] Message-ID: <262a03e185c29583450180e3dc8c4e6c@walle.cc> (raw) In-Reply-To: <20220109044418.4657-1-dphadke@linux.microsoft.com> Hi, Am 2022-01-09 05:44, schrieb Dhananjay Phadke: > Add support for Winbond 64MB W25Q512JV-DTR NOR flash. > Use PARSE_SFDP flag to init parameters during SFDP parsing. > > Signed-off-by: Dhananjay Phadke <dphadke@linux.microsoft.com> > --- > drivers/mtd/spi-nor/winbond.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/mtd/spi-nor/winbond.c > b/drivers/mtd/spi-nor/winbond.c > index 675f32c136b3..ebc826e21f76 100644 > --- a/drivers/mtd/spi-nor/winbond.c > +++ b/drivers/mtd/spi-nor/winbond.c > @@ -118,6 +118,8 @@ static const struct flash_info winbond_parts[] = { > .fixups = &w25q256_fixups }, > { "w25q256jvm", INFO(0xef7019, 0, 64 * 1024, 512) > PARSE_SFDP }, > + { "w25q512jvm", INFO(0xef7020, 0, 64 * 1024, 1024), OTP_INFO(256, 3, 0x1000, 0x1000) should enable OTP support, could you please test this using the flash_otp_{dump,info,erase,write} tools and add that line? > + PARSE_SFDP }, > { "w25q256jw", INFO(0xef6019, 0, 64 * 1024, 512) > NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ | > SPI_NOR_QUAD_READ) }, -michael ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-01-10 15:10 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-09 4:44 [PATCH] mtd: spi-nor: Add support for w25q512jvm Dhananjay Phadke 2022-01-09 4:44 ` Dhananjay Phadke 2022-01-10 0:24 ` kernel test robot 2022-01-10 1:45 ` kernel test robot 2022-01-10 1:45 ` kernel test robot 2022-01-10 5:07 ` Pratyush Yadav 2022-01-10 5:07 ` Pratyush Yadav 2022-01-10 15:10 ` Michael Walle [this message] 2022-01-10 15:10 ` Michael Walle 2022-01-10 23:12 ` Dhananjay Phadke 2022-01-10 23:12 ` Dhananjay Phadke 2022-01-11 5:51 ` Pratyush Yadav 2022-01-11 5:51 ` Pratyush Yadav
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=262a03e185c29583450180e3dc8c4e6c@walle.cc \ --to=michael@walle.cc \ --cc=dphadke@linux.microsoft.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=miquel.raynal@bootlin.com \ --cc=p.yadav@ti.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.