From: mike@compulab.co.il (Mike Rapoport)
To: linux-arm-kernel@lists.infradead.org
Subject: Colibri PXA320 Power management question
Date: Mon, 06 Sep 2010 14:06:36 +0300 [thread overview]
Message-ID: <4C84CB3C.2020704@compulab.co.il> (raw)
In-Reply-To: <20100906101320.GD10367@rakim.wolfsonmicro.main>
Mark Brown wrote:
> On Thu, Sep 02, 2010 at 06:43:02PM +0300, Mike Rapoport wrote:
>> Mark Brown wrote:
>
>>> Yes, exactly - what I'm saying is that Linux is set up to use cpufreq
>>> rather than rely on the built in stuff.
>
>> There's no contradiction here. The PXA3XX cpufreq implementation
>> could trigger automatic voltage scaling.
>
> 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.
As far as I remember, PXA3xx power I2C can be setup to automatically send I2C
command sequence to PMIC upon certain events, such as frequency change, power
state transition and probably something else. You can enable this behavior and
then when cpufreq decides to change frequency the voltage should be scaled
appropriately. No idea, though, if anybody made it work.
Maybe Eric had tried it when he was with Marvell :)
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2010-09-06 11:06 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 [this message]
2010-09-06 11:09 ` Eric Miao
2010-09-06 11:30 ` Mark Brown
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=4C84CB3C.2020704@compulab.co.il \
--to=mike@compulab.co.il \
--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 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.