Messages in this thread | | | Date | Wed, 10 Aug 2005 09:58:49 -0400 | From | Daniel Petrini <> | Subject | Re: [linux-pm] PowerOP 1/3: PowerOP core |
| |
> 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |