Exploring Zephyr Power Management: Overview and Implementation Guide
summary
Zephyr’s power management uses the idle thread to call the PM subsystem with ticks to the next event and a policy that picks the deepest state whose min_residency < time_to_next_event, mapping hardware into seven states from active to soft‑off. Device PM is split into static (system suspend/resume) and runtime (refcounted, synchronous or async flows using pm_device_runtime_get/put and pm_device_runtime_put_async), with power domains grouping children and notifications. Enable with CONFIG_PM, CONFIG_PM_DEVICE, CONFIG_DEVICE_RUNTIME; drivers implement an action callback and SOC PM ops (pm_state_set/exit_post).
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:11Design objectives
- 3:30Key concepts and areas
- 6:04System power management
- 10:40Power states and policy
- 14:19Policy manager details
- 15:50Device power management
- 23:37Power domains
- 25:04Implementation guidelines
- 32:43Q&A session
related talks
41mExploring Zephyr Power Management: Overview and Implementation Guide
36mPower Management on Zephyr
39mZephyr Power Management for Wearable Devices
48mPower Management Challenges in IoT and How Zephyr RTOS Meets Them
59mDevice power management and idle
26mAP Power Sequence Subsystem
41mFuture of Zephyr Device Model
40mOptimizing Zephyr for Peak Performance