Acpi Prp0001 0 __hot__ Instant
Below is a complete ASL example that adds a TMP75 temperature sensor on I²C bus 1, address 0x48, and matches it to the kernel's tmp75 driver through its Device Tree compatible string:
: Ensure your OS is up-to-date, as newer versions may have better support for ACPI devices.
acpi prp0001 0
It is most commonly seen on devices like the Steam Deck when running Windows or alternative Linux distros, where it often handles GPIO pins or small sensors. acpi prp0001 0
A typical PRP0001 device node in ASL (ACPI Source Language) looks like this:
Open (right-click the Start button and select it).
The PRP0001 mechanism is not just a theoretical concept; it is actively used in the kernel to support real-world hardware. Below is a complete ASL example that adds
If you are authoring ASL for a device, ensure that any interrupt listed in _PRW is supported by the platform's interrupt controller for wake events. For GPIO interrupts, verify that the GPIO controller is correctly configured for wake in the ACPI tables.
(default):
echo 1 > /sys/bus/acpi/devices/PRP0001:00/enable The PRP0001 mechanism is not just a theoretical
Example from an ACPI table (SSDT):
Historically, the computing world split into two architectures for recognizing hardware:
The "acpi PRP0001 0" identifier is a perfect example of the Linux kernel's pragmatic and innovative approach to hardware support. It showcases the community's willingness to build bridges between disparate firmware standards to serve the ultimate goal: making hardware work reliably across all platforms.
Some vendor firmwares ship broken _DSD bundles for PRP0001 devices – malformed UUIDs, missing compatible , or referencing non-existent interrupts. This can cause:
In an ideal world, these two worlds would never touch. However, the rise of ARM-based servers (e.g., AWS Graviton, Ampere Altra) and heterogeneous computing has forced Linux to support platforms that ship with ACPI tables but contain IP blocks (devices) that were originally designed for Device Tree.