OMAP: hwmod: Do not disable clocks if hwmod already in idle
authorBenoit Cousson <b-cousson@ti.com>
Tue, 21 Sep 2010 16:34:08 +0000 (10:34 -0600)
committerPaul Walmsley <paul@pwsan.com>
Tue, 21 Sep 2010 21:10:52 +0000 (15:10 -0600)
commit3827f9492bdff045ae57fe67e65ce7e259ed4219
tree29667bce8477d1b067f5449fd1b0c6e5476fdfc9
parent9ee9fff92e02e8c5f84794b3a5ce47646c2dfc39
OMAP: hwmod: Do not disable clocks if hwmod already in idle

The disable function was disabling clocks and dependencies
from both enable and idle state. Since idle function is already
disabling both, an enable -> idle -> disable sequence will
try to disable twice the clocks and thus generate a
"Trying disable clock XXX with 0 usecount" warning.

Signed-off-by: Benoit Cousson <b-cousson@ti.com>
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Tested-by: Kevin Hilman <khilman@deeprootsystems.com>
arch/arm/mach-omap2/omap_hwmod.c