From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Kevin Hilman <khilman@kernel.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Qais.Yousef@arm.com, mka@chromium.org, juri.lelli@gmail.com,
linux-kernel@vger.kernel.org
Subject: [PATCH V4 0/6] cpufreq: Use QoS layer to manage freq-constraints
Date: Thu, 20 Jun 2019 13:05:23 +0530 [thread overview]
Message-ID: <cover.1561014965.git.viresh.kumar@linaro.org> (raw)
Hello,
This patchset attempts to manage CPU frequency constraints using the PM
QoS framework. It only does the basic stuff right now and moves the
userspace constraints to use the QoS infrastructure.
This is rebased over pm/linux-next and another cleanup series [1].
Todo:
- Migrate all users to the QoS framework and get rid of cpufreq specific
notifiers.
- Make PM QoS learn about the relation of CPUs in a policy, so a single
list of constraints is managed for all of them instead of per-cpu
constraints.
V3->V4:
- Few commit logs updated as suggested during reviews.
- Separate commit (2/6) to create resume-latency specific routines
- Reused earlier work ("update") for notifiers as well.
- Kept Reviewed-by tags as is as the patches normally got better only.
Please take them back if you find any issues.
V2->V3:
- Add a comment in cpufreq.c as suggested by Qais.
- Rebased on latest pm/linux-next.
V1->V2:
- The previous version introduced a completely new framework, this one
moves to PM QoS instead.
- Lots of changes because of this.
--
viresh
[1] http://lore.kernel.org/lkml/cover.1560999838.git.viresh.kumar@linaro.org
Viresh Kumar (6):
PM / QOS: Pass request type to dev_pm_qos_{add|remove}_notifier()
PM / QOS: Rename __dev_pm_qos_read_value() and
dev_pm_qos_raw_read_value()
PM / QOS: Pass request type to dev_pm_qos_read_value()
PM / QoS: Add support for MIN/MAX frequency constraints
cpufreq: Register notifiers with the PM QoS framework
cpufreq: Add QoS requests for userspace constraints
Documentation/power/pm_qos_interface.txt | 12 +-
drivers/base/power/domain.c | 8 +-
drivers/base/power/domain_governor.c | 4 +-
drivers/base/power/qos.c | 135 ++++++++++++++--
drivers/base/power/runtime.c | 2 +-
drivers/cpufreq/cpufreq.c | 198 ++++++++++++++++-------
drivers/cpuidle/governor.c | 2 +-
include/linux/cpufreq.h | 11 +-
include/linux/pm_qos.h | 48 ++++--
9 files changed, 316 insertions(+), 104 deletions(-)
--
2.21.0.rc0.269.g1a574e7a288b
next reply other threads:[~2019-06-20 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 7:35 Viresh Kumar [this message]
2019-06-20 7:35 ` [PATCH V4 1/6] PM / QOS: Pass request type to dev_pm_qos_{add|remove}_notifier() Viresh Kumar
2019-06-20 7:35 ` [PATCH V4 2/6] PM / QOS: Rename __dev_pm_qos_read_value() and dev_pm_qos_raw_read_value() Viresh Kumar
2019-06-20 7:35 ` [PATCH V4 3/6] PM / QOS: Pass request type to dev_pm_qos_read_value() Viresh Kumar
2019-06-20 7:35 ` [PATCH V4 4/6] PM / QoS: Add support for MIN/MAX frequency constraints Viresh Kumar
2019-06-20 7:35 ` [PATCH V4 5/6] cpufreq: Register notifiers with the PM QoS framework Viresh Kumar
2019-06-20 7:35 ` [PATCH V4 6/6] cpufreq: Add QoS requests for userspace constraints 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=cover.1561014965.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=Qais.Yousef@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=juri.lelli@gmail.com \
--cc=khilman@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=ulf.hansson@linaro.org \
--cc=vincent.guittot@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).