Unified structure for thermal zone device registration
summary
Proposes replacing the long, growing thermal_zone_device_register argument list with a single-pointer parameter that points to an extensible parameter structure containing all registration fields, so future additions change only the struct not every caller. Notes a current patch set of 30 patches and recommends making the API switch first, then the three-point rework, to reduce churn. Discusses tradeoffs: caller-allocated struct for fast-boot systems and compatibility.
AI-written summary · about
chapters (7)
- 0:00Introduction to thermal zone registration
- 6:59Proposal for unified API structure
- 7:23Frequency invariance problem explained
- 14:40Micro-architecture capacity differences
- 20:00Challenges with turbo frequency assumptions
- 22:07Thermal pressure and scheduler impact
- 23:35Summary and next steps
related talks
34mImprovisation and Demonstration of Linux Thermal Framework for Multiple Temperature Sensors
48mThermal binning support
01h 00mAdvanced Levelization Techniques (part 3 of 3)
33mImproving System Configuration for Zephyr and Beyond
16mUnifying KVM API for protected VM and utilities
22mImproving fw_devlink dependency tracking
29mPCI Endpoint Subsystem Open Items Discussion
47mSubsystems with Object Lifetime Issues (in the Embedded Case)