<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 - [DC] - Maximum pixel clock of dual-link DVI too low for some modes"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105302">105302</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[DC] - Maximum pixel clock of dual-link DVI too low for some modes
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (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>DRM/AMDgpu
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>asheldon55@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>I have a monitor that supports 2560x1440 >60hz (up to around 110hz) through the
DVI-D interface but requires pixel clocks greater than the current dual-link
limit of 330khz, with amdgpu.dc=1. Setting TMDS_MAX_PIXEL_CLOCK to 250000 in
signal_types.h works around the problem.
amdgpu.dc=0 doesn't appear to have this limit (or the value is higher) so the
problem does not exist there.
I'm using ~ag5df's drm-next-4.17-wip branch.
There appears to be a discussion about setting a higher pixel clock limit in
this bug: <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - radeon: allow the user to set a maximum HDMI pixel clock (in MHz) by a kernel parameter"
href="show_bug.cgi?id=93885">https://bugs.freedesktop.org/show_bug.cgi?id=93885</a> but focused on
HDMI and not DVI-D, and regarding the older radeon driver.</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>