From: Nick Thompson <nick.thompson@gefanuc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] Davinci: Configurable NAND chip selects
Date: Thu, 03 Dec 2009 11:11:46 +0000 [thread overview]
Message-ID: <4B179CF2.9050907@gefanuc.com> (raw)
In-Reply-To: <4B052092.7050008@gefanuc.com>
On 19/11/09 10:40, Nick Thompson wrote:
> Davinci: Configurable NAND chip selects
>
> Add a CONFIG_SYS_NAND_CS setting to all davinci configs and
> use it to setup the NAND controller in the davinci_nand
> mtd driver.
>
> Signed-off-by: Nick Thompson <nick.thompson@gefanuc.com>
Hi Sandeep,
Scott ack'ed v1 of this patch with a minor change (made to v2),
but you asked for testing time as it impacts all Davinci
boards. Do you have any feedback? I've done extensive tests on
da830evm and things are working well.
I'd like to submit da830 NAND support, but it's waiting on this
and the table driven pinmux patch.
I've also got a few performance enhancements lined up for
davinci_nand.c which roughly double the speed of NAND reads on
da830 and ought to work well on the rest of Davinci - more
testing for you :)
Thanks,
Nick.
prev parent reply other threads:[~2009-12-03 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 10:40 [U-Boot] [PATCH v2] Davinci: Configurable NAND chip selects Nick Thompson
2009-12-03 11:11 ` Nick Thompson [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=4B179CF2.9050907@gefanuc.com \
--to=nick.thompson@gefanuc.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