Linux 7.1 Merges AMD Dynamic EPP Fixes, Intel Bartlett Lake Scaling Fix

Key Takeaways

• Dynamic EPP now requires boot‑time module parameter, not Kconfig option.
• AMD P‑State driver bug fixes improve stability on Ryzen laptops.
• Intel P‑State driver corrected false 7 GHz report on Bartlett Lake CPUs.
• Raptor Lake E scaling factor fixed, ensuring accurate frequency management.

Pulse Analysis

Linux kernel releases are the primary conduit for hardware‑level enhancements, and the 7.1 power‑management merge underscores that trend. AMD’s Dynamic Energy Performance Preference (EPP) was introduced to let the kernel autonomously shift performance profiles based on AC or DC power states. Early implementations suffered from configuration quirks, prompting the recent change that removes the Kconfig toggle in favor of a boot‑time module parameter. This shift not only simplifies the build process but also paves the way for future default enablement once stability is confirmed, benefiting Ryzen‑based ultrabooks that rely on fine‑grained power tuning.

On the Intel side, the P‑State driver—responsible for translating CPU frequency requests into hardware actions—contained two critical bugs. The first caused the driver to erroneously broadcast a 7 GHz frequency on the newly released Bartlett Lake P‑core‑only silicon, a figure far beyond the chip’s actual capability. The second bug misapplied the scaling factor on Raptor Lake E CPUs, leading to sub‑optimal frequency scaling under load. By correcting these calculations, the kernel now reports accurate frequencies, reducing thermal spikes and improving power efficiency for a broad range of desktop and mobile platforms.

These fixes have immediate ripple effects for OEMs and end users alike. Laptop manufacturers can ship devices with confidence that the kernel will manage power states correctly, translating to longer battery runtimes and more predictable thermals. For developers, the clarified configuration path for Dynamic EPP reduces integration friction, encouraging broader adoption across Linux distributions. Looking ahead, the rapid incorporation of such hardware‑specific patches signals a healthy collaboration between silicon vendors and the open‑source community, ensuring that future architectures—whether AMD’s Zen 4 successors or Intel’s upcoming Meteor Lake—receive timely kernel support.