<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [GLK] no signal after switch resolution from 1080p@23.98"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105887#c75">Comment # 75</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [GLK] no signal after switch resolution from 1080p@23.98"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105887">bug 105887</a>
from <span class="vcard"><a class="email" href="mailto:clinton.a.taylor@intel.com" title="Clinton Taylor <clinton.a.taylor@intel.com>"> <span class="fn">Clinton Taylor</span></a>
</span></b>
<pre>(In reply to <a href="mailto:shashank.sharma@intel.com">shashank.sharma@intel.com</a> from <a href="show_bug.cgi?id=105887#c74">comment #74</a>)
<span class="quote">> Well, I could not relate that, as there are few parallel thread. Also I
> don't understand why we need a HDMI 2.0 retimer on GLK as it already has a
> HDMI 2.0 native controller, unless someone needs 2 or 3 HDMI 2.0 sources
> coming out of GLK NUC, and NUC was short of it, and some platform team
> decided to use some Paradetech dongle to convert DP 1.2 -> HDMI 2.0.
> </span >
The ITE66317 retimer implementation does seem to be causing the Linux driver
some difficulty. Based on what I have seen so far, the Linux driver doesn't
wait long enough during mode changes for the retimer to sync correctly to the
new faster clock.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>