From: Doug Anderson <dianders@chromium.org>
To: Shaik Sajida Bhanu <quic_c_sbhanu@quicinc.com>
Cc: tudor.ambarus@microchip.com, michael@walle.cc, p.yadav@ti.com,
miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
stummala@codeaurora.org, vbadigan@codeaurora.org,
quic_rampraka@quicinc.com, quic_pragalla@quicinc.com,
sartgarg@codeaurora.org
Subject: Re: [PATCH V2] mtd: spi-nor: winbond: Add support for winbond chip
Date: Mon, 13 Dec 2021 07:52:24 -0800 [thread overview]
Message-ID: <CAD=FV=VB6hsEHEb8yZmB=xA__47p4vC6dBc528RV37dvAKTgOQ@mail.gmail.com> (raw)
In-Reply-To: <1638427092-9139-1-git-send-email-quic_c_sbhanu@quicinc.com>
Hi,
On Wed, Dec 1, 2021 at 10:38 PM Shaik Sajida Bhanu
<quic_c_sbhanu@quicinc.com> wrote:
>
> Add support for winbond W25Q512NW-IM chip.
>
> Signed-off-by: Shaik Sajida Bhanu <quic_c_sbhanu@quicinc.com>
> ---
> Changes since V1:
> Added space before name of the flash part as suggested by Doug.
When someone comments on V1, it's nice to CC them on V2. ;-)
> ---
> 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 96573f6..44f19f2 100644
> --- a/drivers/mtd/spi-nor/winbond.c
> +++ b/drivers/mtd/spi-nor/winbond.c
> @@ -100,6 +100,9 @@ static const struct flash_info winbond_parts[] = {
> SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
> { "w25m512jv", INFO(0xef7119, 0, 64 * 1024, 1024,
> SECT_4K | SPI_NOR_QUAD_READ | SPI_NOR_DUAL_READ) },
> + { "w25q512nw", INFO(0xef8020, 0, 64 * 1024, 1024,
> + SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ |
> + SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB) },
I had a quick look. Though I'm no expert on this driver, I believe
that the name should be "w25q512nwm", not "w25q512nw" (you need an "m"
at the end). Evidence:
The Winbond doc [1] shows:
W25Q512NW-IM is 0xef8020
W25Q512NW-IQ/IN is 0xef6020
Comparing to a different datasheet [2], I see that:
W25Q256JW-IM is 0xef8019
W25Q256JW is 0xef6019
Since "W25Q256JW-IM" is in code as "w25q256jwm" it implies to me that
for the "-IM" suffix you just add a "m" to the end of the name.
[1] https://www.winbond.com/resource-files/W25Q512NW%20RevB%2007192021.pdf
[2] https://www.winbond.com/resource-files/W25Q256JW%20SPI%20RevJ%2003102021%20Plus.pdf
After changing the name, feel free to add my Reviewed-by (and please
CC me on v3).
-Doug
next prev parent reply other threads:[~2021-12-13 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 6:38 [PATCH V2] mtd: spi-nor: winbond: Add support for winbond chip Shaik Sajida Bhanu
2021-12-13 15:52 ` Doug Anderson [this message]
2021-12-13 16:58 ` Sajida Bhanu (Temp)
2021-12-13 17:22 ` Sajida Bhanu (Temp) (QUIC)
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='CAD=FV=VB6hsEHEb8yZmB=xA__47p4vC6dBc528RV37dvAKTgOQ@mail.gmail.com' \
--to=dianders@chromium.org \
--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=quic_c_sbhanu@quicinc.com \
--cc=quic_pragalla@quicinc.com \
--cc=quic_rampraka@quicinc.com \
--cc=richard@nod.at \
--cc=sartgarg@codeaurora.org \
--cc=stummala@codeaurora.org \
--cc=tudor.ambarus@microchip.com \
--cc=vbadigan@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).