From: Pavel Machek <pavel@suse.cz>
To: David Singleton <dsingleton@mvista.com>
Cc: linux-pm@lists.osdl.org
Subject: Re: Dynanic On-The-Fly Operating points for PowerOP
Date: Tue, 15 Aug 2006 19:44:34 +0000 [thread overview]
Message-ID: <20060815194433.GF4032@ucw.cz> (raw)
In-Reply-To: <44D8D40F.50005@mvista.com>
Hi!
> 2) The naming scheme for operating points has been unified to
> provide a better interface to the PowerOp power manager daemon.
> The names range from:
>
> highest
> high
> medhigh
> medium
> medlow
> low
> lowest
>
> PowerOp maps the supported processor frequencies onto this
> namespace list. The set of centrino processors it supports have
> supported sets of between four and six different operating points.
>
> The PowerOP daemon, coming soon, can simply read the supported
> set of operating points and make some simple rules based
> decisions about when to transition to various operating points.
>
> The goal of a unified name space is to provide a PowerOp manager
> that runs out of the box, with very little setup by the user.
Well, we already have perfectly working API for frequency management,
why not use that?
--
Thanks for all the (sleeping) penguins.
prev parent reply other threads:[~2006-08-15 19:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 18:12 Dynanic On-The-Fly Operating points for PowerOP David Singleton
2006-08-09 21:17 ` Matthew Locke
2006-08-10 4:39 ` david singleton
2006-08-10 7:44 ` Matthew Locke
2006-08-12 8:07 ` Vitaly Wool
2006-08-12 18:12 ` david singleton
2006-08-12 21:32 ` david singleton
2006-08-12 21:39 ` david singleton
2006-08-12 21:40 ` david singleton
2006-08-12 21:41 ` david singleton
2006-08-16 15:02 ` Len Brown
2006-08-12 23:14 ` Matthew Locke
2006-08-13 2:25 ` Preece Scott-PREECE
2006-08-14 3:37 ` david singleton
2006-08-15 19:44 ` Pavel Machek [this message]
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=20060815194433.GF4032@ucw.cz \
--to=pavel@suse.cz \
--cc=dsingleton@mvista.com \
--cc=linux-pm@lists.osdl.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.