Acpi Prp0001 0 Jun 2026

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.

"Device is compatible with a Device Tree node having a given 'compatible' property." acpi prp0001 0

For (like Pixelbooks), look for the Google Audio SPI Device driver . Verify the compatible string in _DSD matches the

: PRP0001 acts as a "fallback" or "generic" Hardware ID (HID). When the OS encounters this ID, it knows not to look for a standard ACPI driver match immediately. Instead, it looks for a (Device Specific Data) property named compatible within the ACPI table. Driver Matching compatible string is found (e.g., "google,eve-audio" : PRP0001 acts as a "fallback" or "generic"

If disabled, you will see prints like:

Author’s note: If your bootloader supports command-line editing, acpi prp0001 0 is safe to test transiently – it will not corrupt firmware or storage. However, always verify fixed boot with =1 (or omitted) before production deployment.