[PATCH 1/2] OMAP3: CPUidle: remove redundant setting of PER next power state
Kevin Hilman
khilman at deeprootsystems.com
Fri Oct 1 17:01:19 EDT 2010
When checking how to program the next powerstate for the PER
powerdomain, the next state of PER powerdomain was written twice.
Remove the duplicate write.
Reported-by: Santosh Shilimkar <santosh.shilimkar at ti.com>
Signed-off-by: Kevin Hilman <khilman at deeprootsystems.com>
---
arch/arm/mach-omap2/cpuidle34xx.c | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/cpuidle34xx.c b/arch/arm/mach-omap2/cpuidle34xx.c
index 8ea012e..703b5ec 100644
--- a/arch/arm/mach-omap2/cpuidle34xx.c
+++ b/arch/arm/mach-omap2/cpuidle34xx.c
@@ -272,10 +272,8 @@ static int omap3_enter_idle_bm(struct cpuidle_device *dev,
*/
per_next_state = per_saved_state = pwrdm_read_next_pwrst(per_pd);
if ((per_next_state == PWRDM_POWER_OFF) &&
- (core_next_state > PWRDM_POWER_RET)) {
+ (core_next_state > PWRDM_POWER_RET))
per_next_state = PWRDM_POWER_RET;
- pwrdm_set_next_pwrst(per_pd, per_next_state);
- }
/* Are we changing PER target state? */
if (per_next_state != per_saved_state)
--
1.7.2.1
More information about the linux-arm-kernel
mailing list