Linux Power Management Features & Their Interactions, Part 2
summary
Covers how Linux runtime PM actually behaves with real drivers: many controllers use auto runtime PM so runtime gets/puts happen without runtime_suspend/runtime_resume callbacks, and auto suspend=1000ms reduces resume churn; power domains move from ad hoc dev_pm_domain to genpd on/off callbacks exposed by a provider (TI K3 PDS example) with one domain per device and optional domain hierarchies; PM QoS PM QoS resume-latency aggregates minima across the device tree so zero blocks suspend, and clocks/IRQ wake handling are handled by domain helpers.
AI-written summary · about
chapters (6)
- 0:00Linux power management intro
- 3:54Power management trade-offs
- 11:23Runtime PM APIs
- 24:00Power domains in kernel
- 35:39Power management QoS
- 40:37Additional PM features
related talks
36mLinux Power Management Features, Their Relationships and Interactions- 36mLinux Power Management Features, Their Relationships and Interactions
59mDevice power management and idle
47mLinux Kernel Power Management - 101
32mAdding Runtime Power Management Capabilities to Device Drivers
25mMultiple system-wide low power-states
43mLinux Power! (from the Perspective of a PMIC Vendor)
41mThe Case for an SoC Power Management Driver