[19/27] cpufreq: s3c24xx: Don't validate the frequency table twice

Message ID fc79e745f14e9b038256de2546817b35b3846314.1519620578.git.viresh.kumar@linaro.org
State New
Headers show
  • Untitled series #9364
Related show

Commit Message

Viresh Kumar Feb. 26, 2018, 5:09 a.m.
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 s3c24xx driver.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

 drivers/cpufreq/s3c24xx-cpufreq.c | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)


To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


diff --git a/drivers/cpufreq/s3c24xx-cpufreq.c b/drivers/cpufreq/s3c24xx-cpufreq.c
index 6bebc1f9f55a..3f0947e119a9 100644
--- a/drivers/cpufreq/s3c24xx-cpufreq.c
+++ b/drivers/cpufreq/s3c24xx-cpufreq.c
@@ -351,11 +351,8 @@  struct clk *s3c_cpufreq_clk_get(struct device *dev, const char *name)
 static int s3c_cpufreq_init(struct cpufreq_policy *policy)
 	policy->clk = clk_arm;
 	policy->cpuinfo.transition_latency = cpu_cur.info->latency;
-	if (ftab)
-		return cpufreq_table_validate_and_show(policy, ftab);
+	policy->freq_table = ftab;
 	return 0;