diff options
| author | Viresh Kumar <viresh.kumar@linaro.org> | 2017-07-19 15:42:49 +0530 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2017-07-26 00:15:47 +0200 |
| commit | fc4c709fc88d5603b235ba18d11f6dba811e1664 (patch) | |
| tree | c8e1a62ff39e359d1fdd20b1fb05e38402e87590 /drivers/cpufreq/kirkwood-cpufreq.c | |
| parent | fe829ed8ef1f3c7ac22843bd594ef2f6c4044288 (diff) | |
| download | talos-obmc-linux-fc4c709fc88d5603b235ba18d11f6dba811e1664.tar.gz talos-obmc-linux-fc4c709fc88d5603b235ba18d11f6dba811e1664.zip | |
cpufreq: Allow dynamic switching with CPUFREQ_ETERNAL latency
With the recent updates, CPUFREQ_ETERNAL is only used by the drivers
which don't know their transition latency but want to use dynamic
switching.
Anyway, the routine cpufreq_policy_transition_delay_us() caps the value
of transition latency to 10 ms now and that can be used safely with such
platforms.
Remove the check from cpufreq_init_governor() and allow dynamic
switching for such configurations as well.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq/kirkwood-cpufreq.c')
0 files changed, 0 insertions, 0 deletions
