Differences between revisions 94 and 95
Revision 94 as of 2013-02-21 15:18:38
Size: 16795
Editor: ABTS-MH-dynamic-082
Comment:
Revision 95 as of 2013-03-22 20:10:52
Size: 17814
Editor: customer-219
Comment: Added Benoit Cousson
Deletions are marked like this. Additions are marked like this.
Line 41: Line 41:
||<^>Benoit Cousson ||<^:>+0100||<-2#FF8888 style="font-size:x-small;"> ||<-2#FF8888 style="font-size:x-small;"> ||<-2#FF8888 style="font-size:x-small;"> ||<-2#FF8888 style="font-size:x-small;"> ||<-2#FF8888 style="font-size:x-small;"> ||<-2#FF8888 style="font-size:x-small;"> ||<-2#FF8888 style="font-size:x-small;"> ||<-2#FFFF88 style="font-size:x-small;"> ||<-2#88FF88 style="font-size:x-small;"> ||<-2#88FF88 style="font-size:x-small;"> ||<-2#88FF88 style="font-size:x-small;"> ||<-2#88FF88 style="font-size:x-small;"> ||<-2#88FF88 style="font-size:x-small;"> ||<-2#88FF88 style="font-size:x-small;"> ||<-2#88FF88 style="font-size:x-small;"> ||<-2#88FF88 style="font-size:x-small;"> ||<-2#88FF88 style="font-size:x-small;"> ||<-2#FFFF88 style="font-size:x-small;"> ||<-2#FFFF88 style="font-size:x-small;"> ||<-2#FF8888 style="font-size:x-small;"> ||<-2#FF8888 style="font-size:x-small;"> ||<-2#FF8888 style="font-size:x-small;"> ||<-2#FF8888 style="font-size:x-small;"> ||<-2#FF8888 style="font-size:x-small;"> ||

Power Management

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. 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

Blueprints and Specifications

  1. 11.05: The Matrix (PM Feature set across various SoC)

  2. All Blueprints

  3. Detailed specifications of larger projects

Getting involved

Communication

Team Availability

legend

usually unavailable

can be available once in a while

usually available


name

TZ

availability (UTC)

00

01

02

03

04

05

06

07

08

09

10

11

12

13

14

15

16

17

18

19

20

21

22

23

Amit Kucheria

+0530

Benoit Cousson

+0100

Chander Kashyap

+0530

Daniel Lezcano

+0100

Hongbo Zhang

+0800

Kevin Hilman

-0800

Mike Turquette

-0800

Rajagopal Venkat

+0530

Sanjay Singh Rawat

+0530

Serge Broslavsky

+0200

Vincent Guittot

+0200

Viresh Kumar

+0530

Sources

  1. Powerdebug git repo

  2. Powertop git repo

  3. PM QA scripts for automated validation of PM features

Members

Process

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