OMAP: hwmod: add non-locking versions of enable and idle functions
authorKevin Hilman <khilman@deeprootsystems.com>
Mon, 26 Jul 2010 22:34:29 +0000 (16:34 -0600)
committerPaul Walmsley <paul@pwsan.com>
Mon, 26 Jul 2010 22:34:29 +0000 (16:34 -0600)
commit848240223c35fcc71c424ad51a8e8aef42d3879c
tree6c11872b61e0aa4eed0db43e362cdbac8c7c9284
parentfa98347ebf1c516e49694e1584cd96a63428676a
OMAP: hwmod: add non-locking versions of enable and idle functions

Some hwmods may need to be idled/enabled in atomic context, so
non-locking versions of these functions are required.

Most users should not need these and usage of theses should be
controlled to understand why access is being done in atomic context.
For this reason, the non-locking functions are only exposed at the
hwmod level and not at the omap-device level.

The use-case that led to the need for the non-locking versions is
hwmods that are enabled/idled from within the core idle/suspend path.
Since interrupts are already disabled here, the mutex-based locking in
hwmod can sleep and will cause potential deadlocks.

Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Paul Walmsley <paul@pwsan.com>
arch/arm/mach-omap2/omap_hwmod.c
arch/arm/plat-omap/include/plat/omap_hwmod.h