All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eugeny S. Mints" <eugeny.mints@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: pm list <linux-pm@lists.osdl.org>
Subject: Re: PowerOP, Intro 0/3
Date: Fri, 25 Aug 2006 22:11:59 +0400	[thread overview]
Message-ID: <44EF3D6F.3030802@gmail.com> (raw)
In-Reply-To: <20060826082848.GC8538@elf.ucw.cz>

Pavel Machek wrote:
> Hi!
> 
>> The PowerOP Core provides completely arch independent interface
>> to create and control operating points which consist of arbitrary
>> subset of power parameters available on a certain platform.
>>
>> PowerOP Core upper layer interface provides the following capabilities:
>> - to register an operating point by passing an idenificator of the point
>> represened by a string and arbitrary substet of power paremeters available on a
>> certain platform by a string (parameter name) and value pairs.
>> - to unregister operating point by name
>> - to set operating point by name
>> - to get values of arbitrary subset of platform power parameters associated
>> this  a point (point is passed by name or NULL to get current parameter values
>> from hw)
> 
> I do not think this can work in notebook world, sorry. You'll just get
> way too many operating points.
The only feature for notebook world currently presented in the kernel is 
CPUFreq. CPUFreq PowerOP integration series I sent out for discussion is 
intended to at least provide the same functionality for notebook world as 
current functionality is. Did you glance at this series?

</personal> Pavel,
please stop removing original recipients from either TO: or CC: lists!
please, when you snip original message _do_not_ snip names of replied persons!
</end>
	Eugeny
> Workable solution would be to create power domains, and group devices
> into power domains.
> 								Pavel

  reply	other threads:[~2006-08-25 18:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24  1:08 PowerOP, Intro 0/3 Eugeny S. Mints
2006-08-26  8:28 ` Pavel Machek
2006-08-25 18:11   ` Eugeny S. Mints [this message]
2006-08-26 20:38     ` Pavel Machek
2006-08-27 21:34       ` Eugeny S. Mints
2006-08-28 17:34         ` Pavel Machek
2006-08-28  7:37       ` Matthew Locke
2006-08-28 16:59         ` Preece Scott-PREECE
2006-08-29  7:28           ` Matthew Locke
2006-08-29 15:42             ` David Singleton
2006-10-05  3:26             ` Dominik Brodowski
2006-08-26 13:43   ` Vitaly Wool
2006-08-26 13:55     ` Pavel Machek
2006-08-29 18:56       ` Vitaly Wool

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=44EF3D6F.3030802@gmail.com \
    --to=eugeny.mints@gmail.com \
    --cc=linux-pm@lists.osdl.org \
    --cc=pavel@ucw.cz \
    /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.