cpufreq: SCMI: Don't validate the frequency table twice
The cpufreq core is already validating the CPU frequency table after calling the ->init() callback of the cpufreq drivers and the drivers don't need to do the same anymore. Though they need to set the policy->freq_table field directly from the ->init() callback now. Stop validating the frequency table from SCMI driver. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> Acked-by: Sudeep Holla <sudeep.holla@arm.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
This commit is contained in:
parent
8913315e94
commit
d983af9864
1 changed files with 1 additions and 9 deletions
|
@ -159,13 +159,7 @@ static int scmi_cpufreq_init(struct cpufreq_policy *policy)
|
||||||
priv->domain_id = handle->perf_ops->device_domain_id(cpu_dev);
|
priv->domain_id = handle->perf_ops->device_domain_id(cpu_dev);
|
||||||
|
|
||||||
policy->driver_data = priv;
|
policy->driver_data = priv;
|
||||||
|
policy->freq_table = freq_table;
|
||||||
ret = cpufreq_table_validate_and_show(policy, freq_table);
|
|
||||||
if (ret) {
|
|
||||||
dev_err(cpu_dev, "%s: invalid frequency table: %d\n", __func__,
|
|
||||||
ret);
|
|
||||||
goto out_free_cpufreq_table;
|
|
||||||
}
|
|
||||||
|
|
||||||
/* SCMI allows DVFS request for any domain from any CPU */
|
/* SCMI allows DVFS request for any domain from any CPU */
|
||||||
policy->dvfs_possible_from_any_cpu = true;
|
policy->dvfs_possible_from_any_cpu = true;
|
||||||
|
@ -179,8 +173,6 @@ static int scmi_cpufreq_init(struct cpufreq_policy *policy)
|
||||||
policy->fast_switch_possible = true;
|
policy->fast_switch_possible = true;
|
||||||
return 0;
|
return 0;
|
||||||
|
|
||||||
out_free_cpufreq_table:
|
|
||||||
dev_pm_opp_free_cpufreq_table(cpu_dev, &freq_table);
|
|
||||||
out_free_priv:
|
out_free_priv:
|
||||||
kfree(priv);
|
kfree(priv);
|
||||||
out_free_opp:
|
out_free_opp:
|
||||||
|
|
Loading…
Reference in a new issue