Acpi Prp0001 0

Device (LEDS) Name (_HID, "PRP0001") Name (_DSD, Package () ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"), // UUID for device properties Package () Package () "compatible", "gpio-leds" // DT compatible string

Or a related error:

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. How should I2C drivers be matched in ACPI with HID PRP0001 acpi prp0001 0

)

The PRP0001 ID relies entirely on the ACPI _DSD (Device Specific Data) object. The _DSD provides a way to represent Device Tree properties within ACPI. Device (LEDS) Name (_HID, "PRP0001") Name (_DSD, Package

If the directory doesn’t exist, the ACPI table might be malformed or the device not present.

Here’s what it actually means.

A typical PRP0001 device node in ASL (ACPI Source Language) looks like this:

: A patch by Andy Shevchenko corrected device_get_match_data() to work correctly with PRP0001 devices. Previously, calling this function returned nothing because the ACPI core did not respect PRP0001 during match data retrieval. Can’t copy the link right now

ACPI is the standard for device discovery, power management, and configuration in x86 systems (and increasingly ARM servers). When a PC boots, the BIOS/UEFI provides the OS with ACPI tables (DSDT, SSDT, etc.). These tables contain AML (ACPI Machine Language) bytecode that describes every device on the motherboard: PCIe slots, UARTs, I2C controllers, GPIOs, and more.