[ 0.987789] acpi PRP0001:00: platform device creation failed. -16
[ 3.102345] ACPI: PRP0001 device [GPIO0] probing... [ 3.115678] Unable to handle kernel NULL pointer dereference at IRQ mapping
: Create a new, official ACPI ID for the device, write ACPI Source Language (ASL) code to describe it, and add that ID to the driver's ACPI match table in the Linux kernel. This is the "proper" but often cumbersome route, as it requires coordination and allocation of new IDs.
To understand ACPI\PRP0001\0 , you must understand the two primary ways operating systems discover hardware: acpi prp0001 0
For an I2C device, ensure the I2C controller driver is bound:
: The kernel's device enumeration code looks for the compatible property inside the device's _DSD package. This property lists one or more device names, such as "ti,ads7830" . If this property is missing or invalid, the kernel will simply refuse to enumerate the device.
Example output: PRP0001:00
Note: In cases where a device has both a traditional ACPI ID and PRP0001 , the system can prioritize the specific ACPI handler if necessary, but PRP0001 acts as a fallback for generic DT drivers. 4. PRP0001 and Device Tree Property Matching
The kernel sees PRP0001 , then jumps to the _DSD (Device Specific Data) section, finds "honeywell,hmc5843" , and loads the correct driver. Common "PRP0001" Issues and Fixes
At its core, PRP0001 is a special ACPI Hardware ID (HID) that serves as a "Device Tree (DT) namespace link". It was introduced to solve a practical problem: reusing existing Linux kernel drivers that were originally written for the Device Tree on ACPI-based x86 systems without having to allocate an official ACPI/PNP ID. This is the "proper" but often cumbersome route,
If you are authoring ASL for a device, ensure that any interrupt listed in _PRW is supported by the platform's interrupt controller for wake events. For GPIO interrupts, verify that the GPIO controller is correctly configured for wake in the ACPI tables.
At first glance, disabling a feature that allows driver reuse seems destructive. But practical scenarios exist:
