Proceedings of the PM SW Workshop Jun 2010

From OMAPpedia

(Difference between revisions)
Jump to: navigation, search
Line 28: Line 28:
** [http://dev.omapzoom.org/pub/scm/swarch/linux-omap-adv.git RFC Patches] Branch: hwmod_dss
** [http://dev.omapzoom.org/pub/scm/swarch/linux-omap-adv.git RFC Patches] Branch: hwmod_dss
-
====Multi-level omap_device_idle===
+
===Multi-level omap_device_idle===
* '''Problem Statement'''
* '''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
** Today most drivers only use one level of device_idle by populating activate/ deactivate_func as omap_device_idle_hwmods/ omap_device_enable_hwmods
Line 41: Line 41:
* '''RFC Patches'''
* '''RFC Patches'''
Placeholder for patches from Vibhore to support device latency contraint
Placeholder for patches from Vibhore to support device latency contraint
 +
 +
===Access to HWMOD Internal Data===
 +
* '''Problem Statement'''
 +
** Information stored in hwmod structs are not directly accessible to drivers. There might be instances when this is needed.
 +
** E.g. A driver requesting for optional clocks can do away with knowing the clock name string.
 +
** Syslink, which needs to request for i2c1 clocks can request for i2c hmwod main_clk.
 +
 +
* '''Proposed Solution'''
 +
** Discuss and identify a list of all the hwmod internal data that might be needed by drivers and define apis for each of them - Rajendra

Revision as of 09:13, 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

Access to HWMOD Internal Data

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox