Acpi Prp0001 0 -

(Device-Specific Data) in the ACPI tables to find the actual hardware identity. Why you see it as an "Unknown Device" If you are seeing ACPI\VEN_PRP&DEV_0001 in Windows Device Manager (common on Steam Decks Chromebooks

echo 1 > /sys/bus/acpi/devices/PRP0001:00/unbind 2>/dev/null echo 1 > /sys/bus/acpi/devices/PRP0001:00/bind

Name (_HID, "PRP0001") Name (_DSD, Package() ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"), Package () Package (2) "compatible", "ti,tmp75" ,

At its core, "ACPI PRP0001" is a special identifier in the that enables platform vendors to use Device Tree (DT) compatible strings for device identification instead of traditional ACPI hardware IDs. acpi prp0001 0

It loads the standard Linux Device Tree driver for that specific sensor. 🚀 Why This Matters

Example from an ACPI table (SSDT):

Or a related error:

bridges these two. If an ACPI device has PRP0001 as a _HID or _CID , the kernel checks the _DSD object for a compatible property. 2. Why PRP0001 Exists: The Problem it Solves

If you are authoring ASL for a device, ensure that any interrupt listed in _PRW is supported by the platform's interrupt controller for wake events. For GPIO interrupts, verify that the GPIO controller is correctly configured for wake in the ACPI tables.

The _DSD must use the correct UUID for device properties: daffd814-6eba-4d8c-8a91-bc9bbf4aa301 . (Device-Specific Data) in the ACPI tables to find

The string acpi prp0001 0 unlocks a fascinating corner of the Linux kernel’s driver model. It tells a story of hardware abstraction bridging two worlds: the rigid, BIOS-centric ACPI and the flexible, open-source-friendly Device Tree.

If you are dealing with ACPI\PRP0001 entries slowing down or cluttering your Device Manager, use these step-by-step methods to clear them. Method 1: The Steam Deck Solution

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. 🚀 Why This Matters Example from an ACPI

When Linux encounters _HID = "PRP0001" , the ACPI subsystem bypasses standard ACPI matching and looks at the _DSD (Device-Specific Data) package. Within _DSD , a special UUID identifies the "Device Properties" section. Inside that section, a compatible property provides one or more strings — exactly like a Device Tree compatible statement: