<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption with refreshrates >73Hz when DPM changing VRAM clock"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105300#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption with refreshrates >73Hz when DPM changing VRAM clock"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105300">bug 105300</a>
from <span class="vcard"><a class="email" href="mailto:tempel.julian@gmail.com" title="tempel.julian@gmail.com">tempel.julian@gmail.com</a>
</span></b>
<pre>I thought of something similar too. But I'm far away from 330Mhz pixel clock.
I'm just using LCD standard timings, which result in a pixel clock of
304.37MHz:
<a href="https://abload.de/img/75hzhgs1d.png">https://abload.de/img/75hzhgs1d.png</a>
I also had the suspicion that the magic 300Mhz mark might be a problem, so I
created a resolution with custom timings for 74Hz which resulted in ~295MHz,
but the issue was still the same. It seems like it's really just about the
refresh rate and not the timings or pixelclock.</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>