<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [i915] HDMI connector status is connected after disconnection" href="https://bugs.freedesktop.org/show_bug.cgi?id=107125#c21">Comment # 21</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [i915] HDMI connector status is connected after disconnection" href="https://bugs.freedesktop.org/show_bug.cgi?id=107125">bug 107125</a> from <a class="email" href="mailto:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> Jani Nikula</a> <pre>Copy-pasting what I've written before, and was pasted to <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - [i915] HDMI connector status is connected when plug out HDMI very slowly" href="show_bug.cgi?id=110835">bug 110835</a> too: --- We get a hotplug interrupt before the plug is completely out, while ddc communication still works with the display, and we conclude we are still connected. Moreover, the live status bits on the hotplug state have been notoriously unreliable in the past, we've tried using them like three times in the past, leading to regressions and reverts every time. You can come up with all sorts of pathological slow plug/unplug/wiggle cases. If you have a concrete requirement how slow needs to be okay, or better yet write a test case for igt and chamelium, we can work with that. We've proposed fixes in the past but they stalled because some undisclosed unquantified test case still failed. --- Presumably we're getting the issues because we've improved our hotplug and/or ddc code to not have too much inherent delays. The actual user reported bugs apparently get fixed by all of the proposed solutions. The failures in undisclosed tests only get fixed by Guang Bai's patches, but IMO that's a moot point as long as we don't have access to the tests and can't verify the tests make sense. Finally, any solution resorting to using hotplug live status (including Guang Bai's patches) *absolutely* *must* dig through the sad history of it, commit by commit in git logs, and explain in excruciating detail why it failed several times before, and why it would be different this time. I'm not accepting anything with roundabout "it should just work" statements.</pre> </div> <hr> You are receiving this mail because: <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>