summaryrefslogtreecommitdiff
path: root/drivers/cpufreq/cpufreq_conservative.c
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-05-14 02:01:08 +0300
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-05-30 15:34:17 +0300
commit16de72b9f4d07e393bea7b1221898b3be718a296 (patch)
tree43660e07ea40059549e3ee3ae001510152b8b421 /drivers/cpufreq/cpufreq_conservative.c
parent9e8c0a899b2f89b8367d33668f6819892f0a00f2 (diff)
downloadlinux-16de72b9f4d07e393bea7b1221898b3be718a296.tar.xz
cpufreq: governor: Simplify performance and powersave governors
The performance and powersave cpufreq governors handle the CPUFREQ_GOV_START event in the same way as CPUFREQ_GOV_LIMITS. However, the cpufreq core always invokes cpufreq_governor() with the event argument equal to CPUFREQ_GOV_LIMITS right after invoking it with event equal to CPUFREQ_GOV_START. As a result, for both the governors in question, __cpufreq_driver_target() is executed twice in a row with the same arguments which is not useful. For this reason, simplify the performance and powersave governors to handle the CPUFREQ_GOV_LIMITS event only as that's going to be sufficient for the governor start too. Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Diffstat (limited to 'drivers/cpufreq/cpufreq_conservative.c')
0 files changed, 0 insertions, 0 deletions