From: Viresh Kumar <viresh.kumar@linaro.org>
To: rjw@sisk.pl
Cc: linaro-kernel@lists.linaro.org, patches@linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>,
Shawn Guo <shawn.guo@linaro.org>
Subject: [PATCH 05/14] cpufreq: imx6q: use cpufreq_generic_init() routine
Date: Wed, 21 Aug 2013 20:12:24 +0530 [thread overview]
Message-ID: <0394a2f6338e937f5b29cdca883d22e04ee0cce4.1377093938.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1377093938.git.viresh.kumar@linaro.org>
In-Reply-To: <cover.1377093938.git.viresh.kumar@linaro.org>
Use generic cpufreq_generic_init() routine instead of replicating the same code
here.
Cc: Shawn Guo <shawn.guo@linaro.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
drivers/cpufreq/imx6q-cpufreq.c | 13 +------------
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/drivers/cpufreq/imx6q-cpufreq.c b/drivers/cpufreq/imx6q-cpufreq.c
index f35c674..5efd9b7 100644
--- a/drivers/cpufreq/imx6q-cpufreq.c
+++ b/drivers/cpufreq/imx6q-cpufreq.c
@@ -150,18 +150,7 @@ static int imx6q_set_target(struct cpufreq_policy *policy, unsigned int index)
static int imx6q_cpufreq_init(struct cpufreq_policy *policy)
{
- int ret;
-
- ret = cpufreq_table_validate_and_show(policy, freq_table);
- if (ret) {
- dev_err(cpu_dev, "invalid frequency table: %d\n", ret);
- return ret;
- }
-
- policy->cpuinfo.transition_latency = transition_latency;
- cpumask_setall(policy->cpus);
-
- return 0;
+ return cpufreq_generic_init(policy, freq_table, transition_latency);
}
static struct cpufreq_driver imx6q_cpufreq_driver = {
--
1.7.12.rc2.18.g61b472e
next prev parent reply other threads:[~2013-08-21 14:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 14:42 [PATCH 00/14] cpufreq: create & use cpufreq_generic_init() routine Viresh Kumar
2013-08-21 14:42 ` [PATCH 01/14] cpufreq: create " Viresh Kumar
2013-08-21 14:42 ` [PATCH 02/14] cpufreq: cpu0: use " Viresh Kumar
2013-08-21 14:42 ` [PATCH 03/14] cpufreq: dbx500: " Viresh Kumar
2013-08-21 23:00 ` Linus Walleij
2013-08-21 14:42 ` [PATCH 04/14] cpufreq: exynos: " Viresh Kumar
2013-08-21 14:42 ` Viresh Kumar [this message]
2013-08-21 14:42 ` [PATCH 06/14] cpufreq: kirkwood: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 07/14] cpufreq: maple: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 08/14] cpufreq: pasemi: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 09/14] cpufreq: pmac64: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 10/14] cpufreq: s3c: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 11/14] cpufreq: s5pv210: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 12/14] cpufreq: sa11x0: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 13/14] cpufreq: spear: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 14/14] cpufreq: tegra: " Viresh Kumar
2013-08-21 23:20 ` [PATCH 00/14] cpufreq: create & " Rafael J. Wysocki
2013-08-22 4:47 ` Viresh Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0394a2f6338e937f5b29cdca883d22e04ee0cce4.1377093938.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
--cc=shawn.guo@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).