All of lore.kernel.org
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 3/7] ARM: dts: enable hi4511 with device tree
Date: Mon, 2 Sep 2013 10:33:28 +0200	[thread overview]
Message-ID: <CACRpkdbQKOdgOzSwK=TvkDdv-mp=Mn6sTTwtUoRUzi9=PrkqDg@mail.gmail.com> (raw)
In-Reply-To: <87d2ovs0fm.fsf@linaro.org>

On Fri, Aug 30, 2013 at 4:44 PM, Kevin Hilman <khilman@linaro.org> wrote:

>>> Why is sysctrl and all of its children now under the clocks node?
>>>
>>> Kevin
>>
>> SMP registers and clock registers are sharing the system controller.
>
> That suggest the clock node should be a child of the sysctrl node, not
> the other way around.

That is the way we do it for the Nomadik in
arch/arm/boot/dts/ste-nomadik-stn8815.dtsi
so a precedent exist. (SRC is system reset and control).

Yours,
Linus Walleij

  reply	other threads:[~2013-09-02  8:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28 13:10 [PATCH v9 0/7] enable hi3xxx SoC Haojian Zhuang
2013-08-28 13:10 ` [PATCH v9 1/7] clk: hi3xxx: add clock support Haojian Zhuang
2013-08-28 13:10 ` [PATCH v9 2/7] ARM: hi3xxx: add board support with device tree Haojian Zhuang
2013-08-28 13:10 ` [PATCH v9 3/7] ARM: dts: enable hi4511 " Haojian Zhuang
2013-08-29 18:13   ` Kevin Hilman
2013-08-30  1:19     ` Haojian Zhuang
2013-08-30 14:44       ` Kevin Hilman
2013-09-02  8:33         ` Linus Walleij [this message]
2013-08-28 13:10 ` [PATCH v9 4/7] ARM: config: enable hi3xxx in multi_v7_defconfig Haojian Zhuang
2013-08-28 13:10 ` [PATCH v9 5/7] ARM: config: add defconfig for Hi3xxx Haojian Zhuang
2013-08-28 13:10 ` [PATCH v9 6/7] ARM: hi3xxx: add smp support Haojian Zhuang
2013-08-29 18:24   ` Kevin Hilman
2013-08-28 13:10 ` [PATCH v9 7/7] ARM: hi3xxx: add hotplug support Haojian Zhuang

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='CACRpkdbQKOdgOzSwK=TvkDdv-mp=Mn6sTTwtUoRUzi9=PrkqDg@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --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.