diff options
| author |   Viresh Kumar <viresh.kumar@linaro.org> | 2019-06-20 08:35:50 +0530 |
|---|---|---|
| committer |   Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2019-06-28 11:24:56 +0200 |
| commit | 70a59fde6e69d1d8579f84bf4555bfffb3ce452d (patch) | |
| tree | 53863dd8106c2f2a564da43055a3e1154da2895f /include/linux/pm_qos.h | |
| parent | cpufreq: Consolidate cpufreq_update_current_freq() and __cpufreq_get() (diff) | |
| download | wireguard-linux-70a59fde6e69d1d8579f84bf4555bfffb3ce452d.tar.xz wireguard-linux-70a59fde6e69d1d8579f84bf4555bfffb3ce452d.zip | |
cpufreq: Avoid calling cpufreq_verify_current_freq() from handle_update()
On some occasions cpufreq_verify_current_freq() schedules a work whose
callback is handle_update(), which further calls cpufreq_update_policy()
which may end up calling cpufreq_verify_current_freq() again.
On the other hand, when cpufreq_update_policy() is called from
handle_update(), the pointer to the cpufreq policy is already
available, but cpufreq_cpu_acquire() is still called to get it in
cpufreq_update_policy(), which should be avoided as well.
To fix these issues, create a new helper, refresh_frequency_limits(),
and make both handle_update() call it cpufreq_update_policy().
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
[ rjw: Rename reeval_frequency_limits() as refresh_frequency_limits() ]
[ rjw: Changelog ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'include/linux/pm_qos.h')
0 files changed, 0 insertions, 0 deletions