Re: [PATCH v2 0/4] media: qcom: flip the switch between Venus and Iris drivers

On 1/27/2026 5:35 PM, Dmitry Baryshkov wrote:

On Tue, Jan 27, 2026 at 12:43:36PM +0100, Konrad Dybcio wrote:

quoted

On 1/26/26 3:09 AM, Dmitry Baryshkov wrote:

quoted

As the Venus and Iris drivers are close to the "feature parity" for the
common platforms (SC7280, SM8250), in order to get more attention to
squashing bugs from the Iris driver, flip the switch and default to the
Iris driver if both are enabled. The Iris driver has several
regressions, but hopefully they can be fixed through the development
cycle by the respective team. Also it is better to fail the test than
crash the device (which Venus driver does a lot).

Note: then intention is to land this in 6.21, which might let us to
drop those platforms from the Venus driver in 6.22+.

Testing methodology: fluster test-suite, single-threaded mode, SM8250
device (RB5).

$ ./fluster.py r -j 1 -d  GStreamer-H.264-V4L2-Gst1.0 -s -so out-h264.md -ts JVT-AVC_V1
$ ./fluster.py r -j 1 -d  GStreamer-H.265-V4L2-Gst1.0 -s -so out-h265.md -ts JCT-VC-HEVC_V1
$ ./fluster.py r -j 1 -d  GStreamer-VP9-V4L2-Gst1.0 -s -so out-vp9.md

For H.264:

Only the main set was used on both platforms

On Venus pass 126/135
On Iris  pass 78/135

This sounds a little bad..

I'd let Vikash comment here, we were promised feature parity for Venus /
Iris drivers before accepting the latter one.

The list of tests passing for Venus, but failing for Iris:

quoted

|BA3_SVA_C|✔️|

This need to be checked. Similar failure was seen in SM8550 due to 
unssuported profile V4L2_MPEG_VIDEO_H264_PROFILE_EXTENDED.

< |cabac_mot_fld0_full|✔️|
< |cabac_mot_mbaff0_full|✔️|
< |cabac_mot_picaff0_full|✔️|
< |CAFI1_SVA_C|✔️|
< |CAMA1_Sony_C|✔️|
< |cama1_vtc_c|✔️|
< |cama2_vtc_b|✔️|
< |cama3_vtc_b|✔️|
< |CAMACI3_Sony_C|✔️|
< |CAMASL3_Sony_B|✔️|
< |CAMP_MOT_MBAFF_L30|✔️|
< |CAMP_MOT_MBAFF_L31|✔️|
< |CANLMA2_Sony_C|✔️|
< |CANLMA3_Sony_C|✔️|
< |cavlc_mot_fld0_full_B|✔️|
< |cavlc_mot_mbaff0_full_B|✔️|
< |cavlc_mot_picaff0_full_B|✔️|
< |CVCANLMA2_Sony_C|✔️|
< |CVFI1_Sony_D|✔️|
< |CVFI1_SVA_C|✔️|
< |CVFI2_Sony_H|✔️|
< |CVFI2_SVA_C|✔️|
< |CVMA1_Sony_D|✔️|
< |CVMAPAQP3_Sony_E|✔️|
< |CVMAQP2_Sony_G|✔️|
< |CVMAQP3_Sony_D|✔️|
< |CVMP_MOT_FLD_L30_B|✔️|
< |CVMP_MOT_FRM_L31_B|✔️|
< |CVNLFI1_Sony_C|✔️|
< |CVNLFI2_Sony_H|✔️|
< |FI1_Sony_E|✔️|
< |MR9_BT_B|✔️|
< |Sharp_MP_Field_1_B|✔️|
< |Sharp_MP_Field_2_B|✔️|
< |Sharp_MP_Field_3_B|✔️|
< |Sharp_MP_PAFF_1r2|✔️|
< |Sharp_MP_PAFF_2r|✔️|

Above tests are related to interlace support. As of now, interlace 
support is not there in iris driver, as it is gradually evolving w.r.t 
enabling available hardware codecs.

quoted

[...]

quoted

For Venus several tests crash the firmware or crash the device,
so test-suite was executed with extra:

But this sounds way way worse

[...]

quoted

For H.265:

Only the main set was used on both platforms

On Venus pass 135/147
On Iris  pass 133/147

[...]

quoted

For VP9 codec:

On Venus pass 174/311
On Iris  pass 232/311

These two give me hope..

Ultimately, I think it's the right thing to do, if only to prevent the
crashes you've described..

Yep.

Regards,
Vikash