[ 0.987789] acpi PRP0001:00: platform device creation failed. -16 To the uninitiated, acpi prp0001 0 looks like a random string of hex and numbers. But to embedded Linux developers, firmware engineers, and kernel tinkerers, it represents a powerful (and sometimes frustrating) bridge between legacy PC-style firmware (ACPI) and modern embedded device description (Device Tree).
DefinitionBlock ("ssdt.aml", "SSDT", 2, "HACK", "PRP0001", 0x00000001)
Notice the trick: The ACPI ID is PRP0001 , but the driver uses a pointer to the OF match table. The kernel then tries each compatible string in the _DSD against that table. Problem: Device not created (error -16 or -19) Step 1: Confirm the device is actually enumerated
Compile ( iasl ssdt.asl ) and load via cat ssdt.aml > /sys/kernel/config/acpi/table/ssdt1 .
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);
The Linux kernel parses these tables and creates platform devices, PCI devices, or ACPI-defined devices accordingly. Each device in ACPI has a unique – a string like PNP0501 (legacy serial port) or INT33BD (Intel I2C controller).
