From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: cpufreq@vger.kernel.org, linux-kernel@vger.kernel.org,
Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH] cpufreq: cpufreq-cpu0: use the exact frequency for clk_set_rate()
Date: Wed, 27 Mar 2013 23:46:38 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.1303272345260.9558@axis700.grange> (raw)
In-Reply-To: <Pine.LNX.4.64.1302251820431.3030@axis700.grange>
Hi Shawn
On Mon, 25 Feb 2013, Guennadi Liakhovetski wrote:
> clk_set_rate() isn't supposed to accept approximate frequencies, instead
> a supported frequency should be obtained from clk_round_rate() and then
> used to set the clock.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Can I have your ack for this one, please?
Thanks
Guennadi
> ---
>
> Applies on top of my previous patch to fix unsigned freq_Hz "cpufreq: fix
> sign check of an unsigned variable in cpufreq-cpu0"
>
> drivers/cpufreq/cpufreq-cpu0.c | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cpufreq/cpufreq-cpu0.c b/drivers/cpufreq/cpufreq-cpu0.c
> index e7bad3c..6ce9b51 100644
> --- a/drivers/cpufreq/cpufreq-cpu0.c
> +++ b/drivers/cpufreq/cpufreq-cpu0.c
> @@ -45,7 +45,7 @@ static int cpu0_set_target(struct cpufreq_policy *policy,
> struct cpufreq_freqs freqs;
> struct opp *opp;
> unsigned long volt = 0, volt_old = 0, tol = 0;
> - long freq_Hz;
> + long freq_Hz, freq_exact;
> unsigned int index, cpu;
> int ret;
>
> @@ -60,6 +60,7 @@ static int cpu0_set_target(struct cpufreq_policy *policy,
> freq_Hz = clk_round_rate(cpu_clk, freq_table[index].frequency * 1000);
> if (freq_Hz < 0)
> freq_Hz = freq_table[index].frequency * 1000;
> + freq_exact = freq_Hz;
> freqs.new = freq_Hz / 1000;
> freqs.old = clk_get_rate(cpu_clk) / 1000;
>
> @@ -96,7 +97,7 @@ static int cpu0_set_target(struct cpufreq_policy *policy,
> }
> }
>
> - ret = clk_set_rate(cpu_clk, freqs.new * 1000);
> + ret = clk_set_rate(cpu_clk, freq_exact);
> if (ret) {
> pr_err("failed to set clock rate: %d\n", ret);
> if (cpu_reg)
> --
> 1.7.2.5
>
>
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next prev parent reply other threads:[~2013-03-27 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 17:22 Guennadi Liakhovetski
2013-03-27 22:46 ` Guennadi Liakhovetski [this message]
2013-03-28 2:07 ` Shawn Guo
2013-05-22 18:12 ` Guennadi Liakhovetski
2013-05-22 19:31 ` Rafael J. Wysocki
2013-06-05 11:25 ` Guennadi Liakhovetski
2013-06-05 12:15 ` Rafael J. Wysocki
2013-03-28 7:11 ` 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=Pine.LNX.4.64.1303272345260.9558@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®