From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, kumar.gala@freescale.com
Subject: Re: [PATCH 2/2] powerpc/85xx: add a 32-bit P1022DS device tree
Date: Fri, 2 Dec 2011 16:19:33 -0600 [thread overview]
Message-ID: <4ED94EF5.2090406@freescale.com> (raw)
In-Reply-To: <1322863714-6818-2-git-send-email-timur@freescale.com>
On 12/02/2011 04:08 PM, Timur Tabi wrote:
> + lbc: localbus@ffe05000 {
> + reg = <0x0 0xffe05000 0 0x1000>;
> + ranges = <0x0 0x0 0x0 0xe8000000 0x08000000
> + 0x1 0x0 0x0 0xe0000000 0x08000000
> + 0x2 0x0 0x0 0xff800000 0x00040000
> + 0x3 0x0 0x0 0xffdf0000 0x00008000>;
> +
> + /*
> + * This node is used to access the pixis via "indirect" mode,
> + * which is done by writing the pixis register index to chip
> + * select 0 and the value to/from chip select 1. Indirect
> + * mode is the only way to access the pixis when DIU video
> + * is enabled. Note that this assumes that the first column
> + * of the 'ranges' property above is the chip select number.
> + */
> + board-control@0,0 {
> + compatible = "fsl,p1022ds-indirect-pixis";
> + reg = <0x0 0x0 1 /* CS0 */
> + 0x1 0x0 1>; /* CS1 */
> + };
> +
> + nor@0,0 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + compatible = "cfi-flash";
> + reg = <0x0 0x0 0x8000000>;
> + bank-width = <2>;
> + device-width = <1>;
[snip]
> + };
> +
> + nand@2,0 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + compatible = "fsl,elbc-fcm-nand";
> + reg = <0x2 0x0 0x40000>;
[snip]
> + };
> + };
> +
> + board-control@3,0 {
> + compatible = "fsl,p1022ds-fpga", "fsl,fpga-ngpixis";
> + reg = <3 0 0x30>;
> + interrupt-parent = <&mpic>;
> + /*
> + * IRQ8 is generated if the "EVENT" switch is pressed
> + * and PX_CTL[EVESEL] is set to 00.
> + */
> + interrupts = <8 8 0 0>;
> + };
> + };
[snip]
> +/include/ "fsl/p1022si-post.dtsi"
Please add something after post to strip simple-bus off of the localbus
node's compatible. Either you have board-control@0,0, or you have the
other stuff (did you ever find out what the situation with NAND is?) --
not both at the same time. Or do you have U-Boot patching in status
updates now?
I realize this isn't a 32-bit versus 36-bit issue, but this seemed as
good a time as any to repeat this complaint. :-)
-Scott
next prev parent reply other threads:[~2011-12-02 22:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 22:08 [PATCH 1/2] powerpc/85xx: fix localbus and PCI addresses in the P1022DS 36-bit device tree Timur Tabi
2011-12-02 22:08 ` [PATCH 2/2] powerpc/85xx: add a 32-bit P1022DS " Timur Tabi
2011-12-02 22:19 ` Scott Wood [this message]
2011-12-02 22:24 ` Timur Tabi
2011-12-02 22:34 ` Scott Wood
2011-12-02 23:41 ` Timur Tabi
2011-12-02 23:50 ` Scott Wood
2011-12-02 23:03 ` Kumar Gala
2011-12-05 23:44 ` Timur Tabi
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=4ED94EF5.2090406@freescale.com \
--to=scottwood@freescale.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).