Linux users running AMD processors could soon have a much easier time tuning their hardware directly from the operating system. While Windows users have long relied on the official Ryzen Master utility to tweak performance parameters, Linux enthusiasts have had to jump into the BIOS or rely on third-party workarounds. Now, AMD is laying the groundwork for native, official Ryzen overclocking support on Linux at the kernel level. For any one that knows their way around a BIOS it’s no big deal, but having something official certainly makes life easier.

AMD engineer Shyam Sundar S K recently submitted a three-patch series to the platform-driver-x86 mailing list. These patches introduce the AMD Overclocking Driver, or AOD for short. Functioning as a WMI driver, AOD communicates with the exact same underlying firmware interface that powers the Ryzen Master software on Windows, exposing those tuning controls directly through the Linux sysfs interface. However, the release of this driver does not mean that a full Ryzen Master desktop application is being ported over to Linux. Instead, AMD is taking a similar path to how it handles its amdgpu graphics driver. By building the core functionality and controls directly into the Linux kernel, AMD leaves the door open for established third-party graphical utilities, such as CoreCtrl or LACT, as well as various desktop environments, to build their own user-friendly frontends on top of the official interface. I already use LACT, but if this improves its usability and cuts down on workarounds, I’m all for it.

In its initial form, the AOD patch series only hooks up a foundational set of tuning controls, though the underlying firmware supports a much wider array of commands that could be enabled in future updates. There are also a few technical quirks in how the driver currently operates compared to existing Linux tuning methods like AMD’s Host System Management Port (HSMP) interface. Whereas HSMP applies changes immediately in the current session but forgets them when you reboot, the new AOD driver saves modifications directly to the firmware, meaning a system restart is required before new power limits take effect.