linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Johannes Poehlmann <johannes.poehlmann@izt-labs.de>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH] new NOR flash winbond w25q16jv, jedec code 0xef7015
Date: Sun, 27 May 2018 14:49:35 +0200	[thread overview]
Message-ID: <d98357d1-7cdd-2a01-e1d9-06dbe3be9e36@gmail.com> (raw)
In-Reply-To: <20180525144811.GA27270@ppcx2.izt.loc>

On 05/25/2018 04:48 PM, Johannes Poehlmann wrote:
> Copy values from jedec code 0xef4015, which is also the jedec code
> of Winbond w25q16db. w25q16jv is presented as follow up type in the
> data sheet. w25q16jv works with this patch.
> 
> Signed-off-by: Johannes Poehlmann <johannes.poehlmann@izt-labs.de>
> ---
>  drivers/mtd/spi-nor/spi-nor.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
> index 5bfa36e..9bac67b 100644
> --- a/drivers/mtd/spi-nor/spi-nor.c
> +++ b/drivers/mtd/spi-nor/spi-nor.c
> @@ -1188,6 +1188,7 @@ static 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)
>  	},
> +	{ "w25q16jv", INFO(0xef7015, 0, 64 * 1024,  32, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },

What about HAS_LOCK and HAS_TB ? Looks good otherwise.

>  	{ "w25x32", INFO(0xef3016, 0, 64 * 1024,  64, SECT_4K) },
>  	{ "w25q20cl", INFO(0xef4012, 0, 64 * 1024,  4, SECT_4K) },
>  	{ "w25q20bw", INFO(0xef5012, 0, 64 * 1024,  4, SECT_4K) },
> 


-- 
Best regards,
Marek Vasut

      reply	other threads:[~2018-05-27 14:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 14:48 [PATCH] new NOR flash winbond w25q16jv, jedec code 0xef7015 Johannes Poehlmann
2018-05-27 12:49 ` Marek Vasut [this message]

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=d98357d1-7cdd-2a01-e1d9-06dbe3be9e36@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=johannes.poehlmann@izt-labs.de \
    --cc=linux-mtd@lists.infradead.org \
    /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).