aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/cpufreq
diff options
context:
space:
mode:
authorLukasz Luba <lukasz.luba@arm.com>2022-08-16 13:01:57 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2022-08-23 20:00:52 +0200
commit6ca7076fbfaeccce173aeab832d76b9e49e1034b (patch)
tree421c2817e4583ba99e30d227accb3d9628c611eb /drivers/cpufreq
parentLinux 6.0-rc2 (diff)
downloadlinux-dev-6ca7076fbfaeccce173aeab832d76b9e49e1034b.tar.xz
linux-dev-6ca7076fbfaeccce173aeab832d76b9e49e1034b.zip
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>
Diffstat (limited to 'drivers/cpufreq')
-rw-r--r--drivers/cpufreq/cpufreq.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 7820c4e74289..69b3d61852ac 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -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);