From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] 8/16 bit support for NAND at runtime
Date: Tue, 23 Mar 2010 11:15:07 -0500 [thread overview]
Message-ID: <20100323161506.GA3412@loki.buserror.net> (raw)
In-Reply-To: <4B8F8C3F.6050703@st.com>
On Thu, Mar 04, 2010 at 04:02:31PM +0530, Vipin KUMAR wrote:
> Hi All,
>
> This query is wrt NAND 8/16 bit device support at runtime. Currently,
> the u-boot code can support only one of these at a time.
>
> Although the NAND device in itself can be recognized by reading the
> device id, the NAND controllers may need different platform specific
> initializations for different device attached.
>
> The current u-boot is written in such a way that
> 1. Initializes chip->options for a particular buswidth option
> 2. calls board_nand_init once and proceeds to read the device id
>
> Although it matches the buswidth selected through chip->options and the
> the buswidth of device id it reads and returns an error if they don't
> match, probably a better way can be to reinitialize NAND controller
> based on 16 bit device and re-read the device id.
At some point I'd like to see u-boot transition to a more flexible NAND init
such as what Linux has (nand_scan_ident/nand_scan_tail). These are actually
in u-boot now, but they're covered up by less flexible init wrapper code.
That way, it would be up to the controller driver to manage this process.
It could try different options if it wants, and only record the successful
one in nand_info[]. It could also make changes between the ident phase and
the bbt scan based on what the ident reveals, such as page size.
-Scott
prev parent reply other threads:[~2010-03-23 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 10:32 [U-Boot] 8/16 bit support for NAND at runtime Vipin KUMAR
2010-03-04 12:28 ` Wolfgang Denk
2010-03-05 4:42 ` Vipin KUMAR
2010-03-21 16:50 ` Wolfgang Denk
2010-03-23 5:42 ` Swarthout Edward L-SWARTHOU
2010-03-23 5:54 ` Vipin KUMAR
2010-03-23 16:15 ` 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=20100323161506.GA3412@loki.buserror.net \
--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