From: Viresh Kumar <viresh.kumar@linaro.org>
To: rjw@rjwysocki.net
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, arvind.chauhan@arm.com,
swarren@nvidia.com, nicolas.pitre@linaro.org,
swarren@wwwdotorg.org, dianders@chromium.org,
linux@arm.linux.org.uk, thomas.abraham@linaro.org,
pdeschrijver@nvidia.com, Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH V3 3/4] cpufreq: Tegra: drop wrapper around tegra_update_cpu_speed()
Date: Sat, 17 May 2014 10:21:22 +0530 [thread overview]
Message-ID: <898b7b84ba61d89bc2cebb63111a745ec633a02e.1400302114.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1400302114.git.viresh.kumar@linaro.org>
In-Reply-To: <cover.1400302114.git.viresh.kumar@linaro.org>
Tegra has implemented an unnecessary wrapper over tegra_update_cpu_speed(), i.e.
tegra_target(), which wasn't doing anything apart of calling
tegra_update_cpu_speed(). Get rid of that and use tegra_target() directly.
Tested-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
drivers/cpufreq/tegra-cpufreq.c | 9 ++-------
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/drivers/cpufreq/tegra-cpufreq.c b/drivers/cpufreq/tegra-cpufreq.c
index 63f0059..6e774c6 100644
--- a/drivers/cpufreq/tegra-cpufreq.c
+++ b/drivers/cpufreq/tegra-cpufreq.c
@@ -82,9 +82,9 @@ out:
return ret;
}
-static int tegra_update_cpu_speed(struct cpufreq_policy *policy,
- unsigned long rate)
+static int tegra_target(struct cpufreq_policy *policy, unsigned int index)
{
+ unsigned long rate = freq_table[index].frequency;
int ret = 0;
/*
@@ -106,11 +106,6 @@ static int tegra_update_cpu_speed(struct cpufreq_policy *policy,
return ret;
}
-static int tegra_target(struct cpufreq_policy *policy, unsigned int index)
-{
- return tegra_update_cpu_speed(policy, freq_table[index].frequency);
-}
-
static int tegra_cpu_init(struct cpufreq_policy *policy)
{
int ret;
--
2.0.0.rc2
next prev parent reply other threads:[~2014-05-17 4:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 4:51 [PATCH V3 0/4] cpufreq: add support for intermediate (stable) Viresh Kumar
2014-05-17 4:51 ` [PATCH V3 1/4] cpufreq: handle calls to ->target_index() in separate routine Viresh Kumar
2014-05-20 16:44 ` Doug Anderson
2014-05-17 4:51 ` [PATCH V3 2/4] cpufreq: add support for intermediate (stable) frequencies Viresh Kumar
2014-05-20 16:48 ` Doug Anderson
2014-05-21 4:14 ` Viresh Kumar
2014-05-17 4:51 ` Viresh Kumar [this message]
2014-05-20 16:48 ` [PATCH V3 3/4] cpufreq: Tegra: drop wrapper around tegra_update_cpu_speed() Doug Anderson
2014-05-17 4:51 ` [PATCH V3 4/4] cpufreq: Tegra: implement intermediate frequency callbacks Viresh Kumar
2014-05-20 16:49 ` Doug Anderson
2014-05-21 4:21 ` 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=898b7b84ba61d89bc2cebb63111a745ec633a02e.1400302114.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=arvind.chauhan@arm.com \
--cc=dianders@chromium.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.pitre@linaro.org \
--cc=pdeschrijver@nvidia.com \
--cc=rjw@rjwysocki.net \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=thomas.abraham@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).