We Are Trusted By
ls /sys/bus/acpi/devices/ | grep PRP0001
: The use of PRP0001 extends to SPI and GPIO as well. For example, the SPI core was modified to initialize a device's modalias from the of_compatible property when PRP0001 is used. Similarly, a PPS (Pulse-Per-Second) GPIO device can be described using PRP0001 , allowing the pps-gpio driver to claim it.
Download the provided directly by Valve. acpi prp0001 0
is the ultimate shortcut. Instead of petitioning an industry body for a unique hardware ID (which is slow and expensive), a developer can simply use
It enables standard i2c-designware or spi-pxa2xx drivers to enumerate child devices that do not have dedicated ACPI HID drivers. ls /sys/bus/acpi/devices/ | grep PRP0001 : The use
When you see ACPI\PRP0001\0 or similar in your Device Manager (Windows) or kernel logs (Linux), it indicates a device that does not have its own unique, vendor-assigned ACPI hardware ID. Instead, it uses a standardized mechanism to tell the OS exactly which driver it needs through a compatible property. Common Occurrences
Here is a partial copy and paste of the driver setup information file which shows driver support for the hardware ID you posted: % HP Support Community Download the provided directly by Valve
Check for a (this is the most important part for PRP0001 ): Since PRP0001 is generic, it usually has a "compatible" string property defined in the firmware (similar to Device Tree). You can often find this in the of_node symlink or by inspecting the description if available.
[ 0.123456] ACPI: PRP0001:00: PRP0001 device [ 0.123457] acpi PRP0001:00: [Firmware Info]: Device [BME280] compatible with bosch,bme280 [ 0.123789] i2c i2c-0: added device BME280
say around the PRP0001 reference? Share public link
We Are Trusted By