From: Bo Yan <byan@nvidia.com>
To: <thierry.reding@gmail.com>, <jonathanh@nvidia.com>
Cc: <robh+dt@kernel.org>, <mark.rutland@arm.com>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] arm64: tegra: add topology data for Tegra194 cpu
Date: Thu, 21 Feb 2019 16:52:21 -0800 [thread overview]
Message-ID: <c70c91f6-b719-cb86-2fe1-e6231c089ce9@nvidia.com> (raw)
In-Reply-To: <1550075622-1072-1-git-send-email-byan@nvidia.com>
The patch V3 adopted changes suggested by Thierry.
On 2/13/19 8:33 AM, 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>
> ---
> V3: Replaced phandles with full path to CPU node
> V2: remove cache nodes, add topology data only
>
> arch/arm64/boot/dts/nvidia/tegra194.dtsi | 42 ++++++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/nvidia/tegra194.dtsi b/arch/arm64/boot/dts/nvidia/tegra194.dtsi
> index 6dfa1ca..708d20c 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra194.dtsi
> +++ b/arch/arm64/boot/dts/nvidia/tegra194.dtsi
> @@ -870,6 +870,48 @@
> #address-cells = <1>;
> #size-cells = <0>;
>
> + cpu-map {
> + cluster0 {
> + core0 {
> + cpu = <&{/cpus/cpu@0}>;
> + };
> +
> + core1 {
> + cpu = <&{/cpus/cpu@1}>;
> + };
> + };
> +
> + cluster1 {
> + core0 {
> + cpu = <&{/cpus/cpu@2}>;
> + };
> +
> + core1 {
> + cpu = <&{/cpus/cpu@3}>;
> + };
> + };
> +
> + cluster2 {
> + core0 {
> + cpu = <&{/cpus/cpu@4}>;
> + };
> +
> + core1 {
> + cpu = <&{/cpus/cpu@5}>;
> + };
> + };
> +
> + cluster3 {
> + core0 {
> + cpu = <&{/cpus/cpu@6}>;
> + };
> +
> + core1 {
> + cpu = <&{/cpus/cpu@7}>;
> + };
> + };
> + };
> +
> cpu@0 {
> compatible = "nvidia,tegra194-carmel", "arm,armv8";
> device_type = "cpu";
>
prev parent reply other threads:[~2019-02-22 0:52 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
2019-02-13 16:33 ` [PATCH V3] " Bo Yan
2019-02-22 0:52 ` Bo Yan [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=c70c91f6-b719-cb86-2fe1-e6231c089ce9@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