[libcamera-devel] Need help with IPU6 vs SimplePipeLine handler
Laurent Pinchart
laurent.pinchart at ideasonboard.com
Sun Oct 1 11:32:55 CEST 2023
Hi Hans,
On Sun, Oct 01, 2023 at 11:14:33AM +0200, Hans de Goede via libcamera-devel wrote:
> Hi All,
>
> I have raw bayer capture working from the cmdline, but after this naive patch:
>
> --- a/src/libcamera/pipeline/simple/simple.cpp
> +++ b/src/libcamera/pipeline/simple/simple.cpp
> @@ -196,6 +196,7 @@ static const SimplePipelineInfo supportedDevices[] = {
> { "mxc-isi", {} },
> { "qcom-camss", {} },
> { "sun6i-csi", {} },
> + { "intel-ipu6", {} },
> };
>
> } /* namespace */
>
>
> qcam still does not see the camera. I believe that this is likely caused
> by the CSI2-receiver on the IPU6 not being so simple. It appears to have
> some sort of cross-switch giving it a whole bunch of different inputs
> and outputs and we need to set that up to connect the CSI data from the sensor
> to one of the inputs and likewise make it dump the raw bayer data into
> /dev/video#.
Could you provide the output of media-ctl --print-dot ? It will help
visualize the topology, the text representation is a monster.
> Specifically I need to run the following script before capturing raw
> bayer from /dev/video0 :
>
> ```
> #!/bin/bash
>
> MDEV=/dev/media0
>
> media-ctl -d $MDEV -l "\"ov2740 19-0036\":0 -> \"Intel IPU6 CSI2 1\":0[1]"
>
> media-ctl -d $MDEV -V "\"ov2740 19-0036\":0 [fmt:SGRBG10/1932x1092]"
> media-ctl -d $MDEV -V "\"Intel IPU6 CSI2 1\":0 [fmt:SGRBG10/1932x1092]"
> media-ctl -d $MDEV -V "\"Intel IPU6 CSI2 1\":1 [fmt:SGRBG10/1932x1092]"
>
> media-ctl -d $MDEV -l "\"ov2740 19-0036\":0 -> \"Intel IPU6 CSI2 1\":0[1]"
> media-ctl -d $MDEV -l "\"Intel IPU6 CSI2 1\":1 -> \"Intel IPU6 ISYS Capture 0\":0[5]"
> ```
>
> Full media-ctl -p output below. So I guess that even without the ISP IPU6
> is probably going to need its own pipelinehandler, or am I missing something here?
[snip]
--
Regards,
Laurent Pinchart
More information about the libcamera-devel
mailing list