❌
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
PRP0001 is not a physical hardware device, but a special "Compatible Device ID" defined in the ACPI specification. When this HID appears in the ACPI namespace of a device, it tells the Linux kernel to act differently. acpi prp0001 0
When users encounter this identifier—most commonly flagged as an —it typically points to specialized hardware on modified mobile devices. These include Google Chromebooks forced to run Windows, Valve Steam Decks utilizing alternative operating systems, and various custom x86 embedded platforms. The Technical Foundation of PRP0001
Verify the compatible string in _DSD matches the driver’s of_match_table exactly. A trailing space or wrong vendor prefix (e.g., bosch,bme280 vs bmp,bme280 ) will cause a mismatch. ❌ This public link is valid for 7
| | Recommendation | |-----------------------------------|----------------------------------------| | Normal server/laptop | Omit parameter (default=1) | | Embedded with custom ACPI | Likely need PRP0001 on | | ACPI table debugging | Try acpi prp0001 0 to isolate | | Security-hardened runtime | Consider =0 + ACPI table signature validation | | You see "PRP0001" in dmesg errors | Test =0 to confirm AML issue |
acpi PRP0001:00: bus: acpi type: hid:PRP0001 acpi PRP0001:00: driver: gpio_keys Can’t copy the link right now
static int __init acpi_prp0001_setup(char *str)
If you’re running a standard desktop PC (Dell XPS, Lenovo ThinkPad, custom AMD Ryzen), you likely see this message because the firmware uses well-known _HID values for all devices.
) Name (_CRS, ResourceTemplate() I2cSerialBusV2(0x10, , , , , , , , "\\_SB.I2C0") )
