From: Sibi Sankar <quic_sibis@quicinc.com>
To: <sudeep.holla@arm.com>, <cristian.marussi@arm.com>,
<rafael@kernel.org>, <viresh.kumar@linaro.org>,
<morten.rasmussen@arm.com>, <dietmar.eggemann@arm.com>,
<lukasz.luba@arm.com>, <pierre.gondois@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<quic_mdtipton@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
Sibi Sankar <quic_sibis@quicinc.com>
Subject: [PATCH V4 0/2] firmware: arm_scmi: Register and handle limits change notification
Date: Thu, 28 Mar 2024 13:11:29 +0530 [thread overview]
Message-ID: <20240328074131.2839871-1-quic_sibis@quicinc.com> (raw)
This series registers for scmi limits change notifications to determine
the throttled frequency and apply HW pressure.
V4:
* Use EXPORT_SYMBOL_GPL instead. [Trilok]
* Use a interim variable to show the khz calc. [Lukasz]
* Use driver_data to pass on the handle and scmi_dev instead of using
global variables. Dropped Lukasz's Rb due to adding these minor
changes.
V3:
* Sanitize range_max received from the notifier. [Pierre]
* Drop patches 1/2 from v2. [Cristian]
* Update commit message in patch 2.
V2:
* Rename opp_xlate -> freq_xlate [Viresh]
* Export cpufreq_update_pressure and use it directly [Lukasz]
Depends on:
HW pressure v6: https://patchwork.kernel.org/project/linux-arm-msm/cover/20240326091616.3696851-1-vincent.guittot@linaro.org/
Sibi Sankar (2):
cpufreq: Export cpufreq_update_pressure
cpufreq: scmi: Register for limit change notifications
drivers/cpufreq/cpufreq.c | 3 ++-
drivers/cpufreq/scmi-cpufreq.c | 44 ++++++++++++++++++++++++++++++++++
include/linux/cpufreq.h | 2 ++
3 files changed, 48 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2024-03-28 7:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 7:41 Sibi Sankar [this message]
2024-03-28 7:41 ` [PATCH V4 1/2] cpufreq: Export cpufreq_update_pressure Sibi Sankar
2024-03-28 7:41 ` [PATCH V4 2/2] cpufreq: scmi: Register for limit change notifications Sibi Sankar
2024-03-28 8:06 ` Lukasz Luba
2024-05-01 8:21 ` Cristian Marussi
2024-05-01 8:26 ` Cristian Marussi
2024-05-14 9:40 ` Sibi Sankar
2024-05-28 9:08 ` Vincent Guittot
2024-06-03 18:48 ` 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=20240328074131.2839871-1-quic_sibis@quicinc.com \
--to=quic_sibis@quicinc.com \
--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=lukasz.luba@arm.com \
--cc=morten.rasmussen@arm.com \
--cc=pierre.gondois@arm.com \
--cc=quic_mdtipton@quicinc.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).