From: valentin.longchamp@keymile.com (Valentin Longchamp)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: kirkwood: refactor dtsi to largest common nodes
Date: Thu, 23 May 2013 15:17:52 +0200 [thread overview]
Message-ID: <519E1700.5040906@keymile.com> (raw)
In-Reply-To: <20130523114025.GO31290@titan.lakedaemon.net>
Jason,
On 05/23/2013 01:40 PM, Jason Cooper wrote:
> Valentin,
>
> On Thu, May 23, 2013 at 11:25:30AM +0200, Valentin Longchamp wrote:
>> Some kirkwood variants (for instance present in the prestera SoCs) do
>> not have all the peripherals whose nodes are initialized in the
>> kirkwood.dtsi. These missing peripherals are SATA, SDIO, and RTC.
>
> Could you provide a little more detail here about the exact problem this
> is solving?
Sure, I will add more detail.
>
>> Their corresponding nodes are moved from kirkwood.dtsi to the
>> kirkwood-628x.dtsi files so that they still are initialized for these
>> variants.
>>
>> Signed-off-by: Valentin Longchamp <valentin.longchamp@keymile.com>
>> ---
>> arch/arm/boot/dts/kirkwood-6281.dtsi | 24 ++++++++++++++++++++++++
>> arch/arm/boot/dts/kirkwood-6282.dtsi | 24 ++++++++++++++++++++++++
>> arch/arm/boot/dts/kirkwood.dtsi | 24 ------------------------
>> 3 files changed, 48 insertions(+), 24 deletions(-)
>
> What about kirkwood-nsa310.dts?
>
Argh, this one slipped through my net when I checked that all .dts except
km_kirkwood somehow include 628[x].dtsi.
I guess it would be OK to just include kirkwood-6281.dtsi in kirkwood-nsa310.dts
as well. Does someone have access to the HW to actually test it ?
Valentin
prev parent reply other threads:[~2013-05-23 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 9:25 [PATCH] ARM: kirkwood: refactor dtsi to largest common nodes Valentin Longchamp
2013-05-23 11:40 ` Jason Cooper
2013-05-23 13:17 ` Valentin Longchamp [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=519E1700.5040906@keymile.com \
--to=valentin.longchamp@keymile.com \
--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.