<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <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#c65">Comment # 65</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 <a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> Alex Deucher</a> <pre>(In reply to iuno from <a href="show_bug.cgi?id=93826#c64">comment #64</a>) > (In reply to Alex Deucher from <a href="show_bug.cgi?id=93826#c63">comment #63</a>) > > > > Are you forcing the power state to high? The mclk shouldn't be affected by > > the display clock. > > 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. Yes, that is independent of the patch in <a href="attachment.cgi?id=131983" name="attach_131983" title="possible fix">attachment 131983</a> <a href="attachment.cgi?id=131983&action=edit" title="possible fix">[details]</a> <a href='page.cgi?id=splinter.html&bug=93826&attachment=131983'>[review]</a>. The driver disables dynamic mclk switching for refresh rates above 120 hz to avoid flickering.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>