diff options
author | Leonard Crestez <leonard.crestez@nxp.com> | 2019-11-26 17:17:13 +0200 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2019-11-29 12:04:50 +0100 |
commit | 36a8015f89e40f7c9c91cc7e6d028fa288dad27b (patch) | |
tree | c6b72f79e678029514d2bf3f385a62d1df9a1f4e /kernel/power | |
parent | 342035f66c866f4ad750477b21b210e98d1f6818 (diff) | |
download | linux-36a8015f89e40f7c9c91cc7e6d028fa288dad27b.tar.gz linux-36a8015f89e40f7c9c91cc7e6d028fa288dad27b.tar.bz2 linux-36a8015f89e40f7c9c91cc7e6d028fa288dad27b.zip |
PM / QoS: Restore DEV_PM_QOS_MIN/MAX_FREQUENCY
Support for adding per-device frequency limits was removed in
commit 2aac8bdf7a0f ("PM: QoS: Drop frequency QoS types from device PM QoS")
after cpufreq switched to use a new "freq_constraints" construct.
Restore support for per-device freq limits but base this upon
freq_constraints. This is primarily meant to be used by the devfreq
subsystem.
This removes the "static" marking on freq_qos_apply but does not export
it for modules.
Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
Tested-by: Matthias Kaehlcke <mka@chromium.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'kernel/power')
-rw-r--r-- | kernel/power/qos.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/kernel/power/qos.c b/kernel/power/qos.c index a45cba7df0ae..83edf8698118 100644 --- a/kernel/power/qos.c +++ b/kernel/power/qos.c @@ -714,8 +714,10 @@ s32 freq_qos_read_value(struct freq_constraints *qos, * @req: Constraint request to apply. * @action: Action to perform (add/update/remove). * @value: Value to assign to the QoS request. + * + * This is only meant to be called from inside pm_qos, not drivers. */ -static int freq_qos_apply(struct freq_qos_request *req, +int freq_qos_apply(struct freq_qos_request *req, enum pm_qos_req_action action, s32 value) { int ret; |