<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [SKL Bisected] eDP can not be lighted up after entering kernel" href="https://bugs.freedesktop.org/show_bug.cgi?id=89554#c40">Comment # 40</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [SKL Bisected] eDP can not be lighted up after entering kernel" href="https://bugs.freedesktop.org/show_bug.cgi?id=89554">bug 89554</a> from <a class="email" href="mailto:sonika.jindal@intel.com" title="Sonika <sonika.jindal@intel.com>"> Sonika</a> <pre>(In reply to Jesse Barnes from <a href="show_bug.cgi?id=89554#c39">comment #39</a>) > I guess this isn't as simple as trying other vswing params, since it affects > the DDI side too. But ideally, if we failed to train like we see here, we'd > try a higher set of vswing values on the DDI side and restart DP training. > How feasible is that? If Windows does that, we'll probably see busted VBTs > in the wild too, so making our re-training code more robust would be helpful. The windows too don't try to retrain with different set of values. Since any set of values cant guarantee working of all the panels universally, the end system integrators are expected to try both the settings in VBT. This suggestion of retraining with higher/lower values came up earlier too. We can give it a try.</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>