<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - link retraining for DP not possible with current design of Atomic modeset framework"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91871">91871</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>link retraining for DP not possible with current design of Atomic modeset framework
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>General
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>sivakumar.thulasimani@intel.com
</td>
</tr></table>
<p>
<div>
<pre>DP spec requires Link training from highest link rate supported by panel to
lowest link rate supported by panel.
It is not possible to implement this in the current atomic modeset logic since
it splits modeset into two half atomic_check and atomic_commit, where it is
expected all values to be calculated in atomic_check and programmed in
atomic_commit.
link training being a negotiation phase of DP modeset it is not possible to
predict if a training at certain link rate will succeed or not. if it does fail
it will require us to disable, calculate new values and enable pll. this is not
possible in current DRM Atomic modeset framework.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>