Thank you for the clarification. That makes sense.Unicam is the driver or the CSI2 receiver on Pi0-4.
Pi5 has a totally different hardware block (on RP1 rather than the main BCM2712 SoC), and that is the CFE.
Two drivers for two different bits of hardware.
Thank you. I will have look into it.Still being worked on.
https://github.com/raspberrypi/libcamera/pull/200 is the libcamera update to use it, and goes alongside the kernel changes in https://github.com/raspberrypi/linux/pull/6437. I'm trying to get the same thing working on 6.12 at the moment, but it's now likely to be after the Christmas break.
I am aware that not all sensors are supporting the selection of virtual channels. However, at the moment we are luckily still able to select sensors which support that feature.Virtual channels probably don't help you. Some sensors don't allow you to set the virtual channel and will always use VC 0.
Glitches in the clock lane won't matter if your sensor does NOT use continuous clock mode, as there will be plenty of LP<>HS transitions.
You may have a hope, but I'm afraid it's not something I have any time to delve into, and none of the libcamera pipeline setup is currently in a position to support it.
Regarding the clock glitches, every sensor should support disabling continuous clock, IIRC. Fortunately, the glitches then should be no problem. Thank you for the clarification.
I am totally aware that my issue is kind of special and I am absolutely not excepting you to delve into it. I think I am able to implement and test the approach myself (without the use of libcamera, just by directly accessing the /dev/videoN-Devices). I was just hoping to get a confirmation from you, that concept could work reliably or if you see any concerns.
Thank you and happy Christmas!
Statistics: Posted by marcp — Fri Dec 20, 2024 3:23 pm