From: Viresh Kumar <viresh.kumar@linaro.org>
To: Sumit Gupta <sumitg@nvidia.com>
Cc: rafael@kernel.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,
ksitaraman@nvidia.com, sanjayc@nvidia.com, bbasu@nvidia.com
Subject: Re: [Patch v4 0/4] Tegra234 cpufreq driver support
Date: Mon, 11 Apr 2022 08:30:30 +0530 [thread overview]
Message-ID: <20220411030030.eqq4a2xgidexowzq@vireshk-i7> (raw)
In-Reply-To: <20220405130119.4697-1-sumitg@nvidia.com>
On 05-04-22, 18:31, Sumit Gupta wrote:
> 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.
Applied. Thanks.
--
viresh
prev parent reply other threads:[~2022-04-11 3:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 13:01 [Patch v4 0/4] Tegra234 cpufreq driver support Sumit Gupta
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 ` Viresh Kumar [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=20220411030030.eqq4a2xgidexowzq@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--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=sumitg@nvidia.com \
--cc=treding@nvidia.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;
as well as URLs for NNTP newsgroup(s).