<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [hsw DP-to-DVI] DP hot plug fails if booted without Monitor Attached" href="https://bugs.freedesktop.org/show_bug.cgi?id=85924#c43">Comment # 43</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [hsw DP-to-DVI] DP hot plug fails if booted without Monitor Attached" href="https://bugs.freedesktop.org/show_bug.cgi?id=85924">bug 85924</a> from <a class="email" href="mailto:paul.a.parenteau@intel.com" title="dog <paul.a.parenteau@intel.com>"> dog</a> <pre>Updating this thread, here's what one of our DP experts has to say: "What’s supposed to happen is that when HPD asserts, we get an interrupt that we process and fire off the appropriate work functions after we determine what to do with it. The work functions are where all the good stuff happens, calling the driver functions for ->detect() and intel_dp_hpd_pulse. Then then we go about setting up all the plane/pipe/port stuff for all the connectors that have been detected as being connected. For DP, we then read the DPCD, read the EDID and parse the display modes in it, figure out what the “preferred” mode is and set up the link configuration for that (by default - userspace can override it). There’s also a user space notification that takes place that notifies the fbdev components and calls their helper functions too." He's going to read through the dmesg logs to see how many steps in this process are taking place. Note: Intel OTC is still unable to reproduce the problem. (See note from Paulo above who is on my team) We need to be able to reproduce the problem so the matter can be investigated, preferably in the US or EMEA.</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>