[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220405130119.4697-1-sumitg@nvidia.com>
Date: Tue, 5 Apr 2022 18:31:15 +0530
From: Sumit Gupta <sumitg@...dia.com>
To: <rafael@...nel.org>, <viresh.kumar@...aro.org>,
<robh+dt@...nel.org>, <krzk+dt@...nel.org>, <treding@...dia.com>,
<jonathanh@...dia.com>, <linux-pm@...r.kernel.org>,
<linux-tegra@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
CC: <ksitaraman@...dia.com>, <sanjayc@...dia.com>, <bbasu@...dia.com>,
<sumitg@...dia.com>
Subject: [Patch v4 0/4] Tegra234 cpufreq driver support
This patchset adds driver support for Tegra234 cpufreq.
Also, added soc data and ops to support multiple SoC's and variants
which have similar logic to {get|set} cpu frequency as Tegra194 in
the same driver.
>From cpufreq point, main difference between Tegra194 and Tegra234 are:
1) Tegra234 uses MMIO for frequency requests and not sysreg like T194.
2) MPIDR affinity info in Tegra234 is different from Tegra194.
3) Register bits of pllp_clk_count and core_clk_count are swapped.
So, added ops hooks for Tegra234.
---
v3-> v4:
- fixed reg property too long error and set additionalProperties to
false in the binding document.
v2 -> v3:
- used CPU COMPLEX CLUSTER name in binding document.
- reordered the patches.
v1 -> v2:
- added nvidia,tegra-ccplex-cluster.yaml binding doc
- changed compatible check to 'soc->actmon_cntr_base' field of soc data
Sumit Gupta (4):
dt-bindings: Document Tegra CCPLEX Cluster
cpufreq: tegra194: add soc data to support multiple soc
cpufreq: tegra194: Add support for Tegra234
arm64: tegra: add node for tegra234 cpufreq
.../tegra/nvidia,tegra-ccplex-cluster.yaml | 52 ++++
arch/arm64/boot/dts/nvidia/tegra234.dtsi | 7 +
drivers/cpufreq/tegra194-cpufreq.c | 246 +++++++++++++++---
3 files changed, 268 insertions(+), 37 deletions(-)
create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra-ccplex-cluster.yaml
--
2.17.1
Powered by blists - more mailing lists