From: Daniel Petrini <d.pensator@gmail.com>
To: Todd Poynor <tpoynor@mvista.com>
Cc: cpufreq@lists.linux.org.uk, linux-pm@lists.osdl.org,
linux-kernel@vger.kernel.org,
Geoff Levand <geoffrey.levand@am.sony.com>
Subject: Re: [linux-pm] PowerOP 1/3: PowerOP core
Date: Wed, 10 Aug 2005 09:58:49 -0400 [thread overview]
Message-ID: <9268368b05081006585ca7a415@mail.gmail.com> (raw)
In-Reply-To: <42F94B68.6060107@mvista.com>
> If these general ideas of arbitrary platform power parameters and
> operating points are deemed worthy of continued consideration, I'll
> propose what I view is the next step: interfaces to create and activate
> operating points from userspace.
>
> At that point it should be possible to write power policy management
> applications for systems that can benefit from this generalized notion
> of operating points: create the operating points that match the system
> usage models (in the case of many embedded systems, the system is some
> mode with different power/performance characteristics such as audio
> playback vs. mobile phone call in progress) and power needs (e.g., low
> battery strength vs. high strength) and activate operating points based
> on events received (new app running, low battery warning, etc.).
>
> Any opinions on all that? Thanks,
>
> --
> Todd
Hi,
I'd like to have an idea of how the powerop would evolve to address:
a) exporting all operating points to sysfs - that would be useful for
a policy manager in user space, or the user policy will already be
aware of the ops?
b) Constraints: if I would like to change to a op and such a
transition is not allowed in hardware, what part of the software will
test it? The set/get powerop functions, the higher layers or even some
lower layer (don't know if expected) ?
thanks,
Daniel
--
10LE - Linux
INdT - Manaus - Brazil
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Petrini <d.pensator@gmail.com>
To: Todd Poynor <tpoynor@mvista.com>
Cc: Geoff Levand <geoffrey.levand@am.sony.com>,
cpufreq@lists.linux.org.uk, linux-pm@lists.osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] PowerOP 1/3: PowerOP core
Date: Wed, 10 Aug 2005 09:58:49 -0400 [thread overview]
Message-ID: <9268368b05081006585ca7a415@mail.gmail.com> (raw)
In-Reply-To: <42F94B68.6060107@mvista.com>
> If these general ideas of arbitrary platform power parameters and
> operating points are deemed worthy of continued consideration, I'll
> propose what I view is the next step: interfaces to create and activate
> operating points from userspace.
>
> At that point it should be possible to write power policy management
> applications for systems that can benefit from this generalized notion
> of operating points: create the operating points that match the system
> usage models (in the case of many embedded systems, the system is some
> mode with different power/performance characteristics such as audio
> playback vs. mobile phone call in progress) and power needs (e.g., low
> battery strength vs. high strength) and activate operating points based
> on events received (new app running, low battery warning, etc.).
>
> Any opinions on all that? Thanks,
>
> --
> Todd
Hi,
I'd like to have an idea of how the powerop would evolve to address:
a) exporting all operating points to sysfs - that would be useful for
a policy manager in user space, or the user policy will already be
aware of the ops?
b) Constraints: if I would like to change to a op and such a
transition is not allowed in hardware, what part of the software will
test it? The set/get powerop functions, the higher layers or even some
lower layer (don't know if expected) ?
thanks,
Daniel
--
10LE - Linux
INdT - Manaus - Brazil
next prev parent reply other threads:[~2005-08-10 13:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 2:51 PowerOP 1/3: PowerOP core Todd Poynor
2005-08-09 7:32 ` Greg KH
2005-08-09 7:32 ` Greg KH
2005-08-09 16:07 ` [linux-pm] " Geoff Levand
2005-08-09 16:07 ` Geoff Levand
2005-08-10 0:33 ` Todd Poynor
2005-08-10 0:33 ` [linux-pm] " Todd Poynor
2005-08-10 13:58 ` Daniel Petrini [this message]
2005-08-10 13:58 ` Daniel Petrini
2005-08-11 0:25 ` Todd Poynor
2005-08-11 0:25 ` Todd Poynor
2005-08-12 16:23 ` david-b
2005-08-13 1:06 ` Todd Poynor
2005-08-13 1:06 ` [linux-pm] " Todd Poynor
2005-08-12 16:23 ` david-b
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=9268368b05081006585ca7a415@mail.gmail.com \
--to=d.pensator@gmail.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=geoffrey.levand@am.sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=tpoynor@mvista.com \
/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.