<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - i915: regression: after DP connected (via docking station) monitor is turned off, when turned on, it does not work anymore" href="https://bugs.freedesktop.org/show_bug.cgi?id=88124#c83">Comment # 83</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - i915: regression: after DP connected (via docking station) monitor is turned off, when turned on, it does not work anymore" href="https://bugs.freedesktop.org/show_bug.cgi?id=88124">bug 88124</a> from <a class="email" href="mailto:ville.syrjala@linux.intel.com" title="Ville Syrjala <ville.syrjala@linux.intel.com>"> Ville Syrjala</a> <pre>(In reply to Jiri Pirko from <a href="show_bug.cgi?id=88124#c82">comment #82</a>) > (In reply to Dhinakaran Pandiyan from <a href="show_bug.cgi?id=88124#c81">comment #81</a>) > > Jiri, > > > > Sorry about the bug getting closed, I haven't worked on this for a while. > > There were no patches merged to address the connector ID change, so the > > retest on drm-tip wasn't necessary IMO. However, there was another related > > issue (monitor on-off) with the same configuration that got fixed. This was > > the reason for @c58 and it seems like the thread got sidetracked since that > > point. > > > > A quick note about the connector IDs. The connectors for displays attached > > to the docking station are created and destroyed dynamically during during > > hotplug/monitor off-on. This is why the ID's change and the flip-flopping of > > connector ID's is probably due to the order in which connectors are > > destroyed and created again. User space is typically able to handle this. > > Connector ID's are stable only for ports directly connected to the GPU. For > > e.g., connector 82: type DP-2 for the docking station is what is going to > > stay the same. > > > > As long as the kernel updates the connection status correctly and sends > > hotplug events, user space is expected to deal with change in connector IDs. > > I am not familiar with xmonad, so I don't know what's going on there. Let me > > see if I can find out more. > > The thing is, there has to be some userspace daemon monitoring the events > and pushing the setting down accordingly. I have no such daemon. > Previously, before patch 0e32b39ceed665bfa4a77a4bc307b6652b991632, the ids > were stable so all worked fine even without need to any additional userspace > daemon. > Could you make the connector IDs stable again? They were never actually stable. You just got lucky earlier.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>