From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 34110] New: 'high' profile does not set the engine and the memory clocks to the max value
Date: Wed, 9 Feb 2011 13:33:28 -0800 (PST) [thread overview]
Message-ID: <bug-34110-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=34110
Summary: 'high' profile does not set the engine and the memory
clocks to the max value
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: darkbasic4@gmail.com
gentoo ~ # power-profile high
Power profile set to HIGH!
gentoo ~ # power-profile status
profile
default
default engine clock: 776000 kHz
current engine clock: 769500 kHz
default memory clock: 1126000 kHz
current memory clock: 1125000 kHz
voltage: 1300 mV
PCIE lanes: 16
gentoo ~ # power-profile low
Power profile set to LOW!
gentoo ~ # power-profile status
profile
low
default engine clock: 776000 kHz
current engine clock: 297000 kHz
default memory clock: 1126000 kHz
current memory clock: 1125000 kHz
voltage: 1258 mV
PCIE lanes: 16
Shouldn't it set the engine to 776000 and the memory to 1126000?
RV670 with R600g, 2.6.38-rc4, xorg-server-1.9.4, mesa git, libdrm git,
xf86-video-ati git, pageflipping on, colortiling on, swapbufferwaits off.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-02-09 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 21:33 bugzilla-daemon [this message]
2011-02-09 22:13 ` [Bug 34110] 'high' profile does not set the engine and the memory clocks to the max value 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-34110-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