Thread (7 messages) 7 messages, 2 authors, 2018-03-12

Lifecycle

  1. Posted viresh.kumar@linaro.org (Viresh Kumar)

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

From: viresh.kumar@linaro.org (Viresh Kumar)
Date: 2018-02-26 05:09:02
Also in: linux-pm, linux-samsung-soc
Subsystem: arm/samsung s3c, s5p and exynos arm architectures, cpu frequency scaling framework, the rest · Maintainers: Krzysztof Kozlowski, "Rafael J. Wysocki", Viresh Kumar, Linus Torvalds

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(-)
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;
 }
-- 
2.15.0.194.g9af6a3dea062
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help