[ 0.987789] acpi PRP0001:00: platform device creation failed. -16
Error code -16 = -EBUSY (Device or resource busy). This often means:
If you are troubleshooting or writing a driver, you can find the real identity of acpi:prp0001:0 by checking the system logs or sysfs.
Method A: Using dmesg
Run dmesg | grep -i prp0001. You will often see output similar to this:
acpi PRP0001:00: bus: acpi type: hid:PRP0001
acpi PRP0001:00: driver: gpio_keys
This example would indicate that the device is a set of GPIO keys (power buttons, lid switch, etc.). acpi prp0001 0
Method B: Using sysfs (Recommended)
You can inspect the device properties directly to see what the firmware intended it to be.
PRP0001 is a special, Microsoft-defined ACPI Hardware ID. Its official meaning is:
"Device is compatible with a Device Tree binding." [ 0
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."
You might see this in:
Device Tree overlay applied via ACPI:
Parsing the _DSD for PRP0001 devices adds cycles. On a real-time embedded system with tens of pseudo-devices, disabling PRP0001 can shave tens of milliseconds from the boot sequence – critical for safety-critical initialization.
PRP0001 is a special ACPI hardware ID (HID).
It stands for "Device Tree / PRP0001" and is defined by the Linux kernel to allow ACPI tables to include devices that are described using a Device Tree fragment.
In other words: