Acpi Prp0001 0 Instant

In the past, hardware developers had a problem. If they made a simple component (like an I2C temperature sensor), they had to write two different sets of descriptions: one for ACPI and one for Device Tree.

Device (ACC0) Name (_HID, "PRP0001") Name (_DSD, Package() ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"), Package() Package() "compatible", "bosch,bma400", Package() "reg", 0x10, acpi prp0001 0

cat /sys/bus/acpi/devices/PRP0001:00/path cat /sys/bus/acpi/devices/PRP0001:00/status In the past, hardware developers had a problem

If a device has PRP0001 in its ACPI ID list, the kernel ( ACPI / scan ) handler treats it as a special case, allowing it to bind to drivers using of_match_table (Open Firmware/Device Tree match table). How it Works: The Role of _DSD In the past

So what does acpi prp0001 0 do?