public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] mtd: nand: Introduce CONFIG_SYS_NAND_BUSWIDTH_16BIT
Date: Tue, 26 Feb 2013 12:22:54 -0600	[thread overview]
Message-ID: <1361902974.12570.0@snotra> (raw)
In-Reply-To: <1361902622-26774-1-git-send-email-fabio.estevam@freescale.com> (from fabio.estevam@freescale.com on Tue Feb 26 12:17:01 2013)

On 02/26/2013 12:17:01 PM, Fabio Estevam wrote:
> Introduce CONFIG_SYS_NAND_BUSWIDTH_16BIT option so that any NAND  
> controller
> driver could use it when a 16-bit NAND is deployed.
> 
> drivers/mtd/nand/ndfc has CONFIG_SYS_NDFC_16BIT, so just rename it,  
> so that
> other NAND drivers could reuse the same symbol.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
>  README                  |    6 +++---
>  drivers/mtd/nand/ndfc.c |    4 ++--
>  2 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/README b/README
> index d8cb394..1e265c9 100644
> --- a/README
> +++ b/README
> @@ -3713,9 +3713,9 @@ Low Level (hardware related) configuration  
> options:
>  - CONFIG_SYS_SRIOn_MEM_SIZE:
>  		Size of SRIO port 'n' memory region
> 
> -- CONFIG_SYS_NDFC_16
> -		Defined to tell the NDFC that the NAND chip is using a
> -		16 bit bus.
> +- CONFIG_SYS_NAND_BUSWIDTH_16BIT
> +		Defined to tell the NAND controller that the NAND chip  
> is using
> + 		a 16 bit bus.

Mention here that not all drivers use this symbol, and provide a list  
of those that do.

E.g. on fsl_ifc, we already have this information elsewhere on a  
per-chip basis.

-Scott

      parent reply	other threads:[~2013-02-26 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 18:17 [U-Boot] [PATCH 1/2] mtd: nand: Introduce CONFIG_SYS_NAND_BUSWIDTH_16BIT Fabio Estevam
2013-02-26 18:17 ` [U-Boot] [PATCH 2/2] mtd: nand: mxc_nand: Fix is_16bit_nand() Fabio Estevam
2013-02-26 18:22 ` Scott Wood [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=1361902974.12570.0@snotra \
    --to=scottwood@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox