AMD DPTCi Driver Posted For Linux To Better Enhance Ryzen Gaming Handhelds
AMD DPTCi Driver Posted For Linux To Better Enhance Ryzen Gaming Handhelds
https://www.phoronix.com/news/AMD-DPTCi-Linux-Driver
Publish Date: 2026-03-03 16:07:00
Source Domain: www.phoronix.com
A request for comments (RFC) patch series was posted today to the Linux kernel mailing list to introduce the AMD Dynamic Power and Thermal Configuration Interface “DPTCi” driver. With this driver it would provide better upstream Linux kernel support for tuning the power / performance / thermals of modern Ryzen-powered gaming handheld devices. Though don’t get too excited right away as the driver was assembled in part by AI that is already causing a bit of a ruckus on the LKML due to lack of disclosure.
Antheas Kapenekakis is the developer who has been heavily involved on improving various Linux drivers for different gaming handhelds. He’s tackled improving the Linux support for OneXPlayer devices, ASUS hardware, AYANEO, MSI Claw, and more. Now he’s been working on writing this AMD DPTCi driver to help further improve the upstream Linux kernel support for the modern AMD Ryzen powered handhelds.
Kapenekakis explained in the patch series cover letter:
“Many AMD-based handheld PCs (GPD, AYANEO, OneXPlayer, AOKZOE, OrangePi) ship with the AGESA ALIB method at _SB.ALIB, which accepts Function 0x0C (the Dynamic Power and Thermal Configuration Interface, DPTCi). This allows software to adjust APU power and thermal parameters at runtime: STAPM limit, fast/slow PPT limits, skin-temperature TDP limit, slow/STAPM time constants, and the thermal control target.
Until now userspace has reached this interface through the acpi_call out-of-tree module or ryzenadj, which carry no ABI guarantees and no per-device safety limits. This driver replaces that with a proper in-kernel implementation that:
* Exposes all seven parameters through the firmware-attributes sysfs ABI, so that standard tools (fwupd, systemd-bios-vendor, etc.) can enumerate and modify them without device-specific knowledge.
* Enforces tiered per-device and per-SoC limits. The default “device” mode restricts writes to a curated safe range (smin..smax) derived from the device’s thermal design. An “expanded” mode…
