Re: [PATCH v14 2/2] arm64: dts: qcom: qcs6490-rb3gen2-vision-mezzanine: Add vision mezzanine

[Bryan O'Donoghue]

On 04/03/2025 08:51, Jorge Ramirez wrote:
> On 04/03/25 09:40:21, Krzysztof Kozlowski wrote:
> > On 04/03/2025 09:36, Jorge Ramirez wrote:
> > > On 03/03/25 18:13:20, Krzysztof Kozlowski wrote:
> > > > On 08/02/2025 23:51, Vikram Sharma wrote:
> > > > > The Vision Mezzanine for the Qualcomm RB3 Gen 2 ships with an imx577
> > > > > camera sensor. Enable IMX577 on the vision mezzanine.
> > > > >
> > > > > An example media-ctl pipeline for the imx577 is:
> > > > >
> > > > > media-ctl --reset
> > > > > media-ctl -V '"imx577 '17-001a'":0[fmt:SRGGB10/4056x3040 field:none]'
> > > >
> > > > AFAIU, camss does not support SRGGB10, but only SRGGB10P.
> > > >
> > > > Based on tests reported on IRC I think this might not have been tested
> > > > correctly.
> > >
> > > I acquired SRGGB10P (10 bit packed) frames from the camera despite the
> > > pipeline being set to SRGGB10 (16 bit) samples.
> > >
> > > so something does not add up.
> >
> > Then the commands are actually correct, just the camss or media behave
> > here a bit unexpected?
>
> setting the pipeline (CSI) as SRGGB10 (16 bit samples) as per below
>
> media-ctl --reset
> media-ctl -v -V '"imx577 '19-001a'":0[fmt:SRGGB10/4056x3040 field:none]'
> media-ctl -V '"msm_csiphy3":0[fmt:SRGGB10/4056x3040]'
> media-ctl -V '"msm_csid0":0[fmt:SRGGB10/4056x3040]'
> media-ctl -V '"msm_vfe0_rdi0":0[fmt:SRGGB10/4056x3040]'
> media-ctl -l '"msm_csiphy3":1->"msm_csid0":0[1]'
> media-ctl -l '"msm_csid0":1->"msm_vfe0_rdi0":0[1]'
>
> allows to capture SRGGB10P samples (frames-xxxx.bin files contain 10 bit samples for the size)
>
>   ==> yavta -B capture-mplane -c -I -n 5 -f SRGGB10P -s 4056x3040 -F /dev/video0
>
>
> shouldnt the CSI need to be set to SRGGB10P instead?
>
>
> > Best regards,
> > Krzysztof

No an internal media bus format MEDIA_BUS_FMT_THING is used

See

87889f1b7ea40d2544b49c62092e6ef2792dced7
5480b0c67f120a6c293cc5eff72fa1d6a74de504
3c1dfb5a69cf836f513a2a49113ee946a4b9d95d

Yavta is specifying a v4l2 pixel format SRGGB10P which then gets 
translated into a media bus format MEDIA_BUS_FMT_SRGGB10_1X10.

I'm not sure what the historical reasons for that are, probably good ones.

---
bod