From: <Tudor.Ambarus@microchip.com>
To: <quic_c_sbhanu@quicinc.com>, <dianders@chromium.org>,
<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>
Cc: <stummala@codeaurora.org>, <vbadigan@codeaurora.org>,
<quic_rampraka@quicinc.com>, <quic_pragalla@quicinc.com>,
<sartgarg@codeaurora.org>
Subject: Re: [PATCH V3] mtd: spi-nor: winbond: Add support for winbond chip
Date: Tue, 14 Dec 2021 11:16:19 +0000 [thread overview]
Message-ID: <488aafc3-2fa9-198b-c448-d1ca7ef52f35@microchip.com> (raw)
In-Reply-To: <1639476991-25676-1-git-send-email-quic_c_sbhanu@quicinc.com>
On 12/14/21 12:16 PM, Shaik Sajida Bhanu wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Add support for winbond W25Q512NW-IM chip.
>
> Signed-off-by: Shaik Sajida Bhanu <quic_c_sbhanu@quicinc.com>
> Reviewed-by: Doug Anderson <dianders@chromium.org>
> ---
> Changes since V1:
> Added space before name of the flash part as suggested by Doug.
>
> Changes since V2:
> Updated chip name as w25q512nwm as suggested by Doug.
> ---
> 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..42d5800 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) },
This does not apply on current spi-nor/next. We've changed how the
flash_info flags are handled. We also require to dump the SPI NOR
sysfs entries under the comment section ---. I'll update the
documentation to add some guidelines on how new flash additions or
flash updates should be proposed. Sometime this week, or maybe
next.
Cheers,
ta
next prev parent reply other threads:[~2021-12-14 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 10:16 Shaik Sajida Bhanu
2021-12-14 11:16 ` Tudor.Ambarus [this message]
2022-01-19 5:34 ` Sajida Bhanu (Temp)
2022-01-19 15:51 ` Michael Walle
2022-01-20 6:45 ` 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=488aafc3-2fa9-198b-c448-d1ca7ef52f35@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=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=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
all inboxes | Powered by JetHome®