PRP0001 was the ghost in the machine—a generic "Platform Device" placeholder, a catch-all for hardware too dumb or too proprietary to name itself. But the 0 ? That was the problem. Device addresses were hex, not decimal zero. It was like finding a house numbered "Nonexistent Street."
), the kernel uses its existing Device Tree matching table to find the correct driver, even if the system is running in ACPI mode. Enumeration acpi prp0001 0
The implications of PRP0001 are profound for the development of cross-architecture drivers. Before its adoption, a driver writer might have had to support two separate paths for device matching: one for ACPI IDs and one for Device Tree compatible strings. With PRP0001, the code becomes unified. A single driver can declare its compatibility via the standard Device Tree binding, and the ACPI core, recognizing PRP0001, will automatically attempt to bind the driver using the provided compatible string. This reduces code duplication in the kernel, lowers the maintenance burden, and significantly speeds up the boot process and driver support for new hardware, particularly in the burgeoning market of ARM-based laptops and servers running Windows or Linux. PRP0001 was the ghost in the machine—a generic
If you suspect you have a PRP0001 device, use these commands: Device addresses were hex, not decimal zero