diff options
author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2019-10-16 12:41:24 +0200 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2019-10-21 02:05:21 +0200 |
commit | 77751a466ebd1a785456556061a2db6d60ea3898 (patch) | |
tree | d1c1b1a776630774675e674965dfe3bbc54b05b5 /drivers/thermal | |
parent | Linux 5.4-rc4 (diff) | |
download | linux-77751a466ebd1a785456556061a2db6d60ea3898.tar.xz linux-77751a466ebd1a785456556061a2db6d60ea3898.zip |
PM: QoS: Introduce frequency QoS
Introduce frequency QoS, based on the "raw" low-level PM QoS, to
represent min and max frequency requests and aggregate constraints.
The min and max frequency requests are to be represented by
struct freq_qos_request objects and the aggregate constraints are to
be represented by struct freq_constraints objects. The latter are
expected to be initialized with the help of freq_constraints_init().
The freq_qos_read_value() helper is defined to retrieve the aggregate
constraints values from a given struct freq_constraints object and
there are the freq_qos_add_request(), freq_qos_update_request() and
freq_qos_remove_request() helpers to manipulate the min and max
frequency requests. It is assumed that the the helpers will not
run concurrently with each other for the same struct freq_qos_request
object, so if that may be the case, their uses must ensure proper
synchronization between them (e.g. through locking).
In addition, freq_qos_add_notifier() and freq_qos_remove_notifier()
are provided to add and remove notifiers that will trigger on aggregate
constraint changes to and from a given struct freq_constraints object,
respectively.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Diffstat (limited to 'drivers/thermal')
0 files changed, 0 insertions, 0 deletions