From: Adam Belay <ambx1@neo.rr.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-pm@lists.osdl.org
Subject: Re: [RFC] Some Thoughts on Device Power Management
Date: Wed, 5 Oct 2005 14:39:23 -0400 [thread overview]
Message-ID: <20051005183923.GA5032@neo.rr.com> (raw)
In-Reply-To: <20051005092307.GA22330@elf.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
On Wed, Oct 05, 2005 at 11:23:07AM +0200, Pavel Machek wrote:
> On St 05-10-05 03:52:09, Adam Belay wrote:
> >
> > Hi All,
> >
> > I've been considering strategies for improving runtime power management,
> > selective suspends, and device power management in general. Here are some
> > of my ideas. I would appreciate any comments or suggestions.
>
> If you want to improve power management, write some code, not "yet
> another useless roadmap". Thanks.
> Pavel
Hi Pavel,
This document was more than a roadmap, it makes references to specific
implementation strategies. Nonetheless, you do bring up a good point.
I actually do have some code for many of the ideas I mentioned. I'm
hoping to have a functional example soon.
Thanks,
Adam
>
> PS: Alan wrote some nice pieces for runtime power management, what
> about helping him?
I agree, a notion of power states is a step forward for runtime power
management. I need to look at Alan's code more carefully, but, as I
understand, it's a little different from my proposal.
My intention was to seperate logical driver states (a given level of
functionality) and physical power states. Device drivers are
responsible for manipulating physical device states, but the driver
model manages logical states and their dependencies.
I think comparing these strategies would be a useful discussion.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-10-05 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 7:52 [RFC] Some Thoughts on Device Power Management Adam Belay
2005-10-05 9:23 ` Pavel Machek
2005-10-05 18:39 ` Adam Belay [this message]
2005-10-06 16:55 ` Alan Stern
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=20051005183923.GA5032@neo.rr.com \
--to=ambx1@neo.rr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox