Exploring Zephyr Power Management: Overview and Implementation Guide
summary
Describes concrete APIs, how the idle thread calls the PM subsystem and the policy manager to pick from seven platform-declared power states, and how devices get suspended and resumed (static vs runtime). Shows code-level names like pm_system_suspend and PM_POLICY_NEXT_STATE, explains config flags (config PM, PM_DEVICE, PM_DEVICE_RUNTIME), runtime sync/async flows and reference counting, and how power domains and latency/residency numbers determine whether transitions actually save energy.
AI-written summary · about
chapters (13)
- 0:00Introduction to Zephyr power management
- 2:10Design goals and key concepts
- 6:05System power management
- 13:58Power states and constraints
- 14:40Policy manager logic
- 15:44Device PM overview
- 19:19Runtime PM for devices
- 23:58Power domains grouping
- 25:24Enabling PM in Zephyr
- 26:27PM in system controllers
- 29:13PM in device drivers
- 32:22Advanced PM features
- 32:43Q&A
related talks
41mExploring Zephyr Power Management: Overview and Implementation Guide
36mPower Management on Zephyr
59mDevice power management and idle
48mPower Management Challenges in IoT and How Zephyr RTOS Meets Them
39mZephyr Power Management for Wearable Devices
26mAP Power Sequence Subsystem
46mDevice Power Management: Journey to 5uA
12mLightning Talk: Strengthening Zephyr’s Camera Framework: Architecture Review and Enhancements