linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Colibri PXA320 Power management question
Date: Mon, 6 Sep 2010 12:30:37 +0100	[thread overview]
Message-ID: <20100906113036.GG10367@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <AANLkTin3=pVMpSjtof_mLtMQGL-84qJZMCnfb-0xKfab@mail.gmail.com>

On Mon, Sep 06, 2010 at 07:09:44PM +0800, Eric Miao wrote:
> On Mon, Sep 6, 2010 at 6:13 PM, Mark Brown

> > That'd be slightly entertaining, though, since IIRC the hardware
> > implementation isn't really set up for being constrained - it doesn't
> > expect to be cooperating with software governors.

> It doesn't need to. There is actually an internal command table, and
> not really sure about the mapping scheme though, but when software
> then has only to care about the frequencies, and voltages will be
> adjusted accordingly.

Ah, I'm misremembering the PXA implementation for the i.MX one - the
i.MX version of this feature had a governor rather than just doing a
lookup from the frequency to a voltage.

  reply	other threads:[~2010-09-06 11:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 10:02 Colibri PXA320 Power management question Yuri Ludkevich
2010-08-14  6:53 ` [Openpxa-users] " Marek Vasut
2010-08-15  2:06   ` Eric Miao
2010-08-15  9:13     ` Igor Grinberg
2010-08-15  9:16       ` Eric Miao
2010-09-02 14:22 ` Mark Brown
2010-09-02 14:41   ` Mike Rapoport
2010-09-02 15:27     ` Mark Brown
2010-09-02 15:43       ` Mike Rapoport
2010-09-04  2:31         ` [Openpxa-users] " Marek Vasut
2010-09-06 10:13         ` Mark Brown
2010-09-06 11:06           ` Mike Rapoport
2010-09-06 11:09           ` Eric Miao
2010-09-06 11:30             ` Mark Brown [this message]
2010-09-06 11:42               ` Haojian Zhuang

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=20100906113036.GG10367@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.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).