From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] mtd: nand: omap_gpmc: Add CONFIG_SYS_NAND_USE_READY to enable ready/busy
Date: Wed, 12 Nov 2014 16:34:24 -0500 [thread overview]
Message-ID: <20141112213424.GI24724@bill-the-cat> (raw)
In-Reply-To: <1415789592-5192-1-git-send-email-sr@denx.de>
On Wed, Nov 12, 2014 at 11:53:11AM +0100, Stefan Roese wrote:
> By defining CONFIG_SYS_NAND_USE_READY the GPMC NAND driver makes
> use of the ready pin / signal for busy / ready detection. This function
> is already available but currently only used in SPL. I don't see a reason
> to not use it in the main U-Boot as well. As it increases the NAND
> performance.
>
> I'm making it configurable, so that boards that might now have this pin
> connected are still supported.
I don't think we need to make this configurable. I think it's always
been an oversight since we've always done this in NAND for SPL and I
can't think of any boards that do support NAND but don't support booting
from NAND in U-Boot.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141112/1a230617/attachment.pgp>
prev parent reply other threads:[~2014-11-12 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 10:53 [U-Boot] [PATCH 1/2] mtd: nand: omap_gpmc: Add CONFIG_SYS_NAND_USE_READY to enable ready/busy Stefan Roese
2014-11-12 10:53 ` [U-Boot] [PATCH 2/2] arm: am335x: Enable CONFIG_SYS_NAND_USE_READY on siemens am33xx Stefan Roese
2014-11-12 20:54 ` [U-Boot] [PATCH 1/2] mtd: nand: omap_gpmc: Add CONFIG_SYS_NAND_USE_READY to enable ready/busy Scott Wood
2014-11-12 21:34 ` Tom Rini [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=20141112213424.GI24724@bill-the-cat \
--to=trini@ti.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