AMD prepares an official driver to adjust the limits of Ryzen from Linux
AMD has sent an official driver for review to adjust various power and current limits for Ryzen processors from Linux. He project is called AOD, acronym for AMD Overclocking Driverand uses an interface in the platform firmware to expose those controls to the operating system.
The proposal is not yet part of the kernel. The changes were submitted to the development list on October 10 and became more widely known on the 21st. For now there is also no AMD graphics application to use them: the first patch is intended to offer an interface through sysfs.
Three limits that can be configured from Linux
The controller allows writing PPT, TDC and EDC values. PPT sets the power limit that the processor can consume; TDC and EDC refer to current limits in sustained conditions and in short duration spikes, respectively. The patch allows you to query the supported range and available increments before entering a value.
It is a practical difference for those who adjust their equipment from Linux. Until now, these options usually depended on the UEFI configuration or tools other than the manufacturer. With AOD, access would be through a brand-maintained kernel interface, provided the platform has the necessary firmware support and patches end up being integrated.
The existence of that interface does not guarantee that any Ryzen supports all controls. Availability depends on the processor, motherboard, and how its firmware exposes functions. Nor does it imply that modifying these limits automatically produces more performance: the final behavior is still conditioned by the cooling and restrictions of the system itself.
Power changes require restart
There is one important limitation in this first version: the new PPT, TDC and EDC values are saved in the firmware and They take effect after restarting the computer. They are not settings applied immediately during a test or match.
The firmware also does not tell the controller what the currently active limits are.. Therefore, the corresponding attributes are used to write a configuration, but not to read the actual value. Yes, it is possible to consult the allowed intervals. This separation should be taken into account when comparing the patch with other ways to modify the limits of a Ryzen.
The documentation distinguishes AOD from HSMP, another management interface present on certain AMD platforms. AOD changes a persistent firmware setting associated with the Precision Boost Overdrive PPT limit. HSMP can alter a boundary while running, but that change is lost upon reboot. They are different mechanisms and the new controller does not replace all the possibilities of the second one.
SMT control is also contemplated
Patches include a switch to enable or disable SMT at the platform level. SMT allows a physical core to execute more than one logical thread. Linux already has ways to stop using those threads, but the feature provided in AOD works through the firmware instead of just disabling them from the kernel.
Another exposed data is the current memory frequencyalthough in this case it can only be read. The first version is therefore limited to a few specific parameters. The firmware recognizes more commands and the controller could expand its functions in future revisions, but it should not be attributed today with options that have not yet been implemented.
The proposal also reserves a debugging path to access firmware WMI methods. That route does not present itself as a stable interface for applications, so programs intended for users should rely on documented sysfs controls if the code is eventually accepted.
Ryzen Master does not come to Linux with these patches
AMD has not released a version of Ryzen Master for Linux along with these patches. AOD is a kernel driverwithout windows, graphical profiles or an official desktop tool announced. A future app could take advantage of its controls, but right now that would be a development possibility, not an available feature.
The series consists of three patches signed by the AMD engineer Shyam Sundar SK. In addition to the driver itself, it organizes the company’s WMI drivers in the kernel’s x86 tree. The code is subject to public review, a process in which the interface, features, or implementation details may change before eventual acceptance.
AMD has also not communicated in which version of Linux it could appear. As a result, users cannot install a stable kernel update today and expect those controls to officially work. The news is the presentation of a technical proposal that opens this possibility, with well-defined limits and still pending integration.
