ARM: OMAP: GPIO de-bounce clocks don't affect module idle state
authorPaul Walmsley <paul@pwsan.com>
Mon, 11 May 2009 16:58:19 +0000 (09:58 -0700)
committerTony Lindgren <tony@atomide.com>
Tue, 12 May 2009 18:18:34 +0000 (11:18 -0700)
commit6f733a349c2b70a83b5451fbe61ef2cf67d41cdf
treedd076b990baf342e0f865a2def66649a2792ebaa
parent72af2b363107df9cd67985ecb8495bbdff3c9857
ARM: OMAP: GPIO de-bounce clocks don't affect module idle state

GPIO de-bounce clocks don't have any impact on the module idle state, so
the clock code should not wait for the module to enable after the de-bounce
clocks are enabled.

Problem found by Kevin Hilman <khilman@deeprootsystems.com>.

Signed-off-by: Paul Walmsley <paul@pwsan.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
arch/arm/mach-omap2/clock34xx.h