[Bug 77908] [IVB Bisected]Subcases dpms-vs-vblank-race-interruptible and modeset-vs-vblank-race of kms_flip fail
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Apr 29 21:08:34 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=77908
--- Comment #4 from Guo Jinxian <jinxianx.guo at intel.com> ---
This commit below fixed the bug. Reset to
b6842feb63a23a6a988f4e1ffb93408d8ff6931e and reverted commit
b6842feb63a23a6a988f4e1ffb93408d8ff6931e, the test result was failed.
commit b6842feb63a23a6a988f4e1ffb93408d8ff6931e
Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
Date: Thu Mar 27 11:08:45 2014 +0200
drm/i915: Allow user modes to exceed DVI 165MHz limit
In commit
commit 6375b768a9850b6154478993e5fb566fa4614a9c
Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
Date: Mon Mar 3 11:33:36 2014 +0200
drm/i915: Reject >165MHz modes w/ DVI monitors
the driver started to filter out display modes which exceed the
single-link DVI 165Mz dotclock limits when the monitor doesn't report
itself as being HDMI compliant. The intent was to filter out all
EDID derived modes that require dual-link DVI to operate since we
don't support dual-link.
However the patch went a bit too far and also causes the driver to reject
such modes even when specified by the user. Normally we don't check the
sink limitations when setting a mode from the user. This allows the user
to specify any mode whether the sink reports to support it or not. This
can be useful since often the sinks support more modes than they report
in the EDID.
So relax the checks a bit, and apply the single-link DVI dotclock limit
only when filtering the mode list, and ignore the limit when setting
a user specified mode.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=72961
Tested-by: Nicholas Vinson <nvinson at comcast.net>
Cc: stable at vger.kernel.org [3.14]
Reviewed-by: Daniel Vetter <daniel at ffwll.ch>
Signed-off-by: Ville Syrjälä <ville.syrjala at linux.intel.com>
Signed-off-by: Jani Nikula <jani.nikula at intel.com>
:040000 040000 e5dd0a22c4ec8df198400605e960f8c683e732ed
4e2a40b8ecf829d92060ba7561ae6a7f7981878c M drivers
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140430/7a5e6f37/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list