Acpi Prp0001 0 🆕 📌

) // ...

static const struct of_device_id bmp280_of_match[] = .compatible = "bosch,bme280" ,

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

Early patches for ACPI support sometimes incorrectly added a static acpi_device_id entry like "PRP0001", 0 to drivers. Adding PRP0001 to an ACPI match table is unnecessary and counterproductive because PRP0001 devices are specifically designed to be matched via the of_match_table . Doing so can create ambiguous matching paths and break the intended behavior. acpi prp0001 0

The ACPI ID PRP0001 is a special identifier used by the Linux kernel to bridge the gap between traditional ACPI (Advanced Configuration and Power Interface) and Device Tree (DT) systems. While often seen in system logs or as an "Unknown Device" in Windows (particularly on devices like the ), its primary purpose is technical integration for hardware developers. What is ACPI PRP0001?

It is used when a device is connected via a low-level serial bus (like I2C or SPI) rather than a native bus like PCI.

If you want, I can:

You’ll see a snippet like:

A more philosophical debate surrounds the use of PRP0001 . Some kernel maintainers view it as a "workaround" that should only be a last resort. The preferred approach for standard hardware is to use proper ACPI IDs to maintain a clean, idiomatic ACPI description that is compatible with other operating systems. As one kernel developer noted, using PRP0001 is "not idiomatic ACPI" and other OSs actively reject the idea of binding to devices described this way. However, proponents argue that it's a pragmatic solution that enables significant code reuse without breaking anything.

| | Matching Behavior | Primary Use Case | |---|---|---| | _HID only | Driver matched via of_match_table using "compatible" property from _DSD | Final production devices without an official ACPI ID | | _CID only | Driver matched via of_match_table while a vendor-specific _HID is present | Bridge period while waiting for an official ID to be allocated | | Both _HID and _CID | IDs preceding PRP0001 in _CID are checked first; final match via of_match_table | Pre-production stages before an official ID exists | Adding PRP0001 to an ACPI match table is

Device (TMP0)

: Seen when running Windows on Chromebook hardware (like Acer or HP models).

Are you seeing this in a or Windows Device Manager ? While often seen in system logs or as