[PATCH 131/228] cpufreq: davinci: use cpufreq_generic_init() routine
Viresh Kumar
viresh.kumar at linaro.org
Fri Sep 13 09:01:17 EDT 2013
Use generic cpufreq_generic_init() routine instead of replicating the same code
here.
Cc: Sekhar Nori <nsekhar at ti.com>
Signed-off-by: Viresh Kumar <viresh.kumar at linaro.org>
---
drivers/cpufreq/davinci-cpufreq.c | 10 +---------
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/cpufreq/davinci-cpufreq.c b/drivers/cpufreq/davinci-cpufreq.c
index 55cf094..972583b 100644
--- a/drivers/cpufreq/davinci-cpufreq.c
+++ b/drivers/cpufreq/davinci-cpufreq.c
@@ -136,21 +136,13 @@ static int davinci_cpu_init(struct cpufreq_policy *policy)
return result;
}
- result = cpufreq_table_validate_and_show(policy, freq_table);
- if (result) {
- pr_err("%s: cpufreq_table_validate_and_show() failed",
- __func__);
- return result;
- }
-
/*
* Time measurement across the target() function yields ~1500-1800us
* time taken with no drivers on notification list.
* Setting the latency to 2000 us to accommodate addition of drivers
* to pre/post change notification list.
*/
- policy->cpuinfo.transition_latency = 2000 * 1000;
- return 0;
+ return cpufreq_generic_init(policy, freq_table, 2000 * 1000);
}
static struct cpufreq_driver davinci_driver = {
--
1.7.12.rc2.18.g61b472e
More information about the linux-arm-kernel
mailing list