mirror of
				https://github.com/torvalds/linux.git
				synced 2025-11-04 02:30:34 +02:00 
			
		
		
		
	cpufreq: check only freq_table in __resolve_freq()
There is no need to check if the cpufreq driver implements callback cpufreq_driver::target_index. The logic in the __resolve_freq uses the frequency table available in the policy. It doesn't matter if the driver provides 'target_index' or 'target' callback. It just has to populate the 'policy->freq_table'. Thus, check only frequency table during the frequency resolving call. Acked-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
This commit is contained in:
		
							parent
							
								
									1c23f9e627
								
							
						
					
					
						commit
						6ca7076fbf
					
				
					 1 changed files with 1 additions and 1 deletions
				
			
		| 
						 | 
				
			
			@ -532,7 +532,7 @@ static unsigned int __resolve_freq(struct cpufreq_policy *policy,
 | 
			
		|||
 | 
			
		||||
	target_freq = clamp_val(target_freq, policy->min, policy->max);
 | 
			
		||||
 | 
			
		||||
	if (!cpufreq_driver->target_index)
 | 
			
		||||
	if (!policy->freq_table)
 | 
			
		||||
		return target_freq;
 | 
			
		||||
 | 
			
		||||
	idx = cpufreq_frequency_table_target(policy, target_freq, relation);
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
		Reference in a new issue