This HID tells the kernel: "Ignore my ACPI ID for matching; instead, look for a compatible property in my _DSD (Device Specific Data) and treat it like a Device Tree compatible string." This mechanism allows a device to be matched and driven using a driver's of_match_table (Open Firmware match table) instead of its acpi_match_table .
A user on a Chromebook forum encountered three devices with hardware IDs ACPI\PRP0001\4&df81603&0 , ACPI\PRP0001\0 , and ACPI\PRP0001\1 . Windows Device Manager showed no driver available for any of them.
Go to > Windows Update > Advanced options > Optional updates . Manufacturers sometimes push niche ACPI drivers here. Are you seeing this on a specific device like a Steam Deck
// Example ASL (ACPI Source Language) Device (SNS0) Name (_HID, "PRP0001") // The Magic Bridge ID Name (_DSD, Package () ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"), Package () Package () "compatible", "manufacturer,specific-sensor" , Package () "interrupt-parent", \_SB.PCI0.GPIO , ) Use code with caution. When Linux reads this: It sees _HID "PRP0001" . acpi prp0001 0
: Mika Westerberg's commit 733e625 introduced the special PRP0001 ID so that driver matching could be done using Device Tree compatible properties.
For example, an ACPI entry might look like this in pseudo-code:
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." This HID tells the kernel: "Ignore my ACPI
The kernel found a PRP0001 device, extracted a compatible property from its _DSD , matched it to an I2C driver ( bme280 ), and created the device.
While powerful, PRP0001 is not a universal solution. It is most commonly used for sensors connected via I2C and SPI, and is considered a workaround for cases where native ACPI bindings are not yet available.
In deep technical terms, it is a bridge allowing OS drivers—particularly in Linux—to use modern, structured device descriptions ( Go to > Windows Update > Advanced options > Optional updates
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
Here, 0 is the driver data (often unused).
= -EBUSY (Device or resource busy). This often means: