AMD’s proposed AMD Overclocking (AOD) driver would expose selected Ryzen controls through Linux’s sysfs interface. The initial series covers power and current limits, platform-level SMT switching, and memory-clock reporting. The power-limit changes take effect after a reboot, according to reports published October 21, 2026, which described the patches as under review.
Hardware Busters reported that AMD engineer Shyam Sundar S K posted the three-patch series to the platform-driver-x86 mailing list on October 10, 2026. The proposed driver connects Linux controls to Ryzen platform firmware.
Which Ryzen controls does the initial series propose?
The initial patch description names three adjustable limits: PPT (Package Power Tracking), TDC (Thermal Design Current), and EDC (Electrical Design Current). Phoronix reported that users could set those limits through sysfs and read their supported ranges.
The series also proposes a platform-level switch for SMT (Simultaneous Multithreading), a processor feature that allows multiple threads to run on a core. It reports the current memory clock as well. The first control list does not include per-core frequency, voltage, or Curve Optimizer settings.
Why AOD and HSMP apply power limits differently
Hardware Busters described AMD’s AOD and HSMP interfaces as differing in when their power-limit changes take effect and whether they persist after a restart:
| Interface | Power-limit type | When the change takes effect | After restart |
| Proposed AOD driver | Firmware setup limit | At the next boot | The setting persists |
| AMD HSMP | Runtime limit | Immediately | The adjustment is lost |
That makes the proposed AOD controls a poor fit for changing a power limit during a benchmark: the change waits for a reboot. HSMP applies its runtime adjustment immediately, but it does not persist through a restart. HSMP is a separate interface, not a function of the AOD patch series.
The patches are a driver proposal, not a Ryzen Master-style app
The October 21 reports described no AMD graphical user interface (GUI) patch alongside the driver. Tom’s Hardware discussed CoreCtrl as a possible future interface, not as an existing AOD integration. The initial controls therefore describe a narrower proposal than per-core tuning through a desktop app: they cover the named power and current limits, SMT switching, and memory-clock reporting.
