<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [BYT] No HDMI hotplugging"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89008#c15">Comment # 15</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [BYT] No HDMI hotplugging"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89008">bug 89008</a>
from <span class="vcard"><a class="email" href="mailto:eich@pdx.freedesktop.org" title="Egbert Eich <eich@pdx.freedesktop.org>"> <span class="fn">Egbert Eich</span></a>
</span></b>
<pre>(In reply to Ville Syrjala from <a href="show_bug.cgi?id=89008#c11">comment #11</a>)
<span class="quote">> (In reply to Ville Syrjala from <a href="show_bug.cgi?id=89008#c10">comment #10</a>)
> > The GPIO approach would involve changing the pin muxing depending on the
> > state of the power well (or maybe leave them as GPIO pins all the time?).
>
> Oh yeah we can't leave them as GPIO pins since we'll be wanting the hardware
> long/short pulse detection to work.</span >
In the case where the power wells are off (ie. no displays connected and link
down) this is probably irrelevant as in this situation you would only expect a
long pulse, short pulses (ie sink issuing an IRQ) should only happen when the
link is up, shouldn't they?</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>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>