From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43114] New: Can't set high engine clock for RadeonHD 6620G
Date: Tue, 17 Apr 2012 00:02:48 GMT [thread overview]
Message-ID: <bug-43114-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=43114
Summary: Can't set high engine clock for RadeonHD 6620G
Product: Drivers
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: runetmember@gmail.com
Regression: No
APU model: A8-3500M with Radeon HD 6620G.
Laptop model: Acer Aspire 7560G.
According to official specs of this APU
http://www.amd.com/us/products/notebook/apu/mainstream/Pages/mainstream.aspx#6
https://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units#cite_ref-122
GPU core clock on high profile should be 444 MHz, but even when I set high
profile manually
~# cat /sys/class/drm/card0/device/power_method
profile
~# cat /sys/class/drm/card0/device/power_profile
high
GPU core clock is not 444 MHz anyway, even below 200 MHz:
~$ cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 200000 kHz
current engine clock: 7990 kHz
default memory clock: 667000 kHz
Maybe output of radeon_pm_info is incorrect, because change between different
profiles and dynpm make no difference in radeon_pm_info information.
Reproduceable with Linux 3.2 and Linux 3.4rc3. dmesg of 3.4rc3 boot process
attached. Is there any additional information I need to provide?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2012-04-17 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 0:02 bugzilla-daemon [this message]
2012-04-17 0:03 ` [Bug 43114] Can't set high engine clock for RadeonHD 6620G bugzilla-daemon
2012-04-17 0:03 ` bugzilla-daemon
2012-04-17 0:03 ` bugzilla-daemon
2013-07-04 9:48 ` 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-43114-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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