From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96487] Cannot force power_dpm_force_performance_level to high
Date: Fri, 10 Jun 2016 22:36:16 +0000 [thread overview]
Message-ID: <bug-96487-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3200 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96487
Bug ID: 96487
Summary: Cannot force power_dpm_force_performance_level to high
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: ltjbour@gmail.com
Created attachment 124464
--> https://bugs.freedesktop.org/attachment.cgi?id=124464&action=edit
Information about the supported gpu states
Linux 4.6.2-1-ARCH #1 SMP PREEMPT Wed Jun 8 08:40:59 CEST 2016 x86_64 GNU/Linux
I thought my problem was perhaps a duplicate of
https://bugs.freedesktop.org/show_bug.cgi?id=70654 but I'm pretty sure that
this isn't the same problem. The problem I'm having is that I can't set the
highest frequency state from my gpu (AMD A8-4500M APU + HD 7640G), in a
consistent and persistent way. And this is regardless of whether uvd is enabled
or not (as I assume this is enabled automatically and I haven't been running
any application that requires it)
In other words I would like to be able to set the dpm level to 'high' so that
it stays in the higher frequency state, but I can't set the
power_dpm_force_performance variable to anything other than 'auto' and 'low'. I
get the following output:
λ echo high | sudo tee
/sys/class/drm/card0/device/power_dpm_force_performance_level
high
tee: /sys/class/drm/card0/device/power_dpm_force_performance_level: Invalid
argument
It turns out that after some testing, I have noticed that it's more stable to
set 'performance' dpm state and force it to 'low', which leaves the GPU
frequency at ~335MHz, than setting it to auto which makes the frequencies jump
between modes [335/490/655]MHz depending on the load. I would obviously like to
be able to set a single mode and have a constant frequency. If I can set 655MHz
permanently that would be ideal.
I've already tried using 'dynpm' and 'profile' modes, but they don't work. I
tried a bunch of times, even enabled/disabled some radeon parameters to see if
they were somehow conflicting but I wasn't able to succesfully change states a
single time. It would permanently stay at 200MHz with either of these two
profile modes set. That left me with the single choice of using 'dpm', as it
was the only mode that was able to at least change the states.
I was told in IRC that the reason I couldn't set the 'high' value permanently
was due to a hardware limitation of Trinity chips. I don't see how this can
possibly be true as I can get this same GPU to be consistently at its highest
frequency state in Windows 8. So if anything this is a limitation of the
driver?
I've attached the kernel info about the available states, the list of radeon
parameters and their values in my system, and the output of /proc/cpuinfo. As
of now I don't know what else to add so feel free to ask for any additional
information, I'll make it available as soon as I can.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4898 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:[~2016-06-10 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 22:36 bugzilla-daemon [this message]
2016-06-10 22:37 ` [Bug 96487] Cannot force power_dpm_force_performance_level to high bugzilla-daemon
2016-06-10 22:38 ` bugzilla-daemon
2016-06-10 22:48 ` bugzilla-daemon
2016-06-10 23:52 ` bugzilla-daemon
2016-06-11 1:28 ` bugzilla-daemon
2016-06-13 16:08 ` bugzilla-daemon
2019-11-19 9:17 ` 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-96487-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.