By ensuring your ACPI tables have a valid compatible property and your drivers have a proper of_match_table , you can leverage the full power of PRP0001 to bring up devices on your x86 or ACPI-based ARM platform without waiting for official ACPI IDs.
Understanding ACPI\PRP0001\0: The Ultimate Guide to This Elusive Hardware ID
In essence, when an ACPI device node has _HID set to PRP0001 , it tells the OS: "Don't look for a standard ACPI driver; instead, treat this device as if it were described by a Device Tree (DT) node. Look for a compatible string in my _DSD (Device Specific Data) properties." acpi prp0001 0
to manage specialized components like custom audio chips, touchpads, or GPIO pins that don't have their own official industry-standard ID. Linux Flexibility
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 By ensuring your ACPI tables have a valid
static const struct of_device_id acme_sensor_match[] = .compatible = "acme,sensor-x" , ; Use code with caution. 5. Troubleshooting PRP0001 Issues
The terminal spat back: \_SB_.PCI0.GHST0 Linux Flexibility Because this identifier is used across
— 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.
She froze. GHST0. It wasn't in the board schematics. It wasn't in any datasheet from Intel, AMD, or any vendor she knew. It was as if the BIOS had grown a new branch on the device tree, like a tree putting out a leaf in winter.
)
: You can use the same driver code for both DT-based systems (like Raspberry Pi) and ACPI-based systems (like x86 laptops) without modification. Flexibility