Files
linux/include/linux
Viresh Kumar fe829ed8ef cpufreq: Add CPUFREQ_NO_AUTO_DYNAMIC_SWITCHING cpufreq driver flag
The policy->transition_latency field is used for multiple purposes
today and its not straight forward at all. This is how it is used:

A. Set the correct transition_latency value.

B. Set it to CPUFREQ_ETERNAL because:
   1. We don't want automatic dynamic switching (with
      ondemand/conservative) to happen at all.
   2. We don't know the transition latency.

This patch handles the B.1. case in a more readable way. A new flag for
the cpufreq drivers is added to disallow use of cpufreq governors which
have dynamic_switching flag set.

All the current cpufreq drivers which are setting transition_latency
unconditionally to CPUFREQ_ETERNAL are updated to use it. They don't
need to set transition_latency anymore.

There shouldn't be any functional change after this patch.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2017-07-26 00:15:46 +02:00
..
2017-07-03 17:00:59 -06:00
2017-07-06 16:24:33 -07:00
2017-07-03 16:56:28 -06:00
2017-07-10 16:32:31 -07:00
2017-07-07 09:49:24 +10:00
2017-07-07 20:09:10 -04:00
2017-07-10 16:32:34 -07:00
2017-07-12 16:26:01 -07:00
2017-07-13 16:00:15 -04:00
2017-07-13 16:00:15 -04:00
2017-07-13 16:00:15 -04:00
2017-07-12 16:26:02 -07:00
2017-07-06 11:30:07 -04:00
2017-07-12 23:11:23 +02:00
2017-07-06 16:24:30 -07:00