<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - 2560x1440 @144Hz graphic glitches and bad refresh rate"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93826#c64">Comment # 64</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - 2560x1440 @144Hz graphic glitches and bad refresh rate"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93826">bug 93826</a>
from <span class="vcard"><a class="email" href="mailto:iuno@posteo.net" title="iuno@posteo.net">iuno@posteo.net</a>
</span></b>
<pre>(In reply to Alex Deucher from <a href="show_bug.cgi?id=93826#c63">comment #63</a>)
<span class="quote">>
> Are you forcing the power state to high? The mclk shouldn't be affected by
> the display clock.</span >
No, setting the refresh rate to 144 results in high mclk, even when I set
power_dpm_force_performance_level to low or pp_dpm_mclk to 0. Using 120 Hz, I
could echo 0 or 1 to pp_dpm_mclk. I also got the power meter on now:
memory dpm state 0 (150 MHz): 77 watts
memory dpm state 1 (1250 MHz): 112 watts
So there is a difference of 35 watts. Using Windows, I'm below the 80 Watts
even with 144 Hz.</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>