U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH v2 1/2] Add GigaDevice gd25q128 128Mbit chip to spi-nor id table.
Date: Tue, 7 Jan 2020 14:10:47 +0100	[thread overview]
Message-ID: <08a17bda-9fe9-36b1-ca3e-cea159c7735e@denx.de> (raw)
In-Reply-To: <20191227132515.15869-1-mc5686@mclink.it>

Hi Mauro,

On 27.12.19 14:25, Mauro Condarelli wrote:
> From: MCon <mc5686@mclink.it>
> 
> Tested on VoCore2
> 
> Signed-off-by: MCon <mc5686@mclink.it>
> Signed-off-by: Mauro Condarelli <mc5686@mclink.it>
> ---
> 
> Changes in v2: None
> 
>   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 d3b84574ac..973b6f86c9 100644
> --- a/drivers/mtd/spi/spi-nor-ids.c
> +++ b/drivers/mtd/spi/spi-nor-ids.c
> @@ -107,6 +107,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("gd25q128", 0xc84018, 0, 64 * 1024, 256,
> +			SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ |
> +			SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB)
> +	},
>   	{
>   		INFO("gd25lq128", 0xc86018, 0, 64 * 1024, 256,
>   			SECT_4K | SPI_NOR_DUAL_READ |
> 

You can drop this patch. The support for this SPI NOR is now included
in mainline.

Thanks,
Stefan

      parent reply	other threads:[~2020-01-07 13:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27 13:25 [PATCH v2 1/2] Add GigaDevice gd25q128 128Mbit chip to spi-nor id table Mauro Condarelli
2019-12-27 13:25 ` [PATCH v2 2/2] Port to new board "VoCore2" Mauro Condarelli
2020-01-07 13:21   ` Stefan Roese
2020-01-07 14:30     ` Mauro Condarelli
2020-01-07 15:58       ` Daniel Schwierzeck
2020-01-07 17:43         ` Mauro Condarelli
2020-01-08 13:37           ` Daniel Schwierzeck
2020-01-09  9:16             ` Weijie Gao
2020-01-09  6:48       ` Stefan Roese
2020-01-07 13:10 ` Stefan Roese [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=08a17bda-9fe9-36b1-ca3e-cea159c7735e@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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