<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Unable to detect monitor modes connected to a TB16 Dell dock" href="https://bugs.freedesktop.org/show_bug.cgi?id=111507#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Unable to detect monitor modes connected to a TB16 Dell dock" href="https://bugs.freedesktop.org/show_bug.cgi?id=111507">bug 111507</a> from <a class="email" href="mailto:stanislav.lisovskiy@intel.com" title="Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>"> Stanislav Lisovskiy</a> <pre>(In reply to Ville Syrjala from <a href="show_bug.cgi?id=111507#c9">comment #9</a>) > (In reply to Stanislav Lisovskiy from <a href="show_bug.cgi?id=111507#c7">comment #7</a>) > > I've looked briefly into the log. There seems to be multiple DP MST > > connectors detected and some modes were pruned as invalid. > > > > Another thing is that if correspondent i915_display_info debugfs entry > > doesn't display anything except this: > > > > connector 118: type DP-5, status: connected > > physical dimensions: 600x340mm > > subpixel order: Unknown > > CEA rev: 3 > > > > it means that it could not find an intel_encoder, > > That's a clear bug in i915_display_info. It should still list the modes even > if there's no encoder. Yep, but there is this line: if (!intel_encoder) return; Have no clue why its there, probably it was added because in next few lines it tries to display info based on intel_encoder->type. We could just move that code: seq_printf(m, "\tmodes:\n"); list_for_each_entry(mode, &connector->modes, head) intel_seq_print_mode(m, 2, mode); before this condition, in order to display modes..</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>