Acpi Prp0001 0

cat modalias

Even if the ID is present, the kernel needs to have the corresponding driver compiled in or available as a module.

is the ultimate shortcut. Instead of petitioning an industry body for a unique hardware ID (which is slow and expensive), a developer can simply use acpi prp0001 0

acpi PRP0001:00: bus: acpi type: hid:PRP0001 acpi PRP0001:00: driver: gpio_keys

The PRP0001 mechanism often depends on CONFIG_OF (Open Firmware) support in the kernel. Even on ACPI systems, CONFIG_OF should be enabled to match DT compatible strings. cat modalias Even if the ID is present,

/* I2C driver structure */ static struct i2c_driver tmp75_driver = .driver = .name = "tmp75", .of_match_table = tmp75_of_match, , .probe_new = tmp75_probe, .id_table = tmp75_id, ;

Device (I2CD) Name (_HID, "PRP0001") Name (_DSD, Package () ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"), Package () Package (2) "compatible", "my-vendor,my-device" , // Additional properties follow the same pattern Even on ACPI systems, CONFIG_OF should be enabled

Here’s what it actually means.

When you see ACPI\PRP0001\0 or similar in your Device Manager (Windows) or kernel logs (Linux), it indicates a device that does not have its own unique, vendor-assigned ACPI hardware ID. Instead, it uses a standardized mechanism to tell the OS exactly which driver it needs through a compatible property. Common Occurrences

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.