From: Scott Wood <scottwood@freescale.com>
To: Priyanka Jain <b32167@rhuath.am.freescale.net>
Cc: <linuxppc-dev@lists.ozlabs.org>,
Priyanka Jain <Priyanka.Jain@freescale.com>
Subject: Re: [PATCH] powerpc/fsl-booke: Add T1040D4RDB/T1042D4RDB board support
Date: Mon, 13 Jul 2015 15:39:19 -0500 [thread overview]
Message-ID: <1436819959.2993.16.camel@freescale.com> (raw)
In-Reply-To: <1436680032-24147-1-git-send-email-b32167@rhuath.am.freescale.net>
On Sun, 2015-07-12 at 00:47 -0500, Priyanka Jain wrote:
> +/ {
> + model = "fsl,T1040D4RDB";
> + compatible = "fsl,T1040D4RDB";
> + #address-cells = <2>;
> + #size-cells = <2>;
> + interrupt-parent = <&mpic>;
> +
> + ifc: localbus@ffe124000{
> + cpld@3,0 {
> + compatible = "fsl,t1040d4rdb-cpld",
> + "fsl,deepsleep-cpld";
> + };
> + };
> +};
What is "fsl,deepsleep-cpld"? Besides the lack of a binding, it seems too
vague. Not all deep sleep capable CPLDs are necessarily going to be
identical.
> + ifc: localbus@ffe124000{
> + reg = <0xf 0xfe124000 0 0x2000>;
> + ranges = <0 0 0xf 0xe8000000 0x08000000
> + 2 0 0xf 0xff800000 0x00010000
> + 3 0 0xf 0xffdf0000 0x00008000>;
> +
> + nor@0,0 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + compatible = "cfi-flash";
> + reg = <0x0 0x0 0x8000000>;
> + bank-width = <2>;
> + device-width = <1>;
> + };
> +
> + nand@2,0 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + compatible = "fsl,ifc-nand";
> + reg = <0x2 0x0 0x10000>;
> + };
> +
> + cpld@3,0 {
> + reg = <3 0 0x300>;
> + };
I'd rather keep reg with the compatible.
> + adt7461@4c{
> + compatible = "adi,adt7461";
> + reg = <0x4c>;
> + };
Node names should be generic.
> + i2c@118100{
> + pca9546@77{
> + compatible = "nxp,pca9546";
> + reg = <0x77>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + };
Likewise.
-Scott
prev parent reply other threads:[~2015-07-13 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 5:47 [PATCH] powerpc/fsl-booke: Add T1040D4RDB/T1042D4RDB board support Priyanka Jain
2015-07-13 20:39 ` 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=1436819959.2993.16.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Priyanka.Jain@freescale.com \
--cc=b32167@rhuath.am.freescale.net \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).