From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [Openpxa-users] Colibri PXA320 Power management question
Date: Sat, 4 Sep 2010 04:31:49 +0200 [thread overview]
Message-ID: <201009040431.49798.marek.vasut@gmail.com> (raw)
In-Reply-To: <4C7FC606.20904@compulab.co.il>
Dne ?t 2. z??? 2010 17:43:02 Mike Rapoport napsal(a):
> Mark Brown wrote:
> > On Thu, Sep 02, 2010 at 05:41:57PM +0300, Mike Rapoport wrote:
> >> Mark Brown wrote:
> >>> The expectation in Linux is that voltage scaling will be done in
> >>> software using cpufreq rather than autonomously by the CPU.
> >>
> >> PXA3xx has ability to automatically control certain regulators
> >> (almost) without software intervention. Setting the bits Yuri is
> >> talking about should enable CPU initiated i2c transactions upon
> >> frequency scaling events.
> >
> > 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.
Considering the CPU and the regulator are compatible and you wont fry the CPU.
In that case, you use cpufreq indeed.
next prev parent reply other threads:[~2010-09-04 2:31 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 ` Marek Vasut [this message]
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
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=201009040431.49798.marek.vasut@gmail.com \
--to=marek.vasut@gmail.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 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.