From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v3 3/3] arm64: dts: meson-axg: add clock DT info for Meson AXG SoC
Date: Wed, 06 Dec 2017 11:11:59 -0800 [thread overview]
Message-ID: <7htvx3smbk.fsf@baylibre.com> (raw)
In-Reply-To: <20171206010055.GE4283@codeaurora.org> (Stephen Boyd's message of "Tue, 5 Dec 2017 17:00:55 -0800")
Stephen Boyd <sboyd@codeaurora.org> writes:
> On 12/01, Jerome Brunet wrote:
>> On Fri, 2017-12-01 at 08:34 -0800, Stephen Boyd wrote:
>> > On 11/30, Yixun Lan wrote:
>> > > Hi Stephen
>> > >
>> > > On 11/30/17 03:35, Stephen Boyd wrote:
>> > > >
>> > > > Maybe just call the node "bus at ff63c000"?
>> > > >
>> > >
>> > > isn't this just a name? what's the benefits to change?
>> > > personally, I tend to keep it this way, because it's better map to the
>> > > data sheet
>> > >
>> > > we also has 'aobus', 'cbus' scattered there..
>> >
>> > Per the ePAPR node names are supposed to be generic, like disk,
>> > cpu, display-controller, gpu, etc. I've never heard of a hiubus,
>> > so probably it's some vendor specific thing? We have the phandle
>> > anyway so it's not like we're losing much information here.
>>
>> Stephen, there is a lot of busses on platform. We can't just call them all
>> 'bus'.
>> I don't get the problem with this name.
>> We are re-using the name from the datasheet here, no fancy invention. It seems
>> to be quite common.
>>
>
> Ok. I'm not the maintainer of the DTS so no worries from me. I'm
> just pointing out that the ePAPR says that node names should be
> generic, and 'hiubus' doesn't sound generic to me. If it matches
> some datasheet then I suppose that's good, but probably that sort
> of distinction should have gone into the compatible string
> instead of the node name.
Stephen is right, the node-name should be generic (e.g. "bus") but the
label can (should) be more SoC-specific, so it should look like:
hiubus: bus at ff63c000 {
Note that we weren't strict about this for all the rest of the amlogic
SoCs (mostly because I didn't notice ) but we should start doing it
correctly now. I'll also clean up the existing DTs.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
Yixun Lan <yixun.lan@amlogic.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Carlo Caione <carlo@caione.org>,
Qiufang Dai <qiufang.dai@amlogic.com>,
linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] arm64: dts: meson-axg: add clock DT info for Meson AXG SoC
Date: Wed, 06 Dec 2017 11:11:59 -0800 [thread overview]
Message-ID: <7htvx3smbk.fsf@baylibre.com> (raw)
In-Reply-To: <20171206010055.GE4283@codeaurora.org> (Stephen Boyd's message of "Tue, 5 Dec 2017 17:00:55 -0800")
Stephen Boyd <sboyd@codeaurora.org> writes:
> On 12/01, Jerome Brunet wrote:
>> On Fri, 2017-12-01 at 08:34 -0800, Stephen Boyd wrote:
>> > On 11/30, Yixun Lan wrote:
>> > > Hi Stephen
>> > >
>> > > On 11/30/17 03:35, Stephen Boyd wrote:
>> > > >
>> > > > Maybe just call the node "bus@ff63c000"?
>> > > >
>> > >
>> > > isn't this just a name? what's the benefits to change?
>> > > personally, I tend to keep it this way, because it's better map to the
>> > > data sheet
>> > >
>> > > we also has 'aobus', 'cbus' scattered there..
>> >
>> > Per the ePAPR node names are supposed to be generic, like disk,
>> > cpu, display-controller, gpu, etc. I've never heard of a hiubus,
>> > so probably it's some vendor specific thing? We have the phandle
>> > anyway so it's not like we're losing much information here.
>>
>> Stephen, there is a lot of busses on platform. We can't just call them all
>> 'bus'.
>> I don't get the problem with this name.
>> We are re-using the name from the datasheet here, no fancy invention. It seems
>> to be quite common.
>>
>
> Ok. I'm not the maintainer of the DTS so no worries from me. I'm
> just pointing out that the ePAPR says that node names should be
> generic, and 'hiubus' doesn't sound generic to me. If it matches
> some datasheet then I suppose that's good, but probably that sort
> of distinction should have gone into the compatible string
> instead of the node name.
Stephen is right, the node-name should be generic (e.g. "bus") but the
label can (should) be more SoC-specific, so it should look like:
hiubus: bus@ff63c000 {
Note that we weren't strict about this for all the rest of the amlogic
SoCs (mostly because I didn't notice ) but we should start doing it
correctly now. I'll also clean up the existing DTs.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/3] arm64: dts: meson-axg: add clock DT info for Meson AXG SoC
Date: Wed, 06 Dec 2017 11:11:59 -0800 [thread overview]
Message-ID: <7htvx3smbk.fsf@baylibre.com> (raw)
In-Reply-To: <20171206010055.GE4283@codeaurora.org> (Stephen Boyd's message of "Tue, 5 Dec 2017 17:00:55 -0800")
Stephen Boyd <sboyd@codeaurora.org> writes:
> On 12/01, Jerome Brunet wrote:
>> On Fri, 2017-12-01 at 08:34 -0800, Stephen Boyd wrote:
>> > On 11/30, Yixun Lan wrote:
>> > > Hi Stephen
>> > >
>> > > On 11/30/17 03:35, Stephen Boyd wrote:
>> > > >
>> > > > Maybe just call the node "bus at ff63c000"?
>> > > >
>> > >
>> > > isn't this just a name? what's the benefits to change?
>> > > personally, I tend to keep it this way, because it's better map to the
>> > > data sheet
>> > >
>> > > we also has 'aobus', 'cbus' scattered there..
>> >
>> > Per the ePAPR node names are supposed to be generic, like disk,
>> > cpu, display-controller, gpu, etc. I've never heard of a hiubus,
>> > so probably it's some vendor specific thing? We have the phandle
>> > anyway so it's not like we're losing much information here.
>>
>> Stephen, there is a lot of busses on platform. We can't just call them all
>> 'bus'.
>> I don't get the problem with this name.
>> We are re-using the name from the datasheet here, no fancy invention. It seems
>> to be quite common.
>>
>
> Ok. I'm not the maintainer of the DTS so no worries from me. I'm
> just pointing out that the ePAPR says that node names should be
> generic, and 'hiubus' doesn't sound generic to me. If it matches
> some datasheet then I suppose that's good, but probably that sort
> of distinction should have gone into the compatible string
> instead of the node name.
Stephen is right, the node-name should be generic (e.g. "bus") but the
label can (should) be more SoC-specific, so it should look like:
hiubus: bus at ff63c000 {
Note that we weren't strict about this for all the rest of the amlogic
SoCs (mostly because I didn't notice ) but we should start doing it
correctly now. I'll also clean up the existing DTs.
Kevin
next prev parent reply other threads:[~2017-12-06 19:11 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 12:53 [PATCH v3 0/3] add clk controller driver for Meson-AXG SoC Yixun Lan
2017-11-28 12:53 ` Yixun Lan
2017-11-28 12:53 ` Yixun Lan
2017-11-28 12:53 ` Yixun Lan
2017-11-28 12:53 ` [PATCH v3 1/3] dt-bindings: clock: add compatible variant for the Meson-AXG Yixun Lan
2017-11-28 12:53 ` Yixun Lan
2017-11-28 12:53 ` Yixun Lan
2017-11-28 12:53 ` Yixun Lan
2017-11-28 15:29 ` Rob Herring
2017-11-28 15:29 ` Rob Herring
2017-11-28 15:29 ` Rob Herring
2017-11-28 12:53 ` [PATCH v3 2/3] clk: meson-axg: add clock controller drivers Yixun Lan
2017-11-28 12:53 ` Yixun Lan
2017-11-28 12:53 ` Yixun Lan
2017-11-28 12:53 ` Yixun Lan
2017-11-28 16:30 ` Rob Herring
2017-11-28 16:30 ` Rob Herring
2017-11-28 16:30 ` Rob Herring
2017-11-28 16:30 ` Rob Herring
2017-11-28 23:16 ` Yixun Lan
2017-11-28 23:16 ` Yixun Lan
2017-11-28 23:16 ` Yixun Lan
2017-11-28 23:16 ` Yixun Lan
2017-11-29 19:34 ` Stephen Boyd
2017-11-29 19:34 ` Stephen Boyd
2017-11-29 19:34 ` Stephen Boyd
2017-11-30 6:01 ` Yixun Lan
2017-11-30 6:01 ` Yixun Lan
2017-11-30 6:01 ` Yixun Lan
2017-11-30 6:01 ` Yixun Lan
2017-12-01 16:39 ` Stephen Boyd
2017-12-01 16:39 ` Stephen Boyd
2017-12-01 16:39 ` Stephen Boyd
2017-12-01 16:39 ` Stephen Boyd
2017-11-28 12:53 ` [PATCH v3 3/3] arm64: dts: meson-axg: add clock DT info for Meson AXG SoC Yixun Lan
2017-11-28 12:53 ` Yixun Lan
2017-11-28 12:53 ` Yixun Lan
2017-11-28 12:53 ` Yixun Lan
2017-11-29 19:35 ` Stephen Boyd
2017-11-29 19:35 ` Stephen Boyd
2017-11-29 19:35 ` Stephen Boyd
2017-11-30 6:01 ` Yixun Lan
2017-11-30 6:01 ` Yixun Lan
2017-11-30 6:01 ` Yixun Lan
2017-11-30 6:01 ` Yixun Lan
2017-12-01 16:34 ` Stephen Boyd
2017-12-01 16:34 ` Stephen Boyd
2017-12-01 16:34 ` Stephen Boyd
2017-12-01 16:59 ` Jerome Brunet
2017-12-01 16:59 ` Jerome Brunet
2017-12-01 16:59 ` Jerome Brunet
2017-12-06 1:00 ` Stephen Boyd
2017-12-06 1:00 ` Stephen Boyd
2017-12-06 1:00 ` Stephen Boyd
2017-12-06 19:11 ` Kevin Hilman [this message]
2017-12-06 19:11 ` Kevin Hilman
2017-12-06 19:11 ` Kevin Hilman
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=7htvx3smbk.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@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.