public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dhananjay Phadke <dphadke@linux.microsoft.com>
To: Angus Ainslie <angus@akkea.ca>, Jagan Teki <jagan@amarulasolutions.com>
Cc: Vignesh R <vigneshr@ti.com>, u-boot@lists.denx.de, kernel@puri.sm
Subject: Re: [PATCH v2] drivers: spi-nor: Add JEDEC id for W25Q16JV
Date: Thu, 13 Jan 2022 10:30:10 -0800	[thread overview]
Message-ID: <a29a59b2-3323-8944-803c-ba115f3caee9@linux.microsoft.com> (raw)
In-Reply-To: <20220113171726.1669216-1-angus@akkea.ca>

On 1/13/2022 9:17 AM, Angus Ainslie wrote:
> Add a JEDEC id for the Winbond W25Q16JV 16M-BIT serial flash memory with
> DUAL/QUAD SPI
> 
> Changes since v1:
> 
> Updated the name for more suffixes
> 
> Signed-off-by: Angus Ainslie <angus@akkea.ca>
> ---
>   drivers/mtd/spi/spi-nor-ids.c | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/drivers/mtd/spi/spi-nor-ids.c b/drivers/mtd/spi/spi-nor-ids.c
> index b551ebd75e..3bd0ded443 100644
> --- a/drivers/mtd/spi/spi-nor-ids.c
> +++ b/drivers/mtd/spi/spi-nor-ids.c
> @@ -314,6 +314,11 @@ const struct flash_info spi_nor_ids[] = {
>   			SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ |
>   			SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB)
>   	},
> +	{
> +		INFO("w25q16jv-im/jm", 0xef7015, 0, 64 * 1024,  32,
> +			SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ |
> +			SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB)
> +	},

Shouldn't this be w25q16jvm, which seems to be unofficial convention for
*-DTR parts? I was looking for naming convention for another Winbond part -

https://lore.kernel.org/u-boot/0c3e4727-0997-a4c5-dab1-b09ea8781c72@linux.microsoft.com/

>   	{
>   		INFO("w25q32jv", 0xef7016, 0, 64 * 1024,  64,
>   			SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ |


  reply	other threads:[~2022-01-13 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 17:17 [PATCH v2] drivers: spi-nor: Add JEDEC id for W25Q16JV Angus Ainslie
2022-01-13 18:30 ` Dhananjay Phadke [this message]
2022-01-14 14:04   ` Angus Ainslie
2022-01-15 20:45     ` Dhananjay Phadke

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=a29a59b2-3323-8944-803c-ba115f3caee9@linux.microsoft.com \
    --to=dphadke@linux.microsoft.com \
    --cc=angus@akkea.ca \
    --cc=jagan@amarulasolutions.com \
    --cc=kernel@puri.sm \
    --cc=u-boot@lists.denx.de \
    --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