Home Explore Help
Sign In
GfA
/
linux_kernel
5
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Browse Source

cpufreq: CPPC: Don't set transition_latency

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>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Viresh Kumar 7 years ago
parent
44a264ee1e
commit
b8b10bc201
1 changed files with 0 additions and 1 deletions
Unified View Show Diff Stats
  1. 0 1
      drivers/cpufreq/cppc_cpufreq.c

+ 0 - 1
drivers/cpufreq/cppc_cpufreq.c
View File 

@@ -162,7 +162,6 @@ static int cppc_cpufreq_cpu_init(struct cpufreq_policy *policy)
 
 		cpu->perf_caps.highest_perf;
 
 		cpu->perf_caps.highest_perf;
 
 	policy->cpuinfo.max_freq = cppc_dmi_max_khz;
 
 	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) /
 
 	policy->transition_delay_us = cppc_get_transition_latency(cpu_num) /
 
 		NSEC_PER_USEC;
 
 		NSEC_PER_USEC;
 
 	policy->shared_type = cpu->shared_type;
 
 	policy->shared_type = cpu->shared_type;