From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105300] amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption with refreshrates >73Hz when DPM changing VRAM clock Date: Wed, 28 Feb 2018 20:28:36 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0941988831==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id B75F16EB4F for ; Wed, 28 Feb 2018 20:28:36 +0000 (UTC) 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 --===============0941988831== Content-Type: multipart/alternative; boundary="15198497160.76814CB.1534" Content-Transfer-Encoding: 7bit --15198497160.76814CB.1534 Date: Wed, 28 Feb 2018 20:28:36 +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=3D105300 Bug ID: 105300 Summary: amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption with refreshrates >73Hz when DPM changing VRAM clock Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: tempel.julian@gmail.com Created attachment 137704 --> https://bugs.freedesktop.org/attachment.cgi?id=3D137704&action=3Dedit edids for 2560x1440 73Hz, 74Hz and 75Hz Hello, I tried out amd-staging-drm-next-git with Linux 4.16 and my DL-DVI 2560x1440 display: Now I finally get a picture and refreshrates below 74Hz seem to work without apparent issues, thanks for fixing the black screen issue! However, when using edid information which contains a resolution with refreshrates higher than 73Hz, I get flickering artifacts on the desktop. T= he issue disappears when I force full clocks via sysfs or use display timings which prevent the VRAM from downclocking. So it seems very likely to me that it's related to downclocking of the VRAM when using higher refreshrates. This is a regression, the old display stack (amdgpu.dc=3D0) works with refreshrates higher than 73Hz and VRAM downclocking at the same time without issues. I attached edid files which can be loaded via drm_kms_helper.edid_firmware = and drm.edid_firmware (they show equal behavior in this case), they use LCD standard timings. Thanks! --=20 You are receiving this mail because: You are the assignee for the bug.= --15198497160.76814CB.1534 Date: Wed, 28 Feb 2018 20:28:36 +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
Bug ID 105300
Summary amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption= with refreshrates >73Hz when DPM changing VRAM clock
Product DRI
Version unspecified
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component DRM/AMDgpu
Assignee dri-devel@lists.freedesktop.org
Reporter tempel.julian@gmail.com

Created =
attachment 137704 [details]
edids for 2560x1440 73Hz, 74Hz and 75Hz

Hello,
I tried out amd-staging-drm-next-git with Linux 4.16 and my DL-DVI 2560x1440
display:
Now I finally get a picture and refreshrates below 74Hz seem to work without
apparent issues, thanks for fixing the black screen issue!

However, when using edid information which contains a resolution with
refreshrates higher than 73Hz, I get flickering artifacts on the desktop. T=
he
issue disappears when I force full clocks via sysfs or use display timings
which prevent the VRAM from downclocking. So it seems very likely to me that
it's related to downclocking of the VRAM when using higher refreshrates.
This is a regression, the old display stack (amdgpu.dc=3D0) works with
refreshrates higher than 73Hz and VRAM downclocking at the same time without
issues.

I attached edid files which can be loaded via drm_kms_helper.edid_firmware =
and
drm.edid_firmware (they show equal behavior in this case), they use LCD
standard timings.

Thanks!


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