Acpi Prp0001 0 Today

The technical mechanism behind PRP0001 relies heavily on the "compatible" property. In the Device Tree model used heavily in Linux, devices are matched to drivers based on a "compatible" string (e.g., "ti,tmp102" for a Texas Instruments temperature sensor). When a device in an ACPI table uses the ID PRP0001, it must also include a "_DSD" (Device Specific Data) method that contains a "compatible" property. This mechanism allows the kernel to treat an ACPI-enumerated device exactly as it would a Device Tree-enumerated device. For example, a real-time clock or an I2C sensor described in ACPI tables can use PRP0001 to bind to existing Linux drivers that were originally written for Device Tree hardware, without requiring a rewrite of the driver or the creation of a new ACPI-specific driver.

What does acpi prp0001 0 actually do, and why would an engineer ever need to use it? acpi prp0001 0