diff options
author | Viresh Kumar <viresh.kumar@linaro.org> | 2025-01-23 11:04:25 +0530 |
---|---|---|
committer | Viresh Kumar <viresh.kumar@linaro.org> | 2025-02-07 09:45:14 +0530 |
commit | 1f7d1bab50e6ae517f8b6699e56d709d61ae13e5 (patch) | |
tree | edac5554ba21c94cb7e59cf0e2dfa0d6aefc31dc /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | 9a23eb8b2b5d8c5f1129c5a523a786ddd53cd7c9 (diff) |
cpufreq: Introduce policy->boost_supported flag
It is possible to have a scenario where not all cpufreq policies support
boost frequencies. And letting sysfs (or other parts of the kernel)
enable boost feature for that policy isn't correct.
Add a new flag, boost_supported, which will be set to true by the
cpufreq core only if the freq table contains valid boost frequencies.
Some cpufreq drivers though don't have boost frequencies in the
freq-table, they can set this flag from their ->init() callbacks.
Once all the drivers are updated to set the flag correctly, we can check
it before enabling boost feature for a policy.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions