[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1592775274-27513-3-git-send-email-sumitg@nvidia.com>
Date: Mon, 22 Jun 2020 03:04:32 +0530
From: Sumit Gupta <sumitg@...dia.com>
To: <rjw@...ysocki.net>, <viresh.kumar@...aro.org>,
<catalin.marinas@....com>, <will@...nel.org>,
<thierry.reding@...il.com>, <robh+dt@...nel.org>,
<devicetree@...r.kernel.org>, <jonathanh@...dia.com>,
<talho@...dia.com>, <linux-pm@...r.kernel.org>,
<linux-tegra@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
CC: <bbasu@...dia.com>, <sumitg@...dia.com>, <mperttunen@...dia.com>
Subject: [TEGRA194_CPUFREQ Patch v3 2/4] arm64: tegra: Add t194 ccplex compatible and bpmp property
On Tegra194, data on valid operating points for the CPUs needs to be
queried from BPMP. In T194, there is no node representing CPU complex.
So, add compatible string to the 'cpus' node instead of using dummy
node to bind cpufreq driver. Also, add reference to the BPMP instance
for the CPU complex.
Signed-off-by: Sumit Gupta <sumitg@...dia.com>
---
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra194.dtsi b/arch/arm64/boot/dts/nvidia/tegra194.dtsi
index 7c9511a..0abf287 100644
--- a/arch/arm64/boot/dts/nvidia/tegra194.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra194.dtsi
@@ -1764,6 +1764,8 @@
};
cpus {
+ compatible = "nvidia,tegra194-ccplex";
+ nvidia,bpmp = <&bpmp>;
#address-cells = <1>;
#size-cells = <0>;
--
2.7.4
Powered by blists - more mailing lists