<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - connector properties sometimes go outdated" href="https://bugs.freedesktop.org/show_bug.cgi?id=92728#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - connector properties sometimes go outdated" href="https://bugs.freedesktop.org/show_bug.cgi?id=92728">bug 92728</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>So at first, I thought it was the loop in sna_output_detect() not filling in the properties, but the kernel should always fill in the property values, even when just querying the mode count. The expectation is that we call sna_output_detect() everytime we have reason to believe the output has changed (i.e. hotplug uevent or user reprobe). During the detect we then refresh the property values. The EDID property is rather special in terms of the connector properties as it gets explicitly updated by get_modes() (after detect). If the EDID was swapped (but the connector status remained the same) it could miss the update, but the modes would remain the same as well. It wouldn't be the same effect as not returning an EDID at all though. Hmm. The problem appears to be that the kernel changes the ID whenever, not on an actual EDID change. That means we always have the issue that the EDID value can be out of date after being set in detect by the time we reach attach_edid.</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> </ul> </body> </html>