All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <Peng.Fan@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2 v1] sf: Update AT45DB021D flash chip parameters
Date: Wed, 25 Mar 2015 22:11:11 +0800	[thread overview]
Message-ID: <5512C1FF.2040808@freescale.com> (raw)
In-Reply-To: <1427286985-28592-1-git-send-email-haikun.wang@freescale.com>

Hi Haikun,

On 3/25/2015 8:36 PM, Haikun Wang wrote:
> From: Haikun Wang <Haikun.Wang@freescale.com>
>
> AT45DB021D flash size is 1024*page_size, page_size is 256bytes or 264bytes.
> In current params_table its size is 64*1024*8, recorrect it.
> Add AT45DB_CMD flag for AT45DB021D.
>
> Signed-off-by: Haikun Wang <Haikun.Wang@freescale.com>
> ---
>
> Changes in v1: None
>
>   drivers/mtd/spi/sf_params.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/spi/sf_params.c b/drivers/mtd/spi/sf_params.c
> index c12e8c6..c6b68f8 100644
> --- a/drivers/mtd/spi/sf_params.c
> +++ b/drivers/mtd/spi/sf_params.c
> @@ -16,7 +16,8 @@
>   const struct spi_flash_params spi_flash_params_table[] = {
>   #ifdef CONFIG_SPI_FLASH_ATMEL		/* ATMEL */
>   	{"AT45DB011D",	   0x1f2200, 0x0,	64 * 1024,     4, RD_NORM,		    SECT_4K},
> -	{"AT45DB021D",	   0x1f2300, 0x0,	64 * 1024,     8, RD_NORM,		    SECT_4K},
> +	{"AT45DB021D",	   0x1f2300, 0x0,	64 * 1024,     4,
> +	 RD_NORM,		    AT45DB_CMD},
It's sector size is 32K, count is 8, right?
>   	{"AT45DB041D",	   0x1f2400, 0x0,	64 * 1024,     8, RD_NORM,		    SECT_4K},
>   	{"AT45DB081D",	   0x1f2500, 0x0,	64 * 1024,    16, RD_NORM,		    SECT_4K},
>   	{"AT45DB161D",	   0x1f2600, 0x0,	64 * 1024,    32, RD_NORM,		    SECT_4K},
Regards,
Peng.

  reply	other threads:[~2015-03-25 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 12:36 [U-Boot] [PATCH 2/2 v1] sf: Update AT45DB021D flash chip parameters Haikun Wang
2015-03-25 14:11 ` Peng Fan [this message]
2015-03-26  2:21   ` Haikun.Wang at freescale.com

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=5512C1FF.2040808@freescale.com \
    --to=peng.fan@freescale.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.