From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94061] [radeon - Kaveri] dpm works badly - much to high power consumption compared to catalyst
Date: Mon, 09 Mar 2015 13:39:25 +0000 [thread overview]
Message-ID: <bug-94061-2300-h6cWx4erNF@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-94061-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=94061
Alex Deucher <alexdeucher@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexdeucher@gmail.com
--- Comment #5 from Alex Deucher <alexdeucher@gmail.com> ---
You can enable bapm (append radeon.bapm=1 to the kernel command line in grub)
which may help. However, it has caused stability problems on some systems
which is why it is not yet enabled be default. Same goes for some of the clock
and powergating features. See the settings of rdev->cg_flags and
rdev->pg_flags in radeon_asic.c.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-03-09 13:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 12:26 [Bug 94061] New: [radeon - Kaveri] dpm works badly - much to high power consumption compared to catalyst bugzilla-daemon
2015-03-02 7:01 ` [Bug 94061] " bugzilla-daemon
2015-03-02 15:50 ` bugzilla-daemon
2015-03-09 11:39 ` bugzilla-daemon
2015-03-09 11:41 ` bugzilla-daemon
2015-03-09 13:39 ` bugzilla-daemon [this message]
2015-03-09 15:14 ` bugzilla-daemon
2015-04-04 9:17 ` bugzilla-daemon
2015-04-04 17:28 ` bugzilla-daemon
2015-04-04 20:49 ` bugzilla-daemon
2020-12-03 17:49 ` bugzilla-daemon
2020-12-03 18:02 ` bugzilla-daemon
2020-12-03 20:02 ` 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-94061-2300-h6cWx4erNF@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;
as well as URLs for NNTP newsgroup(s).