diff options
author | Paul Walmsley <paul@pwsan.com> | 2013-01-26 02:48:56 -0500 |
---|---|---|
committer | Paul Walmsley <paul@pwsan.com> | 2013-01-26 03:42:33 -0500 |
commit | aff2f7d90fc6553aa309db2a635d8e5d70d84916 (patch) | |
tree | 80fa1aa61a364aa6afaa1d14a92870e647954f5e /arch | |
parent | fa2002223e12c6b1bc96381b70c376afe4e01d80 (diff) |
ARM: OMAP2420: hwmod data/PM: use hwmod to block WFI when I2C active
Use the HWMOD_BLOCK_WFI flag in the hwmod data to prevent the MPU from
entering WFI when the I2C devices are active. No idea why this is needed;
this could certainly bear further investigation if anyone is interested.
The objective here is to remove some custom code from the OMAP24xx PM
code.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>
Diffstat (limited to 'arch')
-rw-r--r-- | arch/arm/mach-omap2/omap_hwmod_2420_data.c | 7 | ||||
-rw-r--r-- | arch/arm/mach-omap2/pm24xx.c | 13 |
2 files changed, 6 insertions, 14 deletions
diff --git a/arch/arm/mach-omap2/omap_hwmod_2420_data.c b/arch/arm/mach-omap2/omap_hwmod_2420_data.c index b5efe58c0be0..6a764af6c6d3 100644 --- a/arch/arm/mach-omap2/omap_hwmod_2420_data.c +++ b/arch/arm/mach-omap2/omap_hwmod_2420_data.c | |||
@@ -121,7 +121,12 @@ static struct omap_hwmod omap2420_i2c1_hwmod = { | |||
121 | }, | 121 | }, |
122 | .class = &i2c_class, | 122 | .class = &i2c_class, |
123 | .dev_attr = &i2c_dev_attr, | 123 | .dev_attr = &i2c_dev_attr, |
124 | .flags = HWMOD_16BIT_REG, | 124 | /* |
125 | * From mach-omap2/pm24xx.c: "Putting MPU into the WFI state | ||
126 | * while a transfer is active seems to cause the I2C block to | ||
127 | * timeout. Why? Good question." | ||
128 | */ | ||
129 | .flags = (HWMOD_16BIT_REG | HWMOD_BLOCK_WFI), | ||
125 | }; | 130 | }; |
126 | 131 | ||
127 | /* I2C2 */ | 132 | /* I2C2 */ |
diff --git a/arch/arm/mach-omap2/pm24xx.c b/arch/arm/mach-omap2/pm24xx.c index c333fa6dffa8..909ef53ba2ea 100644 --- a/arch/arm/mach-omap2/pm24xx.c +++ b/arch/arm/mach-omap2/pm24xx.c | |||
@@ -140,14 +140,6 @@ no_sleep: | |||
140 | return 0; | 140 | return 0; |
141 | } | 141 | } |
142 | 142 | ||
143 | static int omap2_i2c_active(void) | ||
144 | { | ||
145 | u32 l; | ||
146 | |||
147 | l = omap2_cm_read_mod_reg(CORE_MOD, CM_FCLKEN1); | ||
148 | return l & (OMAP2420_EN_I2C2_MASK | OMAP2420_EN_I2C1_MASK); | ||
149 | } | ||
150 | |||
151 | static int sti_console_enabled; | 143 | static int sti_console_enabled; |
152 | 144 | ||
153 | static int omap2_allow_mpu_retention(void) | 145 | static int omap2_allow_mpu_retention(void) |
@@ -172,11 +164,6 @@ static int omap2_allow_mpu_retention(void) | |||
172 | 164 | ||
173 | static void omap2_enter_mpu_retention(void) | 165 | static void omap2_enter_mpu_retention(void) |
174 | { | 166 | { |
175 | /* Putting MPU into the WFI state while a transfer is active | ||
176 | * seems to cause the I2C block to timeout. Why? Good question. */ | ||
177 | if (omap2_i2c_active()) | ||
178 | return; | ||
179 | |||
180 | /* The peripherals seem not to be able to wake up the MPU when | 167 | /* The peripherals seem not to be able to wake up the MPU when |
181 | * it is in retention mode. */ | 168 | * it is in retention mode. */ |
182 | if (omap2_allow_mpu_retention()) { | 169 | if (omap2_allow_mpu_retention()) { |