From: Sibi Sankar <quic_sibis@quicinc.com>
To: <dietmar.eggemann@arm.com>, <marcan@marcan.st>,
<sven@svenpeter.dev>, <alyssa@rosenzweig.io>, <rafael@kernel.org>,
<viresh.kumar@linaro.org>, <xuwei5@hisilicon.com>,
<zhanjie9@hisilicon.com>
Cc: <sudeep.holla@arm.com>, <cristian.marussi@arm.com>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<quic_rgottimu@quicinc.com>,
<linux-arm-kernel@lists.infradead.org>, <asahi@lists.linux.dev>,
<linux-pm@vger.kernel.org>, Sibi Sankar <quic_sibis@quicinc.com>
Subject: [PATCH 0/2] Fix per-policy boost behavior
Date: Tue, 27 Feb 2024 22:23:07 +0530 [thread overview]
Message-ID: <20240227165309.620422-1-quic_sibis@quicinc.com> (raw)
Fix per-policy boost behavior by incorporating per-policy boost flag
in the policy->max calculation and setting the correct per-policy
boost_enabled value on devices that use cpufreq_enable_boost_support().
Logs reported-by Dietmar Eggemann [1]:
[1] https://lore.kernel.org/lkml/265e5f2c-9b45-420f-89b1-44369aeb8418@arm.com/
Sibi Sankar (2):
cpufreq: Fix per-policy boost behavior on SoCs using
cpufreq_boost_set_sw
cpufreq: apple-soc: Align per-policy and global boost flags
drivers/cpufreq/apple-soc-cpufreq.c | 1 +
drivers/cpufreq/cpufreq.c | 15 +++++++++------
drivers/cpufreq/freq_table.c | 2 +-
3 files changed, 11 insertions(+), 7 deletions(-)
--
2.34.1
next reply other threads:[~2024-02-27 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 16:53 Sibi Sankar [this message]
2024-02-27 16:53 ` [PATCH 1/2] cpufreq: Fix per-policy boost behavior on SoCs using cpufreq_boost_set_sw Sibi Sankar
2024-02-27 16:53 ` [PATCH 2/2] cpufreq: apple-soc: Align per-policy and global boost flags Sibi Sankar
2024-02-28 2:06 ` [PATCH 0/2] Fix per-policy boost behavior Jie Zhan
2024-02-28 5:07 ` Sibi Sankar
2024-02-28 5:07 ` Viresh Kumar
2024-02-28 5:14 ` Sibi Sankar
2024-02-28 6:35 ` Viresh Kumar
2024-02-28 10:09 ` Sibi Sankar
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=20240227165309.620422-1-quic_sibis@quicinc.com \
--to=quic_sibis@quicinc.com \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=cristian.marussi@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=quic_rgottimu@quicinc.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=sven@svenpeter.dev \
--cc=viresh.kumar@linaro.org \
--cc=xuwei5@hisilicon.com \
--cc=zhanjie9@hisilicon.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 read-only IMAP folder(s) and NNTP newsgroup(s).