<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - HDMI not working on Skylake with EDID read error"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109273#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - HDMI not working on Skylake with EDID read error"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109273">bug 109273</a>
from <span class="vcard"><a class="email" href="mailto:jani.saarinen@intel.com" title="Jani Saarinen <jani.saarinen@intel.com>"> <span class="fn">Jani Saarinen</span></a>
</span></b>
<pre>hi,
Update from Sashank too and similar findings:
>From the logs I can see that these 2 devices have different type of adapters:
The success case (U757): is a type 2 DP->HDMI [drm_kms_helper]] DP dual mode
HDMI ID: DP-HDMI ADAPTOR\004 (err 0) [drm_kms_helper]] DP dual mode adaptor ID:
a0 (err 0) [i915]] DP dual mode adaptor (type 2 HDMI) detected (max TMDS clock:
300000 kHz)
The failure case (E756): is a Type 1 DP->HDMI [drm_kms_helper]] DP dual mode
HDMI ID: DP-HDMI ADAPTOR\004 (err 0) [drm_kms_helper]] DP dual mode adaptor ID:
ff (err 0) [i915]] DP dual mode adaptor (type 1 HDMI) detected (max TMDS clock:
165000 kHz)
Looks like the type-1 adapter is not responding to i2c-over-aux reads after one
power-down, which is causing the detection failure, further causing the display
failures.</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 the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>