/* 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, ;
[ 0.000000] ACPI: PRP0001:0: device active. Ghost made flesh.
The PRP0001 ID solves this by allowing the ACPI table to say: "I don't have a unique ACPI ID for this device, so please just look at the 'compatible' string provided in the properties." Key Benefits
: Mika Westerberg's commit 733e625 introduced the special PRP0001 ID so that driver matching could be done using Device Tree compatible properties.
I2cSerialBusV2 (0x48, ControllerInitiated, 400000, AddressingMode7Bit, "\\_SB.PCI0.I2C1", 0x00, ResourceConsumer, , Exclusive,) ) Return (SBUF) acpi prp0001 0
dmesg | grep -i prp0001 ls /sys/bus/acpi/devices/PRP0001:00/ cat /sys/bus/acpi/devices/PRP0001:00/path
In Linux, PRP0001 allows hardware to be described using standard ACPI tables while still utilizing the of_match_table (Open Firmware) typically used in Device Tree environments. This means a single Linux driver can support both ARM-based (Device Tree) and x86-based (ACPI) systems without needing a unique ACPI ID for every small component. Troubleshooting "Unknown Device" (Windows)
In ACPI, every device in the namespace ( \_SB_ , \_SB_.PCI0 , etc.) has a – a string like PNP0C09 (embedded controller) or ACPI000C (PPTT table). The HID allows the OS to load the correct driver.
She didn't scream. Engineers don't scream; they document. She grabbed her phone to take a picture. The camera app opened, but the viewfinder showed only static—snow, like an old analog TV. /* I2C driver structure */ static struct i2c_driver
If disabled, you will see prints like:
If you see messages regarding PRP0001 in dmesg (e.g., during driver probing or failed ACPI initialization), consider the following, as discussed in StackOverflow :
Hardware architecture relies heavily on hardware description protocols so the operating system can map which chip sits where, what resources it needs, and which driver should claim it. Historically, this fell into two opposing ecosystems:
Suppose a device has both a PRP0001 entry (to load a DT driver) and a legacy PNPXXXX HID (for an older ACPI driver). The kernel may prefer the DT driver via PRP0001. Disabling PRP0001 forces the kernel to fall back to the native ACPI driver – useful for performance comparison or bug workarounds. The HID allows the OS to load the correct driver
For (like Pixelbooks), look for the Google Audio SPI Device driver .
: Users often encounter this ID when installing Windows on devices like the Steam Deck or Chromebooks. On these systems, it often refers to: Google Audio SPI Devices .
When commit c64ffff ("i2c: core: Allow empty id_table in ACPI case as well") fixed the enumeration of I²C devices on ACPI enabled platforms when driver has no ID table, it missed the PRP0001 support.