0: Acpi Prp0001

Download the driver package provided by the .

Standardized for x86 architectures (Intel/AMD). Hardware info is stored in bytecode tables inside the system BIOS.

Last updated: 2025 – This article is evergreen, but kernel versions >6.0 have stable PRP0001 behavior. Always refer to your kernel’s dmesg for exact behavior.

So what does acpi prp0001 0 do?

Are you seeing this in a or Windows Device Manager ?

The kernel:

A tricky bug surfaced regarding module autoloading. When an ACPI device uses PRP0001 , the udev system might generate an OF-style modalias (e.g., of:NdeviceT<compatible> ) instead of an ACPI one ( acpi:PRP0001 ). This caused the system to attempt to load the OF driver variant (e.g., i2c-hid-of ), which would fail, instead of the correct ACPI driver ( i2c-hid-acpi ). A 2024 patch fixed this by adding a MODULE_ALIAS to ensure the proper driver was loaded for PRP0001 I2C HID devices. acpi prp0001 0

sudo acpidump > acpi.dat acpixtract -a acpi.dat iasl -d *dat grep -A 20 PRP0001 *.dsl

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

"The first instance of a generic ACPI-enumerated device (Hardware ID PRP0001 ). This device identifies itself via ACPI Device Properties ( _DSD ) rather than a fixed Hardware ID." Download the driver package provided by the

)

When hardware vendors began crossing these ecosystems—such as embedding ARM-style components (like I2C or SPI audio chips and touch controllers) into x86 platforms—they ran into a problem: writing entirely new ACPI-compliant Windows or Linux drivers for pre-existing Open Firmware (OF) hardware components is incredibly expensive and redundant.