Differences between revisions 47 and 48
Revision 47 as of 2010-11-03 06:11:16
Size: 2759
Editor: ABTS-mum-Dynamic-024
Revision 48 as of 2010-11-11 09:20:48
Size: 2835
Editor: ABTS-mum-dynamic-147
Comment: re-org
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
==== Tasks ====
 1. [[/TaskList|Master Task List]]
 1. [[http://people.canonical.com/~pitti/workitems/linaro-pm-wg/all.html|Task assignments + Burndown chart for the PM WG]]
 1. [[WorkingGroups/PowerManagement/Doc/QA|Quality Assurance]]
Line 22: Line 17:
==== Tasks ====
 1. [[http://people.canonical.com/~pitti/workitems/linaro-pm-wg/all.html|Task assignments + Burndown chart for the PM WG]]
 1. [[WorkingGroups/PowerManagement/Doc/QA|Quality Assurance (QA) Proposal]]
 1. [[/TaskList|Master Task List: Laundry list of things that need to be looked at (someday)]]
Line 24: Line 24:
 * [[WorkingGroups/PowerManagement/Meetings | Meeting Minutes]]
Line 33: Line 32:
   * [[WorkingGroups/PowerManagement/Meetings | Meeting Minutes]]

Power Management

PDF version for distribution

ARM SoCs expose to software a lot of information about HW knobs for controlling power consumption. As there is no device/system HW to OS abstraction layer (such as ACPI), these knobs tend to be controlled directly by OS drivers. Additionally, each SoC vendor exposes a superset of the standard ARM power states to allow fine-grained control over each component to maximize battery-life. This increases the complexity of the core SoC enablement code inside the kernel as well as the peripheral drivers.

SoC vendors have taken slightly different approaches to implementing their OS power management frameworks. The differences arise for a number of reasons: a lack of design patterns to achieve what they require; due to lack of infrastructure support inside the kernel, and, on occasion, because of intrinsic differences in HW structure.

The Power Management WG shall endeavor to identify design patterns that helps with the implementation of the majority of the usecases that vendors care about, without having to invent new infrastructure. To this end, the WG will look at the entire software stack (kernel, middleware, applications and tools) to help optimize power consumption. The WG is responsible for creating infrastructure, guidelines and tools to enable top-notch power management on multiple ARM SoCs.

Developer Resources


  1. Blueprints being worked on

  2. 11.05 - Specifications

  3. 10.10 - Old Specification


  1. Task assignments + Burndown chart for the PM WG

  2. Quality Assurance (QA) Proposal

  3. Master Task List: Laundry list of things that need to be looked at (someday)




  1. git.linaro.org


WorkingGroups/PowerManagement (last modified 2020-02-25 13:36:32)