Proceedings of the PM SW Workshop Jun 2010

From OMAPpedia

(Difference between revisions)
Jump to: navigation, search
Line 26: Line 26:
* '''RFC Patches'''
* '''RFC Patches'''
-
** [http://dev.omapzoom.org/pub/scm/swarch/linux-omap-adv.git RFC Patches]
+
** [http://dev.omapzoom.org/pub/scm/swarch/linux-omap-adv.git RFC Patches] Branch: hwmod_dss
-
Branch: hwmod_dss
+
 
 +
====Multi-level omap_device_idle===
 +
* '''Problem Statement'''
 +
** Today most drivers only use one level of device_idle by populating activate/ deactivate_func as omap_device_idle_hwmods/ omap_device_enable_hwmods
 +
** omap_device_idle_hwmods disables the device clocks, if they happen to be the last set of clocks in the clockdomian, the clockdomain transitions to inactive and the powerdomain to the target state programmed (Deepest possile by default)
 +
** How do we support multiple levels of device idling? So that drivers can prevent going to the deepest idle state incase latency is not acceptable.
 +
 
 +
* '''Proposed Solution'''
 +
** Use device latency constraint to control the powerdomain (of the device) target state.
 +
** Start with mapping the different device idle states with the different powerdomain states supported.
 +
** Keep the activate/deactivate_func same as before.
 +
 
 +
* '''RFC Patches'''
 +
Placeholder for patches from Vibhore to support device latency contraint

Revision as of 09:10, 11 June 2010

This wikipage contains proceedings of the PM SW Workshop held in Bangalore on 7-11 Jun, 2010

Contents

HWMOD Framework Enhancements

Reset Management Support in HWMOD

More Granular HWMOD Structures

=Multi-level omap_device_idle

Placeholder for patches from Vibhore to support device latency contraint

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox