* [PATCH] OMAP: PM: Correct the use of cpufreq
@ 2009-06-23 9:53 ext-eero.nurkkala
2009-06-25 16:48 ` Kevin Hilman
0 siblings, 1 reply; 2+ messages in thread
From: ext-eero.nurkkala @ 2009-06-23 9:53 UTC (permalink / raw)
To: linux-omap; +Cc: Eero Nurkkala
From: Eero Nurkkala <ext-eero.nurkkala@nokia.com>
Wrong info was used to feed the cpufreq. It is possible
now to get below the user defined limit defined at
"/cpufreq/scaling_min_freq". With this patch, the
user defined limits are being obeyed instead of
always using the absolute max and min values supported
by the device.
Signed-off-by: Eero Nurkkala <ext-eero.nurkkala@nokia.com>
---
arch/arm/plat-omap/cpu-omap.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/plat-omap/cpu-omap.c b/arch/arm/plat-omap/cpu-omap.c
index 843e8af..1868c0d 100644
--- a/arch/arm/plat-omap/cpu-omap.c
+++ b/arch/arm/plat-omap/cpu-omap.c
@@ -78,10 +78,10 @@ static int omap_target(struct cpufreq_policy *policy,
/* Ensure desired rate is within allowed range. Some govenors
* (ondemand) will just pass target_freq=0 to get the minimum. */
- if (target_freq < policy->cpuinfo.min_freq)
- target_freq = policy->cpuinfo.min_freq;
- if (target_freq > policy->cpuinfo.max_freq)
- target_freq = policy->cpuinfo.max_freq;
+ if (target_freq < policy->min)
+ target_freq = policy->min;
+ if (target_freq > policy->max)
+ target_freq = policy->max;
freqs.old = omap_getspeed(0);
freqs.new = clk_round_rate(mpu_clk, target_freq * 1000) / 1000;
--
1.5.6.3
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] OMAP: PM: Correct the use of cpufreq
2009-06-23 9:53 [PATCH] OMAP: PM: Correct the use of cpufreq ext-eero.nurkkala
@ 2009-06-25 16:48 ` Kevin Hilman
0 siblings, 0 replies; 2+ messages in thread
From: Kevin Hilman @ 2009-06-25 16:48 UTC (permalink / raw)
To: ext-eero.nurkkala; +Cc: linux-omap
ext-eero.nurkkala@nokia.com writes:
> From: Eero Nurkkala <ext-eero.nurkkala@nokia.com>
>
> Wrong info was used to feed the cpufreq. It is possible
> now to get below the user defined limit defined at
> "/cpufreq/scaling_min_freq". With this patch, the
> user defined limits are being obeyed instead of
> always using the absolute max and min values supported
> by the device.
>
> Signed-off-by: Eero Nurkkala <ext-eero.nurkkala@nokia.com>
Thanks, pushing to current PM branch, and backporting to pm-2.6.29.
Kevin
> ---
> arch/arm/plat-omap/cpu-omap.c | 8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm/plat-omap/cpu-omap.c b/arch/arm/plat-omap/cpu-omap.c
> index 843e8af..1868c0d 100644
> --- a/arch/arm/plat-omap/cpu-omap.c
> +++ b/arch/arm/plat-omap/cpu-omap.c
> @@ -78,10 +78,10 @@ static int omap_target(struct cpufreq_policy *policy,
>
> /* Ensure desired rate is within allowed range. Some govenors
> * (ondemand) will just pass target_freq=0 to get the minimum. */
> - if (target_freq < policy->cpuinfo.min_freq)
> - target_freq = policy->cpuinfo.min_freq;
> - if (target_freq > policy->cpuinfo.max_freq)
> - target_freq = policy->cpuinfo.max_freq;
> + if (target_freq < policy->min)
> + target_freq = policy->min;
> + if (target_freq > policy->max)
> + target_freq = policy->max;
>
> freqs.old = omap_getspeed(0);
> freqs.new = clk_round_rate(mpu_clk, target_freq * 1000) / 1000;
> --
> 1.5.6.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-06-25 16:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-23 9:53 [PATCH] OMAP: PM: Correct the use of cpufreq ext-eero.nurkkala
2009-06-25 16:48 ` Kevin Hilman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox