Proceedings of the PM SW Workshop Jun 2010

From OMAPpedia

(Difference between revisions)
Jump to: navigation, search
(Proposed Implementation)
Line 119: Line 119:
===Proposed Implementation===
===Proposed Implementation===
-
* OMAP PM layer - API’s exported to driver are defined here
+
* '''OMAP PM layer - API’s exported to driver are defined here'''
-
* Are all drivers going to be of type omap_device?
+
** Are all drivers going to be of type omap_device?
-
* Design for existing omap-pm vs. omap_device layer?
+
** Design for existing omap-pm vs. omap_device layer?
-
* -1 to release constraint, otherwise 0 or higher (acceptable latency in us)
+
** -1 to release constraint, otherwise 0 or higher (acceptable latency in us)
-
* We can’t assume that only releasing the constraint will lower power
+
** We can’t assume that only releasing the constraint will lower power
-
* Lowering the constraint can still trigger power state change   
+
** Lowering the constraint can still trigger power state change   
-
void omap_pm_set_max_dev_wakeup_lat(struct device *dev, long t)
+
void omap_pm_set_max_dev_wakeup_lat(struct device *dev, long t)
-
{
+
{
-
/*  existing code */
+
/*  existing code */
-
1. Look for devices’ power domain (might be multiple step if starting with general device)
+
1. Look for devices’ power domain (might be multiple step if starting with general device)
-
2. Use device name as identifier for constraint request
+
2. Use device name as identifier for constraint request
-
 
+
-
if (t == -1)
+
if (t == -1)
-
pwrdm_release_wakeup_lat_constraint (pwrdm, lat_dev_name);
+
pwrdm_release_wakeup_lat_constraint (pwrdm, lat_dev_name);
-
else
+
else
-
pwrdm_set_wakeup_lat_constraint (pwrdm, lat_dev_name, t);
+
pwrdm_set_wakeup_lat_constraint (pwrdm, lat_dev_name, t);
-
}
+
}

Revision as of 10:12, 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

Miscellaneous Issues

Minutes


Power Domain And Clock Domain Cleanup

Aligned on the following two phase approach


SRF Replacement - Constraints Part

Types of Latency Constraints

Details of Interrupt Latency

Details of Device Latency

Proposed Implementation

void omap_pm_set_max_dev_wakeup_lat(struct device *dev, long t)
{
	/*  existing code */	
	1. Look for devices’ power domain (might be multiple step if starting  with general device)
	2. Use device name as identifier for constraint request

	if (t == -1)
		pwrdm_release_wakeup_lat_constraint (pwrdm, lat_dev_name);
	else
		 pwrdm_set_wakeup_lat_constraint (pwrdm, lat_dev_name, t);
}
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox