Skip to content

Commit 6ca7076

Browse files
lukaszluba-armrafaeljw
authored andcommitted
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>
1 parent 1c23f9e commit 6ca7076

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

drivers/cpufreq/cpufreq.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -532,7 +532,7 @@ static unsigned int __resolve_freq(struct cpufreq_policy *policy,
532532

533533
target_freq = clamp_val(target_freq, policy->min, policy->max);
534534

535-
if (!cpufreq_driver->target_index)
535+
if (!policy->freq_table)
536536
return target_freq;
537537

538538
idx = cpufreq_frequency_table_target(policy, target_freq, relation);

0 commit comments

Comments
 (0)