From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate Date: Thu, 15 Jun 2017 20:24:26 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1046860692==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id EA1ED6E80C for ; Thu, 15 Jun 2017 20:24:26 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1046860692== Content-Type: multipart/alternative; boundary="14975582669.F663CBF16.28756"; charset="UTF-8" --14975582669.F663CBF16.28756 Date: Thu, 15 Jun 2017 20:24:26 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D93826 --- Comment #65 from Alex Deucher --- (In reply to iuno from comment #64) > (In reply to Alex Deucher from comment #63) > >=20 > > Are you forcing the power state to high? The mclk shouldn't be affecte= d by > > the display clock. >=20 > 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 H= z, > I could echo 0 or 1 to pp_dpm_mclk. I also got the power meter on now: >=20 > memory dpm state 0 (150 MHz): 77 watts > memory dpm state 1 (1250 MHz): 112 watts >=20 > So there is a difference of 35 watts. Using Windows, I'm below the 80 Wat= ts > even with 144 Hz. Yes, that is independent of the patch in attachment 131983. The driver disables dynamic mclk switching for refresh rates above 120 hz to avoid flickering. --=20 You are receiving this mail because: You are the assignee for the bug.= --14975582669.F663CBF16.28756 Date: Thu, 15 Jun 2017 20:24:26 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 65 on bug 93826<= /a> from Alex Deucher 
(In reply to iuno from comment #64)
> (In reply to Alex Deucher from comment #63)
> >=20
> > Are you forcing the power state to high?  The mclk shouldn't be a=
ffected by
> > the display clock.
>=20
> 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 12=
0 Hz,
> I could echo 0 or 1 to pp_dpm_mclk. I also got the power meter on now:
>=20
> memory dpm state 0  (150 MHz):  77 watts
> memory dpm state 1 (1250 MHz): 112 watts
>=20
> 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 attachm=
ent 131983 [details] [review].  The driver
disables dynamic mclk switching for refresh rates above 120 hz to avoid
flickering.

You are receiving this mail because:
  • You are the assignee for the bug.
= --14975582669.F663CBF16.28756-- --===============1046860692== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1046860692==--