[Bug 110692] [CI][DRMTIP] igt at kms_invalid_dotclock - fail - Failed assertion: ret < 0, error: 0 >= 0

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=110692

--- Comment #2 from Ankit <ankit.k.nautiyal at intel.com> ---
What the subtest is doing : The subtest : kms_invalid_dotclock is a negative
test case. It verifies that any mode with a dotclock value, higher than the max
dotclock should not get applied and the IOCTL should fail.

The test gets the max dotclock value from debugfs : i915_frequency_info. A user
tailored drmModeModeInfo is taken and its clock is intentionally kept more than
the max dotclock. The test then tries to set this mode using drmModeSetCrtc and
expects the IOCTL to fail.

The issue: The issue here is seen with MIPI display, the issue is that the
IOCTL passes, instead of failing. 

The kernel currently, ignores the user timing for mode clock, in case of
connectors with fixed modes, and therefore the mode set passes.

The test acknowledges this fact in the comments, and has a check for skipping
the test with connectors having fixed mode.

This check however depends upon the connector property "scaling mode" which is
missing in the kernel for ICL platform.

Resolution :  The patch [1] from Vandita Kulkarni introduces this property, and
is under review. With this patch the test will skip the case with MIPI display,
since it has fixed mode, which is the expected behavior.

[1] https://patchwork.freedesktop.org/patch/309595/?series=61862&rev=1

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190627/fcd4338d/attachment.html>