AP Power Sequence Subsystem
summary
Describes an implemented Zephyr subsystem API that manages ACPI AP power states (G3, S5–S0) and runs on the Zephyr State Machine Framework, mapping each ACPI state into three hierarchy levels: architecture, chipset, application. Provides mandatory macros and APIs to register entry/run/exit handlers, post events, lock processing and receive notifications; enforces one transition per iteration and hierarchical entry/exit ordering. Warns that missing handlers or next-state entries block the state machine and that callbacks run in the driver thread, so careful locking is required.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:47Chrome OS EC background
- 3:55AP power sequence explained
- 5:07Motivation for AP power sequence
- 6:11AP power sequence overview
- 9:22Zephyr state machine framework
- 12:38Hierarchical state machine
- 13:43Execution flow of AP power sequence
- 15:09Implementing AP power sequence
- 18:44State transition entry/exit
- 20:06Ultimate hook pattern
- 21:54User interface and services
- 23:40Summary
related talks
41mExploring Zephyr Power Management: Overview and Implementation Guide
41mExploring Zephyr Power Management: Overview and Implementation Guide
36mPower Management on Zephyr
41mFuture of Zephyr Device Model
26mA Primer to Clocks and Power Management Through ARM SCMI
35mZephyr OS Memory Protection
34mZephyr Project: RTOS Start-up and Initialization Flow
23mA Dive into Zephyr Device Driver Model
