Name (SBUF, ResourceTemplate ()
: In the Linux ecosystem, hardware is mapped using Device Trees via a property called compatible . The ACPI standard introduced PRP0001 as a universal hardware ID. It tells the OS kernel: "Read the Device Specification Data ( _DSD ) block to figure out what driver this device actually needs."
(e.g., sensor, GPIO) is failing to load? What CPU architecture are you using (e.g., x86, ARM64)? acpi prp0001 0
[PATCH v1 0/4] virt: vmgenid: Add devicetree bindings support
In the Linux kernel, PRP0001 allows ACPI-based systems to reuse existing drivers. By using this ID, developers can make hardware (like I2C or SPI devices) work on ACPI systems without writing entirely new drivers from scratch, provided the _DSD properties are correctly defined in the BIOS. Name (SBUF, ResourceTemplate () : In the Linux
static const struct acpi_device_id my_driver_acpi_ids[] = "PRP0001", 0 ,
The hardware identifier (often appearing in Windows Device Manager as ACPI\VEN_PRP&DEV_0001 ) represents a special Device Tree (DT) compatibility layer . It allows operating systems like Windows to recognize and interact with hardware components originally designed for Linux-based open-firmware architectures. What CPU architecture are you using (e
Here is a partial copy and paste of the driver setup information file which shows driver support for the hardware ID you posted: % HP Support Community
running Windows), it means Windows doesn't know how to handle this Linux-centric bridge. Steam Deck : It usually refers to specialized hardware like the Steam Deck's buttons/controllers
acpi.prp0001=0
To understand PRP0001, one must first understand the evolution of hardware discovery. Traditionally, hardware devices connected via buses like PCI or USB provided unique hardware IDs (such as a Vendor ID and Device ID). The operating system would read these IDs and match them against a database of drivers. However, with the rise of ARM-based systems and the proliferation of embedded controllers and sensors, many devices do not sit on a discoverable bus like PCI. Instead, they are described statically in the ACPI tables—specifically the Differentiated System Description Table (DSDT). Historically, this created a fragmentation problem: hardware vendors would have to create specific ACPI IDs for generic devices, leading to a proliferation of "dummy" IDs for standard components like temperature sensors or generic buttons.