<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69721">69721</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>alexandre.f.demers@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg CVS
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Radeon
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>After fixing <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Display freezes after login with kernel 3.11.0-rc5 on Cayman with dpm=1"
href="show_bug.cgi?id=68235">bug 68235</a>, it appears the maximum memory speed (or core speed)
can't always be reached. This situation depends on the voltage tweaking seen on
some cards. As an exemple, XFX HD-695X-ZNDC has the following maximum values:
max_sclk_vddc->80000, max_mclk_vddci->125000, max_mclk_vddc->125000.
However, the maximum memory clock value should be 130000 and the core clock
should be 83000.
As Alex Deucher explained: "This patch set works around the issue by limiting
the sclk and mclk to the highest levels listed in the clk/voltage dependency
tables. I'll need to dig a bit more internally to try and figure out how to
handle these clks properly."</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>