Remote Core Power Management in AMP Systems
summary
Describes a concrete remoteproc suspend/resume flow for TI AM6/AM62-class SoCs that coordinates Linux, the TISCI prepare_sleep message, genpd aggregation of constraints, and DM selection of a locked low‑power mode; remote cores receive a suspend ping, query DM, and reply act/auto so the driver either sends shutdown or lets firmware self-manage, resume uses PM post‑suspend notifier to reload firmware if DM reports off, and suspend can be aborted if constraints conflict; patches are not yet upstreamed.
AI-written summary · about
chapters (12)
- 0:00Remote core power management intro
- 1:45Problem statement and agenda
- 2:27Understanding AMP systems
- 3:54Remoteproc role in power management
- 7:05Linux kernel PM phases
- 14:06Remoteproc driver differentiation issues
- 15:51Constraints in low power modes
- 17:39Remoteproc suspend/resume solution
- 21:31Remoteproc resume flow and implementation
- 23:38Registering PM hooks in remoteproc
- 24:42Upstreaming plans and challenges
- 27:39Q&A
related talks
36mLinux Power Management Features, Their Relationships and Interactions
59mDevice power management and idle- 36mLinux Power Management Features, Their Relationships and Interactions
32mAdding Runtime Power Management Capabilities to Device Drivers
25mMultiple system-wide low power-states
19mEnabling System Standby With RISC-V Platform
47mLinux Kernel Power Management - 101
41mThe Case for an SoC Power Management Driver