From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v3] atmel_nand: don't require CONFIG_SYS_NAND_ENABLE_PIN
Date: Wed, 16 Mar 2011 18:45:31 -0500 [thread overview]
Message-ID: <20110316234531.GA11518@schlenkerla> (raw)
In-Reply-To: <20110315071638.GA16254@gandalf.sssup.it>
On Mon, Mar 14, 2011 at 09:16:38PM -0000, michael wrote:
> atmel_nand: don't require CONFIG_SYS_NAND_ENABLE_PIN
> If NCE is hooked up to NCS3, we don't need to (and can't)
> explicitly set the state of the NCE pin. Instead, the
> controller asserts it automatically as part of a
> command/data access. Only "CE don't care"-type NAND chips
> can be used in this manner.
>
> Signed-off-by: Michael Trimarchi <michael@amarulasolutions.com>
> Cc: Scott Wood <scottwood@freescale.com>
> Cc: Reinhard Meyer <u-boot@emk-elektronik.de>
>
> ---
> Change since V1
> - add a better description
> Change since V2:
> - change commit message
Applied to u-boot-nand-flash next, with the subject line fixed as in
this e-mail.
-Scott
prev parent reply other threads:[~2011-03-16 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 7:16 [U-Boot] [PATCH v3] This patch fix the usage of the "CE don't care"-type NAND chips Michael Trimarchi
2011-03-16 23:45 ` 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=20110316234531.GA11518@schlenkerla \
--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