<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - HDMI connected monitors fail to sleep and instead turn back on when amdgpu.dc=1" href="https://bugs.freedesktop.org/show_bug.cgi?id=109246#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - HDMI connected monitors fail to sleep and instead turn back on when amdgpu.dc=1" href="https://bugs.freedesktop.org/show_bug.cgi?id=109246">bug 109246</a> from <a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> Alex Deucher</a> <pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=109246#c8">comment #8</a>) > > This does look like there are hotplug events, and the HDMI output is > considered disconnected for a moment. When the monitor enters dpms, it starts polling inputs so it can light up whatever input gets connected without the user having to manually select the input. This can cause havoc with drivers sometimes. > > (In reply to Alex Deucher from <a href="show_bug.cgi?id=109246#c5">comment #5</a>) > > Some monitors poll inputs which sometimes causes the hpd pin to fire which > > looks like a hotplug event to the driver. > > Any idea why this seems to only cause trouble with DC though? DC handles both short and long pulses while I think the non-DC code only handles long pulses. IIRC, the only difference is the length of the pulse and I think the register values used to determine the pulse length are tuned slightly differently in DC to deal with other problematic monitors. I suspect tuning those settings would fix the issue, but I don't know if it would break other things.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>