From: Bo Yan <byan@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: <jonathanh@nvidia.com>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] arm64: tegra: add topology data for Tegra194 cpu
Date: Wed, 13 Feb 2019 08:24:29 -0800 [thread overview]
Message-ID: <705dcfd2-0808-2c50-d73f-97050bf876f0@nvidia.com> (raw)
In-Reply-To: <20190213081252.GA647@ulmo>
I agree, will update this patch with full paths replacing phandles.
On 2/13/19 12:12 AM, Thierry Reding wrote:
> On Mon, Feb 11, 2019 at 03:47:07PM -0800, Bo Yan wrote:
>> The xavier CPU architecture includes 8 CPU cores organized in
>> 4 clusters. Add cpu-map data for topology initialization, this
>> fixes the topology information in
>> /sys/devices/system/cpu/cpu[n]/topology
>>
>> Signed-off-by: Bo Yan <byan@nvidia.com>
>> ---
>> V2: remove cache nodes, add topology data only
>>
>> arch/arm64/boot/dts/nvidia/tegra194.dtsi | 58 +++++++++++++++++++++++++++-----
>> 1 file changed, 50 insertions(+), 8 deletions(-)
>
> This mostly looks good to me. One minor comment below.
>
>>
>> diff --git a/arch/arm64/boot/dts/nvidia/tegra194.dtsi b/arch/arm64/boot/dts/nvidia/tegra194.dtsi
>> index 6dfa1ca..35e6e76 100644
>> --- a/arch/arm64/boot/dts/nvidia/tegra194.dtsi
>> +++ b/arch/arm64/boot/dts/nvidia/tegra194.dtsi
>> @@ -870,56 +870,98 @@
>> #address-cells = <1>;
>> #size-cells = <0>;
>>
>> - cpu@0 {
>> + cpu-map {
>> + cluster0 {
>> + core0 {
>> + cpu = <&cl0_0>;
>
> I wonder if perhaps in this case it would be better to use the full path
> to refer to the phandle here. That way we can avoid the labels, which
> are somewhat cumbersome to write and the hierarchy, in my opinion, is a
> much more natural way to reference these.
>
> What I'm suggesting would look roughly like this:
>
> cpu-map {
> cluster0 {
> core0 {
> cpu = <&{/cpus/cpu@0}>;
> };
>
> core1 {
> cpu = <&{/cpus/cpu@1}>;
> };
> };
>
> cluster1 {
> core0 {
> cpu = <&{/cpus/cpu@2}>;
> };
>
> core1 {
> cpu = <&{/cpus/cpu@3}>;
> };
> };
>
> ...
> };
>
> That's slightly more characters, but I think it's much easier to read
> than the labels.
>
> I don't feel very strongly about it, though, so feel free to keep this
> as-is if you prefer.
>
> Thierry
>
next prev parent reply other threads:[~2019-02-13 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 18:35 [PATCH] " Bo Yan
2019-01-31 22:25 ` Thierry Reding
2019-01-31 23:29 ` Bo Yan
2019-02-11 23:34 ` Bo Yan
2019-02-11 23:47 ` [PATCH V2] " Bo Yan
2019-02-13 8:12 ` Thierry Reding
2019-02-13 16:24 ` Bo Yan [this message]
2019-02-13 16:33 ` [PATCH V3] " Bo Yan
2019-02-22 0:52 ` Bo Yan
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=705dcfd2-0808-2c50-d73f-97050bf876f0@nvidia.com \
--to=byan@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/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
Powered by JetHome