All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Jean Pihet <jpihet@mvista.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: PM branch updated
Date: Fri, 07 Aug 2009 10:11:20 -0700	[thread overview]
Message-ID: <87ws5f35xj.fsf@deeprootsystems.com> (raw)
In-Reply-To: <200908071029.30047.jpihet@mvista.com> (Jean Pihet's message of "Fri\, 7 Aug 2009 10\:29\:29 +0200")

Jean Pihet <jpihet@mvista.com> writes:

> On Thursday 06 August 2009 19:13:06 Kevin Hilman wrote:
>> Kevin Hilman wrote:
>> > I just pushed an updated PM branch which was rebased to current
>> > omap/master (which is based on v2.6.31-rc5)
>>
>> Also, please check out
>>
>>    http://elinux.org/OMAP_Power_Management
>>
>> This page includes the stuff I normally put in the announcment of a new
>> PM branch, but also tries to describe how to use the various features of
>> the PM branch (which has been sorely missing for a while.)
>
> I think this page had been long-awaited. Thanks a lot for putting it
> together.
>
> One question about it:
>
> What about the cpufreq interface for doing DVFS? Is it preferred way
> to change OPPs or is it using /sys/power/vddx_opp? I think cpufreq
> utils are more standard, easier to use and to understand.

CPUfreq is much preferred.  The /sys/power/vdd* are just for manual
testing and more fore PM developers than PM users.

Hey, sounds like a perfect opportunity for you to update the wiki. ;)

Kevin

  reply	other threads:[~2009-08-07 17:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06  1:14 PM branch updated Kevin Hilman
2009-08-06 11:22 ` Roger Quadros
2009-08-06 17:13 ` Kevin Hilman
2009-08-07  8:29   ` Jean Pihet
2009-08-07 17:11     ` Kevin Hilman [this message]
2009-08-10  8:26       ` Jean Pihet
  -- strict thread matches above, loose matches on Subject: below --
2009-08-23 21:40 Kevin Hilman
2009-07-01  1:31 Kevin Hilman

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=87ws5f35xj.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=jpihet@mvista.com \
    --cc=linux-omap@vger.kernel.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.