From: Nishanth Menon <nm@ti.com>
To: Eduardo Valentin <eduardo.valentin@nokia.com>
Cc: ext Kevin Hilman <khilman@deeprootsystems.com>,
Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: [PM-WIP-OPP] [PATCH 1/1] OMAP3: PM: cpu-omap: Check governor limits before applying mpu frequency
Date: Wed, 24 Mar 2010 07:40:58 -0500 [thread overview]
Message-ID: <4BAA085A.6060100@ti.com> (raw)
In-Reply-To: <1269428551-779-1-git-send-email-eduardo.valentin@nokia.com>
Eduardo Valentin had written, on 03/24/2010 06:02 AM, the following:
> From: Eduardo Valentin <eduardo.valentin@nokia.com>
>
> This patch fix the sequence inside omap_target while setting
> a frequency for OMAP3 devices.
>
> Previously any frequency was set, even if out of range. Now
> the range set by the governor is also checked for OMAP3.
>
> Signed-off-by: Eduardo Valentin <eduardo.valentin@nokia.com>
Good catch. thanks.
Acked-by: Nishanth Menon <nm@ti.com>
> ---
> arch/arm/plat-omap/cpu-omap.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/plat-omap/cpu-omap.c b/arch/arm/plat-omap/cpu-omap.c
> index a69b557..0674405 100644
> --- a/arch/arm/plat-omap/cpu-omap.c
> +++ b/arch/arm/plat-omap/cpu-omap.c
> @@ -88,7 +88,7 @@ static int omap_target(struct cpufreq_policy *policy,
> struct cpufreq_freqs freqs;
> #endif
> #if defined(CONFIG_ARCH_OMAP3) && !defined(CONFIG_OMAP_PM_NONE)
> - unsigned long freq = target_freq * 1000;
> + unsigned long freq;
> #endif
> int ret = 0;
>
> @@ -114,6 +114,7 @@ static int omap_target(struct cpufreq_policy *policy,
> ret = clk_set_rate(mpu_clk, freqs.new * 1000);
> cpufreq_notify_transition(&freqs, CPUFREQ_POSTCHANGE);
> #elif defined(CONFIG_ARCH_OMAP3) && !defined(CONFIG_OMAP_PM_NONE)
> + freq = target_freq * 1000;
> if (opp_find_freq_ceil(OPP_MPU, &freq))
> omap_pm_cpu_set_freq(freq);
> #endif
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2010-03-24 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 11:02 [PM-WIP-OPP] [PATCH 1/1] OMAP3: PM: cpu-omap: Check governor limits before applying mpu frequency Eduardo Valentin
2010-03-24 12:40 ` Nishanth Menon [this message]
2010-04-05 23:01 ` Kevin Hilman
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=4BAA085A.6060100@ti.com \
--to=nm@ti.com \
--cc=eduardo.valentin@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.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