dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 81021] AMD CPUs w/ Integrated Graphics (APUs) And Turbo Core Only Boost If "fglrx" Module Is Loaded
Date: Wed, 30 Jul 2014 13:24:48 +0000	[thread overview]
Message-ID: <bug-81021-2300-ZFY0QidCza@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-81021-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=81021

--- Comment #6 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to LiNuxXer from comment #5)
> 
> This bug report here is about Linux not supporting Turbo Core on APUs when
> no specific graphics driver is used.
> 
> In other words, I'm raising the question whether the kernel should be able
> to suipport the APU Turbo Core even without any specific graphics driver.
> 

Turbo Core (bapm) is controlled by a microcontroller on the APU.  The same
microcontroller also manages the GPU power management.  On most APU systems,
turbo core is enabled by default by the sbios, but apparently on your system
it's not.  Maybe there is a bios option to enable it by default on your system.
 When the GPU driver loads and sets up the GPU power management, it can also
enable or disable bapm.  When bapm and GPU power mangement (dynamic GPU engine
clock and voltage scaling, clock and powergating, etc.) are both enabled, some
systems have stability problems (sudden reboots, hangs, graphical corruption,
issues when switching between AC and battery).

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2014-07-30 13:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-81021-2300@https.bugzilla.kernel.org/>
2014-07-29 15:18 ` [Bug 81021] AMD CPUs w/ Integrated Graphics (APUs) And Turbo Core Only Boost If "fglrx" Module Is Loaded bugzilla-daemon
2014-07-29 15:18 ` bugzilla-daemon
2014-07-29 16:03 ` bugzilla-daemon
2014-07-29 23:35 ` bugzilla-daemon
2014-07-30 12:18 ` bugzilla-daemon
2014-07-30 12:32 ` bugzilla-daemon
2014-07-30 13:24 ` bugzilla-daemon [this message]
2014-08-03 17:34 ` bugzilla-daemon
2014-08-04 14:53 ` bugzilla-daemon
2014-08-07  9:34 ` bugzilla-daemon
2014-08-07  9:43 ` bugzilla-daemon
2014-08-07 13:21 ` bugzilla-daemon
2014-08-07 13:31 ` bugzilla-daemon
2014-08-07 15:17 ` bugzilla-daemon
2014-08-07 15:24 ` 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-81021-2300-ZFY0QidCza@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).