History

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.

Lukasz Luba committed 4 years ago

Commit 6ca70761 parent 1c23f9e1 file · +1 −1Browse files

Unified · Split

drivers/cpufreq/cpufreq.c+1−1
@@ -532,7 +532,7 @@ static unsigned int __resolve_freq(struct cpufreq_policy *policy, · 531 unmodified lines
532 532
533 target_freq = clamp_val(target_freq, policy->min, policy->max);533 target_freq = clamp_val(target_freq, policy->min, policy->max);
534 534
535 if (!cpufreq_driver->target_index)535 if (!policy->freq_table)
536 return target_freq;536 return target_freq;
537 537
538 idx = cpufreq_frequency_table_target(policy, target_freq, relation);538 idx = cpufreq_frequency_table_target(policy, target_freq, relation);

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t