diff options
author | 2020-05-30 10:08:30 +0800 | |
---|---|---|
committer | 2020-06-05 14:20:02 +0200 | |
commit | cf6fada71543ceea0f6228ffdc0b85778f3f5a6e (patch) | |
tree | 34b4fa593a9d4aba8260489bd14f0cfac061fa84 /scripts/gdb/linux/utils.py | |
parent | Merge branch 'cpufreq/arm/linux-next' of git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm (diff) | |
download | linux-rng-cf6fada71543ceea0f6228ffdc0b85778f3f5a6e.tar.xz linux-rng-cf6fada71543ceea0f6228ffdc0b85778f3f5a6e.zip |
cpufreq: change '.set_boost' to act on one policy
Macro 'for_each_active_policy()' is defined internally. To avoid some
cpufreq driver needing this macro to iterate over all the policies in
'.set_boost' callback, we redefine '.set_boost' to act on only one
policy and pass the policy as an argument.
'cpufreq_boost_trigger_state()' iterates over all the policies to set
boost for the system.
This is preparation for adding SW BOOST support for CPPC.
To protect Boost enable/disable by sysfs from CPU online/offline,
add 'cpu_hotplug_lock' before calling '.set_boost' for each CPU.
Also move the lock from 'set_boost()' to 'store_cpb()' in
acpi_cpufreq.
Signed-off-by: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Suggested-by: Viresh Kumar <viresh.kumar@linaro.org>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
[ rjw: Subject & changelog ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions