From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 4/7] tegra: fdt: Add NAND controller binding and definitions
Date: Tue, 17 Apr 2012 13:38:33 -0500 [thread overview]
Message-ID: <4F8DB8A9.4060506@freescale.com> (raw)
In-Reply-To: <CAPnjgZ1uXbLUtMTXd5siZsKSF5m3BZGRtkGiEYhK+PQO1PbpNQ@mail.gmail.com>
On 04/17/2012 01:33 PM, Simon Glass wrote:
> Hi Stephen,
>
> On Fri, Apr 13, 2012 at 2:05 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 04/13/2012 12:29 PM, Simon Glass wrote:
>>> +nand-controller at 0x70008000 {
>>> + compatible = "nvidia,tegra20-nand";
>>> + wp-gpios = <&gpio 59 0>; /* PH3 */
>>> + nvidia,width = <8>;
>>> + nvidia,timing = <26 100 20 80 20 10 12 10 70>;
>>> + nand at 0 {
>>> + compatible = "hynix,hy27uf4g2b", "nand-flash";
>>
>> The TRM says there can be up to 8 chip selects. Don't the NAND device
>> sub-nodes need a reg property to indicate which chip-select they're on?
>
> We don't have driver support for this at present.
That shouldn't matter. The device tree is about describing the
hardware. Ideally the device tree shouldn't have to change if in the
future you do get driver support for it.
Also, unit addresses should only be present if reg is present, and they
should match.
-Scott
next prev parent reply other threads:[~2012-04-17 18:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 18:29 [U-Boot] [PATCH v2 0/7] tegra: Add NAND flash support Simon Glass
2012-04-13 18:29 ` [U-Boot] [PATCH v2 1/7] nand: Try to align the default buffers Simon Glass
2012-04-13 18:37 ` Scott Wood
2012-04-13 18:52 ` Simon Glass
2012-04-13 19:17 ` Scott Wood
2012-04-13 19:24 ` Simon Glass
2012-04-13 18:29 ` [U-Boot] [PATCH v2 2/7] fdt: Add debugging to fdtdec_get_int/addr() Simon Glass
2012-04-13 18:29 ` [U-Boot] [PATCH v2 3/7] tegra: Add NAND support to funcmux Simon Glass
2012-04-13 18:29 ` [U-Boot] [PATCH v2 4/7] tegra: fdt: Add NAND controller binding and definitions Simon Glass
2012-04-13 18:43 ` Scott Wood
2012-04-13 19:01 ` Simon Glass
2012-04-13 19:07 ` Scott Wood
2012-04-13 19:16 ` Simon Glass
2012-04-13 20:58 ` Stephen Warren
2012-04-13 21:21 ` Scott Wood
2012-04-13 21:22 ` Stephen Warren
2012-04-13 21:56 ` Scott Wood
2012-04-13 21:05 ` Stephen Warren
2012-04-13 21:12 ` Scott Wood
2012-04-17 18:33 ` Simon Glass
2012-04-17 18:38 ` Scott Wood [this message]
2012-04-17 18:44 ` Simon Glass
2012-04-17 18:45 ` Scott Wood
2012-04-17 18:47 ` Simon Glass
2012-04-13 18:29 ` [U-Boot] [PATCH v2 5/7] tegra: fdt: Add NAND definitions to fdt Simon Glass
2012-04-13 18:29 ` [U-Boot] [PATCH v2 6/7] tegra: nand: Add Tegra NAND driver Simon Glass
2012-04-13 18:29 ` [U-Boot] [PATCH v2 7/7] tegra: Enable NAND on Seaboard Simon Glass
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=4F8DB8A9.4060506@freescale.com \
--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