All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Information resources
Date: Fri, 25 Feb 2011 18:03:38 -0500	[thread overview]
Message-ID: <4D68354A.2060803@cfl.rr.com> (raw)
In-Reply-To: <AANLkTin6czfh2QvVj7dhxsGLsvZhj-jFVUxdS3LQEirK@mail.gmail.com>

On 02/25/2011 03:38 PM, Alex Deucher wrote:
> The CP firmware has nothing to do with the temperature.  The CP
> firmware is just a packet parser for reading in command buffers and
> programming the register backbone.  Just alike a CPU, the GPU runs at
> whatever speed it's clock is set to.  You can manually force lower
> power states using sysfs.  See the power management section of this
> page:
> http://wiki.x.org/wiki/RadeonFeature

I have tried writing low to power_profile and it seems to make little to 
no difference.  A cpu executing a tight loop busy waiting for something 
to do wastes a lot more power than one that has executed a HLT 
instruction, or used even better stop states to gate off clocks that are 
not needed.  It seems to me that when there is nothing for the GPU to 
do, it also should stop executing instructions and gate off any unneeded 
clocks.

  reply	other threads:[~2011-02-25 23:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 19:50 Information resources Phillip Susi
2011-02-24 23:03 ` Jerome Glisse
2011-02-25 14:38   ` Phillip Susi
2011-02-25 20:03     ` Dave Airlie
2011-02-25 20:42       ` Phillip Susi
2011-02-25 20:56         ` Dave Airlie
2011-02-25 21:12           ` Garry Hurley
2011-02-25 23:09           ` Phillip Susi
2011-02-25 23:19             ` Alex Deucher
2011-02-25 23:30               ` Phillip Susi
2011-02-25 23:50                 ` Alex Deucher
2011-02-25 20:15     ` Garry Hurley Jr.
2011-02-25 20:38     ` Alex Deucher
2011-02-25 23:03       ` Phillip Susi [this message]
2011-02-25 23:06         ` Alex Deucher

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=4D68354A.2060803@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=alexdeucher@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.