The Case for an SoC Power Management Driver
summary
Argues for a small SoC driver that registers generic PM domains and attaches them to child platform devices by splitting of_platform_default_populate so domains are set before devices are added. The implementation centralizes clock/regulator/reset sequencing inside a single PM-domain activate/dismiss implementation, moves per-driver PM code out into a platform data flag so drivers stop powering on at probe, and the prototype powers devices at probe and can power off unused resources.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:42SoC power management basics
- 3:46Current power management approaches
- 5:35Power management in ACPI
- 8:49Problems with current designs
- 12:19Previous and ongoing attempts
- 16:58Proposed solution with PM domains
- 19:51Barriers to implementation
- 22:25Proposed SoC PM driver architecture
- 23:56Implementation strategy
- 26:20Requirements and conclusion
- 31:36Q&A session
related talks
41mThe Case for an SoC Power Management Driver
29mPMIC: First One to Turn On and Last One to Turn Off
41mLinux Power Management Features & Their Interactions, Part 2
40mPower Management Integrated Circuits: Keep the Power in Your Hands
43mLinux Power! (from the Perspective of a PMIC Vendor)
39mDesigning a Multi-PMIC Linux Driver: Key Decisions for Effective Mainline Submission
57mImplementing ACPI 5 Features Device Enumeration and PM
46mEarly Platform Drivers in Linux Kernel