diff options
| author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2016-05-14 02:01:08 +0300 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2016-05-30 15:34:17 +0300 |
| commit | 16de72b9f4d07e393bea7b1221898b3be718a296 (patch) | |
| tree | 43660e07ea40059549e3ee3ae001510152b8b421 /drivers/cpufreq/cpufreq_powersave.c | |
| parent | 9e8c0a899b2f89b8367d33668f6819892f0a00f2 (diff) | |
| download | linux-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_powersave.c')
| -rw-r--r-- | drivers/cpufreq/cpufreq_powersave.c | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/drivers/cpufreq/cpufreq_powersave.c b/drivers/cpufreq/cpufreq_powersave.c index b8b400232a74..691e573e46ee 100644 --- a/drivers/cpufreq/cpufreq_powersave.c +++ b/drivers/cpufreq/cpufreq_powersave.c @@ -20,10 +20,8 @@ static int cpufreq_governor_powersave(struct cpufreq_policy *policy, unsigned int event) { switch (event) { - case CPUFREQ_GOV_START: case CPUFREQ_GOV_LIMITS: - pr_debug("setting to %u kHz because of event %u\n", - policy->min, event); + pr_debug("setting to %u kHz\n", policy->min); __cpufreq_driver_target(policy, policy->min, CPUFREQ_RELATION_L); break; |