From: Sumit Gupta <sumitg@nvidia.com>
To: <rafael@kernel.org>, <viresh.kumar@linaro.org>,
<robh+dt@kernel.org>, <krzk+dt@kernel.org>, <treding@nvidia.com>,
<jonathanh@nvidia.com>, <linux-pm@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <ksitaraman@nvidia.com>, <sanjayc@nvidia.com>, <bbasu@nvidia.com>,
<sumitg@nvidia.com>
Subject: [Patch v4 0/4] Tegra234 cpufreq driver support
Date: Tue, 5 Apr 2022 18:31:15 +0530 [thread overview]
Message-ID: <20220405130119.4697-1-sumitg@nvidia.com> (raw)
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
next reply other threads:[~2022-04-06 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 13:01 Sumit Gupta [this message]
2022-04-05 13:01 ` [Patch v4 1/4] dt-bindings: Document Tegra CCPLEX Cluster Sumit Gupta
2022-04-06 18:51 ` Rob Herring
2022-04-05 13:01 ` [Patch v4 2/4] cpufreq: tegra194: add soc data to support multiple soc Sumit Gupta
2022-04-05 13:01 ` [Patch v4 3/4] cpufreq: tegra194: Add support for Tegra234 Sumit Gupta
2022-04-05 13:01 ` [Patch v4 4/4] arm64: tegra: add node for tegra234 cpufreq Sumit Gupta
2022-04-11 3:00 ` [Patch v4 0/4] Tegra234 cpufreq driver support Viresh Kumar
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=20220405130119.4697-1-sumitg@nvidia.com \
--to=sumitg@nvidia.com \
--cc=bbasu@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=ksitaraman@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sanjayc@nvidia.com \
--cc=treding@nvidia.com \
--cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).