bridges these two. If an ACPI device has PRP0001 as a _HID or _CID , the kernel checks the _DSD object for a compatible property. 2. Why PRP0001 Exists: The Problem it Solves
Here is a breakdown of what this identifier means, why it appears, and how to interpret it.
Ensure the driver you are trying to use has a of_match_table definition. Common dmesg logs:
The PRP0001 ID solves this by allowing the ACPI table to say: "I don't have a unique ACPI ID for this device, so please just look at the 'compatible' string provided in the properties." Key Benefits acpi prp0001 0
: Windows does not recognize the device because it lacks the specific driver provided by the manufacturer (e.g., Valve for Steam Deck or Intel for specific chipsets).
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
) Method (_CRS, 0, Serialized) // Defines the I2C connection Name (SBUF, ResourceTemplate () I2cSerialBusV2 (0x4a, ControllerInitiated, 100000, AddressingMode7Bit, "\\_SB.PC00.I2C0", 0x00, ResourceConsumer, , Exclusive,) ) Return (SBUF) bridges these two
— Used when a device has acquired a formal ACPI ID from the vendor, but a fully DT‑compatible driver also exists. The _CID entry allows fallback to DT matching before the driver is updated to include the new ACPI ID.
is a fixed _HID (Hardware ID) value that informs the Linux kernel: "Do not try to match me using conventional ACPI IDs. Instead, read my compatible property from the _DSD (Device-Specific Data) and match me using the driver's Device Tree match table."
Check for a BIOS/Firmware update from your motherboard manufacturer. 2. Driver Not Loading Why PRP0001 Exists: The Problem it Solves Here
It takes the string value (e.g., "acme,sensor-x" ) and searches the of_match_table of available Linux drivers, acting as if the device was described in a Device Tree, not ACPI.
acpi_prp0001 is a powerful abstraction layer allowing modern Linux systems to merge the best of ACPI (dynamic enumeration) and Device Tree (standardized driver bindings). It is crucial for hardware portability, allowing drivers for peripherals to be written once and used on both ARM (DT) and x86 (ACPI) platforms. If you'd like, I can:
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.