From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: DTS armada: Add support for 2 more mvebu model
Date: Fri, 3 Mar 2017 21:12:16 +0100 [thread overview]
Message-ID: <20170303201216.GF1488@lunn.ch> (raw)
In-Reply-To: <CA+_ehUwrn0x8616zyAuTwkv15ERA3Dqu9ATD+P71qZyU7j3bPw@mail.gmail.com>
On Fri, Mar 03, 2017 at 07:59:51PM +0100, Ansuel Smith wrote:
> So i need to refactor the rango file and remove the extra part in the
> dts file, right?
> Also i need to create another dtsi file just for rango that use
> different flash size and gpio leds
> Wouldn't be a waste create one dtsi file just for the rango?
Please do not top post.
For the GPIO LEDs look at cobra, caiman as examples. The LEDs for
rango go in rango.dts.
The flash at d0000 node in armada-385-linksys.dtsi should be moved into
another .dtsi file, e.g. armada-385-linksys-caiman-cobra.dtsi.
So you end up with
armada-385-linksys-caiman.dts
- armada-385-linksys.dtsi
- armada-385-linksys-caiman-cobra.dtsi
armada-385-linksys-cobra.dts
- armada-385-linksys.dtsi
- armada-385-linksys-caiman-cobra.dtsi
armada-385-linksys-rango.dts
- armada-385-linksys.dtsi
Andrew
next prev parent reply other threads:[~2017-03-03 20:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 17:07 [PATCH] ARM: DTS armada: Add support for 2 more mvebu model Ansuel Smith
2017-03-03 17:07 ` Ansuel Smith
2017-03-03 17:07 ` Ansuel Smith
2017-03-03 17:26 ` Andrew Lunn
2017-03-03 17:26 ` Andrew Lunn
2017-03-03 17:26 ` Andrew Lunn
[not found] ` <CA+_ehUx0wcbfHMzPYehbEpQNu-a6vpHqHYJ4U7TY4BkzkLsRBw@mail.gmail.com>
2017-03-03 18:21 ` Andrew Lunn
[not found] ` <CA+_ehUwrn0x8616zyAuTwkv15ERA3Dqu9ATD+P71qZyU7j3bPw@mail.gmail.com>
2017-03-03 20:12 ` Andrew Lunn [this message]
2017-03-06 10:28 ` Imre Kaloz
2017-03-06 10:28 ` Imre Kaloz
2017-03-06 10:28 ` Imre Kaloz
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=20170303201216.GF1488@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.