On 01/10/2024 12:39, Luca Weiss wrote:
And v4l-subdev5 is msm_csid0 on my device.
<snip>
- entity 16: msm_csid0 (5 pads, 22 links, 0 routes)
type V4L2 subdev subtype Unknown flags 0
device node name /dev/v4l-subdev5
pad0: Sink
[stream:0 fmt:SRGGB10_1X10/4056x3040 field:none colorspace:srgb]
<- "msm_csiphy0":1 []
<- "msm_csiphy1":1 []
<- "msm_csiphy2":1 []
<- "msm_csiphy3":1 []
<- "msm_csiphy4":1 []
pad1: Source
[stream:0 fmt:SRGGB10_1X10/4056x3040 field:none colorspace:srgb]
-> "msm_vfe0_rdi0":0 [ENABLED]
-> "msm_vfe1_rdi0":0 []
-> "msm_vfe2_rdi0":0 []
-> "msm_vfe3_rdi0":0 []
-> "msm_vfe4_rdi0":0 []
<snip>
media-ctl --reset
yavta --no-query -w '0x009f0903 2' /dev/v4l-subdev5
yavta --list /dev/v4l-subdev5
media-ctl -V '"msm_csid0":0[fmt:SRGGB10/4056x3040]'
media-ctl -V '"msm_vfe0_rdi0":0[fmt:SRGGB10/4056x3040]'
media-ctl -l '"msm_csid0":1->"msm_vfe0_rdi0":0[1]'
media-ctl -d /dev/media0 -p
That command list and this
yavta -B capture-mplane -c -I -n 5 -f SRGGB10P -s 4056x3040 -F /dev/video0
should work.
I have to test Vladimir's two patches. I'll verify rb5 TPG while I'm at
it, perhaps the error is not sdm670 specific.
That said last time I tested it, it worked and no changes have gone in,
in the meantime.
---
bod
