lkml.org 
[lkml]   [2019]   [Feb]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH V2 0/5] cpufreq: Use QoS layer to manage freq-constraints
Date
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.

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.

V1->V2:
- The previous version introduced a completely new framework, this one
moves to PM QoS instead.
- Lots of changes because of this.

--
viresh

Viresh Kumar (5):
PM / QOS: Pass request type to dev_pm_qos_{add|remove}_notifier()
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 | 115 +++++++++++--
drivers/base/power/runtime.c | 2 +-
drivers/cpufreq/cpufreq.c | 202 ++++++++++++++++-------
drivers/cpuidle/governor.c | 2 +-
include/linux/cpufreq.h | 12 +-
include/linux/pm_qos.h | 71 ++++++--
9 files changed, 323 insertions(+), 105 deletions(-)

--
2.21.0.rc0.269.g1a574e7a288b

\
 
 \ /
  Last update: 2019-02-21 12:31    [W:0.068 / U:0.508 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site