<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [SKL][Audio]cannot refresh the ELD information after xinit" href="https://bugs.freedesktop.org/show_bug.cgi?id=90447#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [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:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> Jani Nikula</a> <pre>(In reply to Mengdong Lin from <a href="show_bug.cgi?id=90447#c14">comment #14</a>) > Is it X that should trigger the modeset? Yes. The kernel sends a hotplug uevent the userspace listens to. Please verify that you get the uevent by running 'udevadm monitor' and plugging/unplugging. > And should x always trigger the modeset after a hot-plug in even if the > monitor EDID and resolution don't change? Yes. We don't cache that information, so they are lost on unplug. We don't know if the display is the same or not. > I guess i915 or DRM driver keeps the orignal EDID and resolution. No, we don't. The issue you're probably seeing is that hotplug/hotunplug itself does not set/invalidate the ELD, and therefore does not notify the audio driver. The notification to audio driver happens as part of the modeset sequence, triggered by userspace. If your userspace does get the hotplug uevent, but does not trigger the modeset, the problem is in your userspace. If your userspace does not get the uevent, or the subsequent modeset sequence triggered by userspace does not notify the audio driver, the problem is in the kernel display driver.</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>