OMAP3: CPUidle: remove redundant setting of PER next power state
authorKevin Hilman <khilman@deeprootsystems.com>
Fri, 1 Oct 2010 15:35:47 +0000 (08:35 -0700)
committerKevin Hilman <khilman@deeprootsystems.com>
Fri, 1 Oct 2010 20:49:32 +0000 (13:49 -0700)
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@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
arch/arm/mach-omap2/cpuidle34xx.c

index 8ea012ef0b5a7f5b34ca9c6467ac1c942e71c3cb..703b5ec88e98af56bfbed229cbc717cf85cc5184 100644 (file)
@@ -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)