<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED INVALID - [SKL][Audio]cannot refresh the ELD information after xinit" href="https://bugs.freedesktop.org/show_bug.cgi?id=90447#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED INVALID - [SKL][Audio]cannot refresh the ELD information after xinit" href="https://bugs.freedesktop.org/show_bug.cgi?id=90447">bug 90447</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>The stance we have taken is that userspace is in charge of handling notifications to topology changes - for a couple of reasons, this moves the policy from the kernel to the user, and the other is that it should allow for fast reconnection (often also desirable, but impossible if the kernel acts). You actually need to run "udevadm monitor --property --tag-match=HOTPLUG" to see if the hotplug event is indeed the uevent being sent. Equally a small X client listening to RR notifications to confirm that they are being received and propagated (X needs to be built with udev support for example). And finally, but not last of all you need a client to respond to the RR notifications and issue a new modeset (and that depends upon your window/desktop/session manager). As a last resort, an xrandr --auto, should issue the modeset required to confirm that ELD notifications are being sent following a modeset following a hotplug.</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>