ACPI PRP0001 0 (commonly surfaced in kernel logs as messages referencing “prp0001” or similar identifiers) denotes a platform resource-provisioning ACPI object associated with device provisioning and power/resource management on modern x86 and ARM platforms. This editorial explains what PRP0001 is, its origin and purpose within ACPI, why it appears in logs, practical implications for system integrators and users, diagnostic approaches, remediation strategies, and forward-looking considerations for firmware and OS maintainers.
On typical x86 laptops, PRP0001 devices are extremely rare. Disabling it changes nothing except perhaps for a niche embedded controller. The parameter primarily affects ARM64 servers and x86 IoT platforms (Bay Trail, Apollo Lake) where ACPI and DT drivers coexist.
You might see this in:
Device Tree overlay applied via ACPI:
An ACPI table from an untrusted source could contain a malicious _DSD that tricks a device-tree driver into misconfiguring DMA or IRQ mappings. Disabling PRP0001 reduces the attack surface. (Note: ACPI itself is already a massive attack surface, but this is a "belt and suspenders" measure.) acpi prp0001 0
The string is composed of three parts:
0: This is the instance number or index. It indicates this is the first (and often only) instance of this specific device object found at that specific path in the ACPI namespace.Seeing prp0001 usually means the operating system (typically Linux) has found a device described generically in the ACPI tables. ACPI PRP0001 0 (commonly surfaced in kernel logs
PRP0001 allows firmware writers to expose a Device Tree-style compatible string (e.g., "bosch,bme280") inside an ACPI table, and the Linux kernel will then attempt to match it to a Device Tree driver instead of an ACPI driver.