I have narrowed this down to the new PiSP driver upstreamed in libcamera. They are matching the wrong entity names for CFE devices. https://gitlab.freedesktop.org/camera/libcamera/-/blame/v0.5.0/src/libcamera/pipeline/rpi/pisp/pisp.cpp#L883 Curiously, Raspberry Pi's fork of libcamera still uses the old match strings, even when they upstreamed these changes to Debian: https://github.com/raspberrypi/libcamera/blob/d83ff0a4ae4503bc56b7ed48cd142c3dd423ad3b/src/libcamera/pipeline/rpi/pisp/pisp.cpp#L883
This might suggest that there may be changes to the camera related devicetree overlays in the future. For now the fix will be to try for both older and newer match strings
I have narrowed this down to the new PiSP driver upstreamed in libcamera. They are matching the wrong entity names for CFE devices. /gitlab. freedesktop. org/camera/ libcamera/ -/blame/ v0.5.0/ src/libcamera/ pipeline/ rpi/pisp/ pisp.cpp# L883 /github. com/raspberrypi /libcamera/ blob/d83ff0a4ae 4503bc56b7ed48c d142c3dd423ad3b /src/libcamera/ pipeline/ rpi/pisp/ pisp.cpp# L883
https:/
Curiously, Raspberry Pi's fork of libcamera still uses the old match strings, even when they upstreamed these changes to Debian: https:/
This might suggest that there may be changes to the camera related devicetree overlays in the future. For now the fix will be to try for both older and newer match strings