From: Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jaedon Shin <jaedon.shin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Ralf Baechle <ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>
Cc: Kevin Cernekee <cernekee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH 1/4] MIPS: BMIPS: bcm7346: add nodes for NAND
Date: Wed, 24 Jun 2015 12:32:07 -0700 [thread overview]
Message-ID: <558B05B7.8010401@gmail.com> (raw)
In-Reply-To: <1544bf6110b43fbaa8dbb3b06a18e08ae87b386d.1435124524.git.jaedon.shin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
+Brian,
On 23/06/15 23:08, Jaedon Shin wrote:
> Add NAND device nodes to BMIPS based BCM7346 platform.
>
> Signed-off-by: Jaedon Shin <jaedon.shin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
[snip]
> +
> +&nand0 {
> + status = "okay";
> +
> + nandcs@1 {
> + compatible = "brcm,nandcs";
> + reg = <1>;
> + nand-ecc-step-size = <512>;
> + nand-ecc-strength = <8>;
> + nand-on-flash-bbt;
> +
> + #size-cells = <2>;
> + #address-cells = <2>;
> +
> + flash1.rootfs0@0 {
> + reg = <0x0 0x0 0x0 0x80000000>;
> + };
> +
> + flash1.rootfs1@80000000 {
> + reg = <0x0 0x80000000 0x0 0x80000000>;
> + };
> + };
> +};
Should we create something like brcmnand-cs1-512-8 to reduce the amount
of duplication between DTS files?
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-24 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 6:08 [PATCH 0/4] MIPS: BMIPS: dts: add NAND device nodes for bcm7xxx platforms Jaedon Shin
[not found] ` <cover.1435124524.git.jaedon.shin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-06-24 6:08 ` [PATCH 1/4] MIPS: BMIPS: bcm7346: add nodes for NAND Jaedon Shin
[not found] ` <1544bf6110b43fbaa8dbb3b06a18e08ae87b386d.1435124524.git.jaedon.shin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-06-24 19:32 ` Florian Fainelli [this message]
[not found] ` <558B05B7.8010401-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-06-25 8:52 ` Jaedon Shin
[not found] ` <EFAFA0BE-CC2F-4342-9C89-DED8EC6CF377-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-06-26 3:00 ` Florian Fainelli
[not found] ` <558CC050.6040101-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-06-26 13:54 ` Jaedon Shin
[not found] ` <D85A0C84-46BA-4F77-9A90-DE21EBED1887-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-06-26 16:32 ` Florian Fainelli
2015-06-24 6:08 ` [PATCH 2/4] MIPS: BMIPS: bcm7358: " Jaedon Shin
2015-06-24 6:08 ` [PATCH 3/4] MIPS: BMIPS: bcm7360: " Jaedon Shin
2015-06-24 6:08 ` [PATCH 4/4] MIPS: BMIPS: bcm7362: " Jaedon Shin
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=558B05B7.8010401@gmail.com \
--to=f.fainelli-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=cernekee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jaedon.shin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org \
--cc=ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.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).