Matt Delco has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/44397 )
Change subject: mb/google/dedede: Replace static Camera ACPI by driver for WDoo ......................................................................
Patch Set 10:
(1 comment)
https://review.coreboot.org/c/coreboot/+/44397/9/src/mainboard/google/dedede... File src/mainboard/google/dedede/variants/waddledoo/overridetree.cb:
https://review.coreboot.org/c/coreboot/+/44397/9/src/mainboard/google/dedede... PS9, Line 196: ACPI_DT_NAMESPACE_HID
I think the ACPI subsystem will look for the "compatible" property in _DSD and link the driver accor […]
AFAIK the PRP0001 scheme is entirely a coreboot invention that's using a vendor ID that doesn't belong to coreboot, and further the scheme of using the "compatible" property is non-standard in ACPI and something that wouldn't work with Windows (since it bases which driver to use solely on the hardware ID). The INT3499 lets Windows use a Intel-specific driver, though since Windows tends to use the monolothic camera representation (vs. individual devices for things like the camera, NVM, and VCM) this might be a moot point (since on Windows a "null" driver would be used for the NVM and VCM devices--these devices would instead be controlled by the camera driver that uses information reported in the camera device to locate the I2C addresses for the NCM and VCM devices).