From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 52345] KMS Power Management have no effect
Date: Mon, 23 Jul 2012 04:46:19 +0000 [thread overview]
Message-ID: <bug-52345-502-Ex97AaErzA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-52345-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=52345
--- Comment #7 from Grigori Goronzy <greg@chown.ath.cx> 2012-07-22 21:46:19 PDT ---
You might have the same problem as me, see
http://lists.freedesktop.org/archives/dri-devel/2012-July/025159.html
First, the engine clock readout seems to be completely bogus on APUs, disregard
it.
Second, the power management functions limit the maximum engine clock to the
default engine clock. On most standalone GPUs, the default clock seems to be
equivalent to the maximum p-state's clock, so that is fine. Not so much on the
APUs!
I'm interested in what the AtomBIOS PowerPlay table looks like on your device.
Can you boot with drm.debug=6 in the kernel command line and tell me what it
says in the log?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-07-22 21:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 16:30 [Bug 52345] New: KMS Power Management have no effect bugzilla-daemon
2012-07-21 16:43 ` [Bug 52345] " bugzilla-daemon
2012-07-21 23:54 ` bugzilla-daemon
2012-07-22 0:39 ` bugzilla-daemon
2012-07-22 2:13 ` bugzilla-daemon
2012-07-22 22:06 ` bugzilla-daemon
2012-07-22 22:18 ` bugzilla-daemon
2012-07-23 3:26 ` bugzilla-daemon
2012-07-23 4:13 ` bugzilla-daemon
2012-07-23 4:46 ` bugzilla-daemon [this message]
2012-07-23 5:05 ` bugzilla-daemon
2012-07-23 5:08 ` bugzilla-daemon
2019-11-19 8:28 ` 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-52345-502-Ex97AaErzA@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