diff options
| author |   Viresh Kumar <viresh.kumar@linaro.org> | 2015-07-30 12:40:35 +0530 |
|---|---|---|
| committer |   Eduardo Valentin <edubezval@gmail.com> | 2015-08-14 18:26:23 -0700 |
| commit | 1afb9c539daebc2c8a7b33d0e0b8fc9f74671b02 (patch) | |
| tree | fc09b2a671c8890cacbd2358008d2a4bce44f2b6 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | thermal/cpu_cooling: rename max_freq as clipped_freq in notifier (diff) | |
| download | wireguard-linux-1afb9c539daebc2c8a7b33d0e0b8fc9f74671b02.tar.xz wireguard-linux-1afb9c539daebc2c8a7b33d0e0b8fc9f74671b02.zip | |
thermal/cpu_cooling: update policy limits if clipped_freq < policy->max
policy->max is the maximum allowed frequency defined by user and
clipped_freq is the maximum that thermal constraints allow.
If clipped_freq is lower than policy->max, then we need to readjust
policy->max.
But, if clipped_freq is greater than policy->max, we don't need to do
anything. We used to call cpufreq_verify_within_limits() in this case,
but it doesn't change anything in this case.
Lets skip this unnecessary call and write a comment that explains this.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Eduardo Valentin <edubezval@gmail.com>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions