From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 111913] AMD Navi10 GPU powerplay issues when using two DisplayPort connectors Date: Sat, 19 Oct 2019 11:24:10 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0607620366==" 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 8CC8D89CF5 for ; Sat, 19 Oct 2019 11:24:10 +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 --===============0607620366== Content-Type: multipart/alternative; boundary="15714842500.cc79D.4135" Content-Transfer-Encoding: 7bit --15714842500.cc79D.4135 Date: Sat, 19 Oct 2019 11:24:10 +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=3D111913 --- Comment #12 from Stefan Rehm --- If I change dcn2_0_soc.dram_clock_change_latency_us in "rivers/gpu/drm/amd/display/dc/dcn20/dcn20_resource.c" from 404.0 to 10.0 (the value used in kernel 5.3) the messages disappear and the system behaves normal again. However, as long as /sys/class/drm/card0/device/power_dpm_force_performance_level is set to "auto", I am now seeing massive flickering. Forcing it to low or = high fixes that. According to the sources for kernel 5.3 the value of 10.0 for dram_clock_change_latency is a hack. Can anyone elaborate on this? --=20 You are receiving this mail because: You are the assignee for the bug.= --15714842500.cc79D.4135 Date: Sat, 19 Oct 2019 11:24:10 +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

Comme= nt # 12 on bug 11191= 3 from = Stefan Rehm 
If I change

dcn2_0_soc.dram_clock_change_latency_us

in "rivers/gpu/drm/amd/display/dc/dcn20/dcn20_resource.c" from 40=
4.0 to 10.0
(the value used in kernel 5.3) the messages disappear and the system behaves
normal again. However, as long as

/sys/class/drm/card0/device/power_dpm_force_performance_level

is set to "auto", I am now seeing massive flickering. Forcing it =
to low or high
fixes that.

According to the sources for kernel 5.3 the value of 10.0 for
dram_clock_change_latency is a hack. Can anyone elaborate on this?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15714842500.cc79D.4135-- --===============0607620366== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0607620366==--