Arm SoCs expose a lot of information to software about Hardware knobs for controlling power consumption. As there is no Hardware 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 Hardware structure.
The Power Management Working Group shall endeavor to identify design patterns that help with the implementation of the majority of the usecases that vendors care about. To this end, the Power Management Working Group will look at the entire software stack (kernel, middleware, applications and tools) to help optimize power consumption. The Power Management Working Group is responsible for creating infrastructure, guidelines and tools to enable top-notch power management on Arm SoCs.
- Governance: Linaro Technical Steering Committee (MEMBERS ONLY)
- Mailing lists: EAS Dev, Sched-Tools
- Engineering: Power Management Engineering Wiki
- JIRA Project: Project Summary, JIRA Board, JIRA Structure