<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 - fail - Failed assertion: igt_hotplug_detected(mon, HOTPLUG_TIMEOUT)" href="https://bugs.freedesktop.org/show_bug.cgi?id=111045#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@kms_chamelium@(hdmi|dp)-hpd-fast - 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#c6">comment #6</a>) > There could be a chamelium config issue wrt. HDMI, since there is no HDMI > sinks connected (even the USBC->HDMI dongle will show up as DP), but the > HDMI chamelium subtests are not skipped as they should be. I think the configuration is fine. I routinely run HDMI tests on my DP port with lspcon, and configuring .igtrc to map the DUT DP output to the Chamelium HDMI input works. > However probably all the DP kms_chamelium tests will fail expectedly on > DP-alt outputs. Can you elaborate? I'm not sure I understand. > The exceptions could be kms_chamelium subtests where the > subtest properly handles hotplug events: enables/disables the output > according to the connect/disconnect hotplug event it receives. That's not > the case atm with most of the kms_chamelium subtests. Why is this needed? If a user plugs a USB-C to HDMI dongle, the DRM client should see a hotplug event even if the output hasn't been enabled yet, right? Some tests currently assert HPD on the Chamelium side and expect a hotplug. Is this supposed not to work with DP-ext?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>