From: David Brownell <david-b@pacbell.net>
To: linux-pm@lists.osdl.org
Cc: Adam Belay <abelay@novell.com>
Subject: Re: [RFC] A New Power Management API
Date: Sat, 16 Apr 2005 10:27:53 -0700 [thread overview]
Message-ID: <200504161027.53592.david-b@pacbell.net> (raw)
In-Reply-To: <1113533193.3451.40.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Thursday 14 April 2005 7:46 pm, Adam Belay wrote:
> The new API uses a power container/domain model.
I like that as a basic organizing principle, and I don't think
anyone has problems with the notion that the power relationships
can't always map directly to the physical device tree.
Could you describe a bit about how the containers behave? For
example, when a device drops its power consumption, how does it
notify its container? And when sets of devices -- e.g. all USB
devices, all PCI devices -- support the same power states, how
will that code be shared? Would "struct power_device" be the
driver model replacement for "struct power"?
Also, I'd rather see "struct system_power_state *" everywhere
you're now passing "int system_state" in the API.
- Dave
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-04-16 17:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 2:46 [RFC] A New Power Management API Adam Belay
2005-04-15 8:21 ` Benjamin Herrenschmidt
2005-04-15 13:16 ` Daniel Petrini
2005-04-15 18:20 ` Adam Belay
2005-04-16 17:13 ` David Brownell
2005-04-17 20:26 ` Adam Belay
2005-04-15 15:50 ` Jordan Crouse
2005-04-15 18:54 ` Adam Belay
2005-04-16 2:53 ` Todd Poynor
2005-04-16 19:26 ` David Brownell
2005-04-19 3:09 ` Todd Poynor
2005-05-08 19:05 ` David Brownell
2005-04-16 18:24 ` David Brownell
2005-04-17 20:48 ` Adam Belay
2005-04-17 22:29 ` David Brownell
2005-04-17 23:01 ` Adam Belay
2005-04-16 17:27 ` David Brownell [this message]
2005-04-17 20:25 ` Adam Belay
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=200504161027.53592.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=abelay@novell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox