Thus, acpi prp0001 0 is not going away; it remains a vital “back door” for flexible device description. 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.
ls /sys/bus/acpi/devices/PRP0001:00/ -l If the directory doesn’t exist, the ACPI table might be malformed or the device not present. acpi prp0001 0
static const struct of_device_id bmp280_of_match[] = .compatible = "bosch,bme280" , ; MODULE_DEVICE_TABLE(of, bmp280_of_match); static const struct acpi_device_id bmp280_acpi_match[] = "PRP0001", .driver_data = (kernel_ulong_t)&bmp280_of_match[0] , ; MODULE_DEVICE_TABLE(acpi, bmp280_acpi_match); Thus, acpi prp0001 0 is not going away;
When you see log lines like:
External (_SB_.I2C0, DeviceObj) Scope (_SB.I2C0) Device (SENS) Name (_HID, "PRP0001") Name (_DSD, Package () ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"), Package () Package () "compatible", "bosch,bme280" , Package () "reg", 0x77 , ) .driver_data = (kernel_ulong_t)&bmp280_of_match[0]