| Message ID | b12a6112319a01d6d4e7420c551c32652fb7160b.1522653632.git.viresh.kumar@linaro.org |
|---|---|
| State | Accepted |
| Commit | b8b10bc2015cd91350aac68447377c8410a48865 |
| Headers | show |
| Series | cpufreq: CPPC: Don't set transition_latency | expand |
diff --git a/drivers/cpufreq/cppc_cpufreq.c b/drivers/cpufreq/cppc_cpufreq.c index 8300a9fcb80c..38f65c371139 100644 --- a/drivers/cpufreq/cppc_cpufreq.c +++ b/drivers/cpufreq/cppc_cpufreq.c @@ -162,7 +162,6 @@ static int cppc_cpufreq_cpu_init(struct cpufreq_policy *policy) cpu->perf_caps.highest_perf; policy->cpuinfo.max_freq = cppc_dmi_max_khz; - policy->cpuinfo.transition_latency = cppc_get_transition_latency(cpu_num); policy->transition_delay_us = cppc_get_transition_latency(cpu_num) / NSEC_PER_USEC; policy->shared_type = cpu->shared_type;
Now that the driver has started to set transition_delay_us directly, there is no need to set transition_latency along with it, as it is not used by the cpufreq core. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> --- drivers/cpufreq/cppc_cpufreq.c | 1 - 1 file changed, 1 deletion(-) -- 2.15.0.194.g9af6a3dea062