From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99476] Forcing perf level to high doesn't change memory clock
Date: Fri, 20 Jan 2017 15:10:18 +0000 [thread overview]
Message-ID: <bug-99476-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1205 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99476
Bug ID: 99476
Summary: Forcing perf level to high doesn't change memory clock
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: samuel.pitoiset@gmail.com
Hi,
After changing the current performance level with:
echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level
only the shader clock is updated but not the memory clock.
# cat /sys/kernel/debug/dri/0/amdgpu_pm_info
[ mclk ]: 300 MHz
[ sclk ]: 1306 MHz
# cat /sys/class/drm/card0/device/pp_dpm_sclk
0: 300Mhz
1: 608Mhz
2: 910Mhz
3: 1077Mhz
4: 1145Mhz
5: 1191Mhz
6: 1236Mhz
7: 1306Mhz *
# cat /sys/class/drm/card0/device/pp_dpm_mclk
0: 300Mhz *
1: 1750Mhz
Same issue if I choose the manual mode and try to echo 1 in pp_dpm_mclk.
Tested on Linux 4.8 with RX480.
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2510 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
next reply other threads:[~2017-01-20 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 15:10 bugzilla-daemon [this message]
2017-02-09 13:46 ` [Bug 99476] Forcing perf level to high doesn't change memory clock bugzilla-daemon
2017-02-09 17:10 ` bugzilla-daemon
2017-02-10 17:59 ` 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-99476-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).