[Bug 105887] [GLK] no signal after switch resolution from 1080p at 23.98
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Apr 23 08:19:45 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=105887
--- Comment #10 from shashank.sharma at intel.com <shashank.sharma at intel.com> ---
(In reply to Jani Saarinen from comment #6)
> Shashank, Ville, any commments?
There is something fishy with the EDID's extension blocks for this monitor.
first probe, EDID says neither 420_only nor 420_also supported:
=============
[ 1.278592] [drm:drm_add_display_info] *ERROR* YCBCR420 (also) supported =N
[ 1.278596] [drm:drm_add_display_info] *ERROR* YCBCR420 (only) supported =N
[ 1.278600] [drm:drm_add_display_info] *ERROR* YCBCR420 dc support =N
[ 1.278604] [drm:drm_add_display_info] *ERROR* ========
====================================
second probe says 420_also modes supported but no 420_only mode:
=============
[ 1.278673] [drm:drm_add_display_info] *ERROR* YCBCR420 (also) supported =Y
[ 1.278678] [drm:drm_add_display_info] *ERROR* YCBCR420 (only) supported =N
[ 1.278682] [drm:drm_add_display_info] *ERROR* YCBCR420 dc support =N
[ 1.278686] [drm:drm_add_display_info] *ERROR* ========
====================================
and the third probe says both 420_also as well as 420_only supported:
=============
[ 1.460456] [drm:drm_add_display_info] *ERROR* YCBCR420 (also) supported =Y
[ 1.460564] [drm:drm_add_display_info] *ERROR* YCBCR420 (only) supported =Y
[ 1.460566] [drm:drm_add_display_info] *ERROR* YCBCR420 dc support =N
[ 1.460567] [drm:drm_add_display_info] *ERROR* ========
====================================
I am not sure how HF-VSDB block is changing every probe, that to in an
incremental supported way :)
- Shashank
--
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/20180423/03dc387e/attachment.html>
More information about the intel-gfx-bugs
mailing list