Acpi Prp0001 0 ~upd~ -
Because this identifier is used across multiple platforms, the exact fix depends on the device you are using. Follow the relevant solution blueprint below. Method 1: The Steam Deck Resolution
PRP0001 devices require the kernel to look into the driver's of_match_table (Device Tree match table) rather than acpi_match_table . When the C‑based device_get_match_data() function was called, it already handled this correctly. However, the Rust abstraction for drivers did not include the equivalent logic. This affected any Rust‑written driver that relied on match data for a PRP0001 device.
Normally, ACPI and Devicetree (the system used by Linux on ARM/mobile devices) are two completely different ways for a computer to talk to its hardware. is a special "virtual" ID that tells the operating system:
What (laptop, server, or single-board computer) are you using? Share public link
Download the provided directly by Valve. acpi prp0001 0
A Rust kernel developer identified that device_get_match_data() returned None for PRP0001 devices in Rust kernel modules because the Rust code stored an index in the of_device_id structure instead of a data pointer.
: Often appears when users install Windows on a Steam Deck.
| | Recommendation | |-----------------------------------|----------------------------------------| | Normal server/laptop | Omit parameter (default=1) | | Embedded with custom ACPI | Likely need PRP0001 on | | ACPI table debugging | Try acpi prp0001 0 to isolate | | Security-hardened runtime | Consider =0 + ACPI table signature validation | | You see "PRP0001" in dmesg errors | Test =0 to confirm AML issue |
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. Because this identifier is used across multiple platforms,
As kernel development continues, PRP0001 remains a relevant and useful feature for hardware enablement. Recent patches (2025–2026) continue to refine how PRP0001 devices are handled, including improvements to match data retrieval and handling of devices with both _HID and PRP0001 in _CID . While it is often described as a temporary solution, PRP0001 continues to serve as an essential bridge for developers bringing devices to ACPI platforms.
Dominant in the ARM, RISC-V, and embedded Linux worlds.
In technical terms, PRP0001 is a special used to signal that a device should be enumerated using its Device Tree "compatible" property . It acts as a fallback for manufacturers who want to use standard Linux drivers for hardware integrated into an ACPI-based BIOS environment. Common hardware associated with this ID includes: How should I2C drivers be matched in ACPI with HID PRP0001
Ensure is checked to allow Windows to find the matching .inf file. Developer Context (Linux) Normally, ACPI and Devicetree (the system used by
AI responses may include mistakes. For financial advice, consult a professional. Learn more
: Used on Intel Edison or other IoT platforms to let Linux drivers work without rewriting code for ACPI. How to handle it If you are seeing this as an "Unknown Device" in Windows: ACPI Based Device Enumeration
The special DT namespace link device ID, PRP0001, provides a means to use the existing DT-compatible device identification in ACPI and to satisfy the above requirements following from the ACPI specification at the same time.
