cpufreq: Replace "max_transition_latency" with "dynamic_switching"

Browse source

There is no limitation in the ondemand or conservative governors which
disallow the transition_latency to be greater than 10 ms.

The max_transition_latency field is rather used to disallow automatic
dynamic frequency switching for platforms which didn't wanted these
governors to run.

Replace max_transition_latency with a boolean (dynamic_switching) and
check for transition_latency == CPUFREQ_ETERNAL along with that. This
makes it pretty straight forward to read/understand now.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

...

This commit is contained in:

Viresh Kumar 2017-07-19 15:42:46 +05:30 • committed by Rafael J. Wysocki

parent 768608a578

commit ed4676e254

3 changed files with 7 additions and 12 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

8

drivers/cpufreq/cpufreq.c

View file

2

drivers/cpufreq/cpufreq_governor.h

View file

9

include/linux/cpufreq.h

View file