[Bug 105300] amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption with refreshrates >73Hz when DPM changing VRAM clock - bugzilla-daemon

From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-105300-502@http.bugs.freedesktop.org/> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1774 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105300

            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=137704&action=edit
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. The
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=0) 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.

[-- Attachment #1.2: Type: text/html, Size: 3274 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel