All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108613] amdgpu.dc=1 + xf86-video-amdgpu: changing to a GPU upscaling resolution resets pp_dpm_mclk
Date: Wed, 31 Oct 2018 19:57:05 +0000	[thread overview]
Message-ID: <bug-108613-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 108613
           Summary: amdgpu.dc=1 + xf86-video-amdgpu: changing to a GPU
                    upscaling resolution resets pp_dpm_mclk
           Product: DRI
           Version: DRI git
          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

My display doesn't offer upscaling resolutions. However, amdgpu.dc=1 +
xf86-video-amdgpu does.
When I change the resolution from native (2560x1440) to one of those
automatically offered upscaling resolutions (e.g. 1920x1080), the value in
"/sys/class/drm/card0/device/pp_dpm_mclk" gets set to default.

I changed it before like this (to prevent flickering with 75Hz with my
display):

echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_level
echo "2" >  /sys/class/drm/card0/device/pp_dpm_mclk

The VRAM runs with its maximum clock as long as I don't change resolution. When
I change the resolution like described above, the VRAM clock again gets
dynamically changed according to load, which introduces nasty flickering in my
case.

The desired behavior would be that the change done to pp_dpm_mclk remains
untouched when changing to a GPU upscaling resolution.

I haven't checked if pp_dpm_sclk is affected as well. Other
powerplay/overdrive/fan settings remain untouched by resolution change.

Using latest linux-amd-staging-drm-next-wip-git kernel.
Xorg session

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3094 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

             reply	other threads:[~2018-10-31 19:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 19:57 bugzilla-daemon [this message]
2018-11-01 11:22 ` [Bug 108613] amdgpu.dc=1 + xf86-video-amdgpu: changing to a GPU upscaling resolution resets pp_dpm_mclk bugzilla-daemon
2018-11-01 12:19 ` bugzilla-daemon
2018-11-01 12:20 ` bugzilla-daemon
2018-11-01 15:35 ` bugzilla-daemon
2018-11-01 15:37 ` bugzilla-daemon
2018-11-01 21:26 ` bugzilla-daemon
2018-11-01 21:51 ` bugzilla-daemon
2018-11-02 14:06 ` bugzilla-daemon
2018-11-14  5:39 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-108613-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.