We must not attempt to wait for the CAM module to become ready after
clock enable, since it has no target IDLEST bit.
Thanks to Sergio Alberto Aguirre Rodriguez <[EMAIL PROTECTED]> for
reporting this and testing the patch.
Signed-off-by: Paul Walmsley <[EMAIL PROTECTED]>
Tested-by: Sergio Alberto Aguirre Rodriguez <[EMAIL PROTECTED]>
---
arch/arm/mach-omap2/clock.c | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/clock.c b/arch/arm/mach-omap2/clock.c
index be5c616..189b8a6 100644
--- a/arch/arm/mach-omap2/clock.c
+++ b/arch/arm/mach-omap2/clock.c
@@ -256,6 +256,10 @@ static void omap2_clk_wait_ready(struct clk *clk)
/* REVISIT: What are the appropriate exclusions for 34XX? */
if (cpu_is_omap34xx()) {
+ /* CAM */
+ if (prcm_mod == OMAP34XX_CM_REGADDR(OMAP3430_CAM_MOD, 0))
+ return;
+
/* SSI */
if (prcm_mod == OMAP34XX_CM_REGADDR(CORE_MOD, 0) &&
(reg & 0x0f) == 0 &&
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
