OMAP2/3/4 core: create omap_device layer

The omap_device code provides a mapping of omap_hwmod structures into
the platform_device system, and includes some details on external
(board-level) integration.  This allows drivers to enable, idle, and
shutdown on-chip device resources, including clocks, regulators, etc.
The resources enabled and idled are dependent on the device's maximum
wakeup latency constraint (if present).

At the moment, omap_device functions are intended to be called from
platform_data function pointers.  Ideally in the future these
functions will be called from either subarchitecture-specific
platform_data activate, deactivate functions, or via an custom
bus/device type for OMAP.

Signed-off-by: Paul Walmsley <[email protected]>
Cc: Benoit Cousson <[email protected]>
Cc: Kevin Hilman <[email protected]>
Cc: Tony Lindgren <[email protected]>
Cc: Rajendra Nayak <[email protected]>
Cc: Vikram Pandita <[email protected]>
Cc: Sakari Poussa <[email protected]>
Cc: Anand Sawant <[email protected]>
Cc: Santosh Shilimkar <[email protected]>
Cc: Eric Thomas <[email protected]>
Cc: Richard Woodruff <[email protected]>

0 files changed, 0 insertions, 0 deletions