From: Aaron Kling via B4 Relay <devnull+webgeek1234.gmail.com@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Aaron Kling <luceoscutum@gmail.com>,
Sumit Gupta <sumitg@nvidia.com>
Cc: Thierry Reding <treding@nvidia.com>,
linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org,
Aaron Kling <webgeek1234@gmail.com>,
Mikko Perttunen <mperttunen@nvidia.com>
Subject: [PATCH 0/2] cpufreq: tegra186: Fix initialization and scaling
Date: Tue, 26 Aug 2025 15:15:58 -0500 [thread overview]
Message-ID: <20250826-tegra186-cpufreq-fixes-v1-0-97f98d3e0adb@gmail.com> (raw)
This series fixes an issue with shared policy per cluster not scaling
all cpus and with some cores being initialized by the subsystem.
Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
---
Aaron Kling (2):
cpufreq: tegra186: Set target frequency for all cpus in policy
cpufreq: tegra186: Initialize all cores to base frequencies
drivers/cpufreq/tegra186-cpufreq.c | 19 ++++++++++++++++---
1 file changed, 16 insertions(+), 3 deletions(-)
---
base-commit: 1b237f190eb3d36f52dffe07a40b5eb210280e00
change-id: 20250826-tegra186-cpufreq-fixes-7fbff81c68a2
Best regards,
--
Aaron Kling <webgeek1234@gmail.com>
next reply other threads:[~2025-08-26 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 20:15 Aaron Kling via B4 Relay [this message]
2025-08-26 20:15 ` [PATCH 1/2] cpufreq: tegra186: Set target frequency for all cpus in policy Aaron Kling via B4 Relay
2025-08-26 20:16 ` [PATCH 2/2] cpufreq: tegra186: Initialize all cores to base frequencies Aaron Kling via B4 Relay
2025-08-27 2:09 ` Mikko Perttunen
2025-08-27 5:54 ` Aaron Kling
2025-08-27 10:16 ` Mikko Perttunen
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=20250826-tegra186-cpufreq-fixes-v1-0-97f98d3e0adb@gmail.com \
--to=devnull+webgeek1234.gmail.com@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=luceoscutum@gmail.com \
--cc=mperttunen@nvidia.com \
--cc=rafael@kernel.org \
--cc=sumitg@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.com \
--cc=viresh.kumar@linaro.org \
--cc=webgeek1234@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
all inboxes | Powered by JetHome®