<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@kms_chamelium@(hdmi|dp)-hpd-fast|igt@kms_chamelium@dp-edid-change-during-suspend - fail - Failed assertion: igt_hotplug_detected(mon, HOTPLUG_TIMEOUT)" href="https://bugs.freedesktop.org/show_bug.cgi?id=111045#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@kms_chamelium@(hdmi|dp)-hpd-fast|igt@kms_chamelium@dp-edid-change-during-suspend - fail - Failed assertion: igt_hotplug_detected(mon, HOTPLUG_TIMEOUT)" href="https://bugs.freedesktop.org/show_bug.cgi?id=111045">bug 111045</a> from <a class="email" href="mailto:contact@emersion.fr" title="emersion <contact@emersion.fr>"> emersion</a> <pre>(In reply to Imre Deak from <a href="show_bug.cgi?id=111045#c15">comment #15</a>) > If unplugging a DP-alt display while there is an active modeset on it, and > then replugging the DP-alt display, the HW/FW/driver won't signal the > corresponding plug-in hotplug event until the mode is disabled. Hmm, I see. > The failing tests do this: > > - <have the output enabled> > - unplug the display, keeping the output enabled > - wait/poll for the disconnect status -> success > - replug the display, while the output is still enabled > - wait/poll for the connect status -> fail > > This sequence is not supported with DP-alt sinks (like the USB-C to HDMI > dongle), as I described above. Thanks for the explanation! > If there wouldn't be any mode enabled for the whole duration of the > sequence, or the client would enable/disable the mode according to the > output's connected/disconnected status, then all the hotplug uevents, > polling would work as the test expects. I'll try to send a patch to do this.</pre> </div> <hr> You are receiving this mail because: <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>