2023-02-20 14:42:35

by Naresh Kamboju

Subject: v4l2-test-controls.cpp(325): expected 8 private controls, got 7

Following v4l2 tests are failing on Linux mainline v6.2 on arm64 hikey device.
Am I missing anything in my test environment ?

Driver Info:
----------
Driver name : vivid
Bus info : platform:vivid-000
Driver version : 6.2.0

Fail log:
---------
fail: v4l2-test-controls.cpp(325): expected 8 private controls, got 7
test VIDIOC_QUERY_EXT_CTRL/QUERYMENU: FAIL
fail: v4l2-test-controls.cpp(366): qctrl.step || qctrl.minimum ||
qctrl.maximum || qctrl.default_value
test VIDIOC_QUERYCTRL: FAIL
..
fail: v4l2-test-controls.cpp(473): g_ctrl returned an error (22)
test VIDIOC_G/S_CTRL: FAIL
..
fail: v4l2-test-controls.cpp(593): returned control value out of range
fail: v4l2-test-controls.cpp(706): invalid control 0098f90f
test VIDIOC_G/S/TRY_EXT_CTRLS: FAIL
..
fail: v4l2-test-formats.cpp(264): fmtdesc.description mismatch:
was 'Y/UV 4:2:0', expected 'Y/CbCr 4:2:0'
test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: FAIL


Test details,
https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2/testrun/14859062/suite/v4l2-compliance/tests/
https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2/testrun/14859062/suite/v4l2-compliance/test/VIDIOC_ENUM_FMT-FRAMESIZES-FRAMEINTERVALS/log

--
Linaro LKFT
https://lkft.linaro.org

2023-02-20 15:10:59

by Hans Verkuil

Subject: Re: v4l2-test-controls.cpp(325): expected 8 private controls, got 7

On 20/02/2023 15:42, Naresh Kamboju wrote:
> Following v4l2 tests are failing on Linux mainline v6.2 on arm64 hikey device.
> Am I missing anything in my test environment ?
>
> Driver Info:
> ----------
> Driver name : vivid
> Bus info : platform:vivid-000
> Driver version : 6.2.0
>
> Fail log:
> ---------
> fail: v4l2-test-controls.cpp(325): expected 8 private controls, got 7
> test VIDIOC_QUERY_EXT_CTRL/QUERYMENU: FAIL
> fail: v4l2-test-controls.cpp(366): qctrl.step || qctrl.minimum ||
> qctrl.maximum || qctrl.default_value
> test VIDIOC_QUERYCTRL: FAIL
> ..
> fail: v4l2-test-controls.cpp(473): g_ctrl returned an error (22)
> test VIDIOC_G/S_CTRL: FAIL
> ..
> fail: v4l2-test-controls.cpp(593): returned control value out of range
> fail: v4l2-test-controls.cpp(706): invalid control 0098f90f
> test VIDIOC_G/S/TRY_EXT_CTRLS: FAIL
> ..
> fail: v4l2-test-formats.cpp(264): fmtdesc.description mismatch:
> was 'Y/UV 4:2:0', expected 'Y/CbCr 4:2:0'

This suggests that you are running with an old(er) v4l-utils version, since I adapted
v4l2-compliance to avoid this failure. It's due to a change in the kernel, so currently
both old and new descriptions are accepted.

Looking at the logs:

v4l2-compliance SHA: 5d8c459c1bf9 2021-04-08 13:28:26

That's much too old.

Regards,

Hans

> test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: FAIL
>
>
> Test details,
> https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2/testrun/14859062/suite/v4l2-compliance/tests/
> https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2/testrun/14859062/suite/v4l2-compliance/test/VIDIOC_ENUM_FMT-FRAMESIZES-FRAMEINTERVALS/log
>
> --
> Linaro LKFT
> https://lkft.linaro.org