From: Matthew Garrett <mjg59@srcf.ucam.org>
To: david@lang.hm
Cc: Pavel Machek <pavel@ucw.cz>,
Arjan van de Ven <arjan@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@lists.linux-foundation.org>
Subject: Re: Power Management framework proposal
Date: Mon, 30 Jul 2007 02:05:20 +0100 [thread overview]
Message-ID: <20070730010520.GC27398@srcf.ucam.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707291456460.15835@asgard.lang.hm>
On Sun, Jul 29, 2007 at 03:00:07PM -0700, david@lang.hm wrote:
> yes it is, and each type of device is growing it's own, incompatible,
> interfaces for controlling things like this. I was aiming to do two
> things.
Anything playing with power management needs to be aware of the
limitations of the hardware. Many devices have reduced functionality
when in reduced power states, and it's vital that the caller be aware of
that. There's no way to express that information in a consistent way
because the limitations vary widely between different types of device.
So, given that software will need to be aware of the different special
cases for different types of hardware, there's very little cost to each
of them exposing a different interface.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2007-07-30 1:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 6:49 Power Management framework proposal david
2007-07-22 7:57 ` [linux-pm] " Igor Stoppa
2007-07-22 8:58 ` david
2007-07-22 12:05 ` Igor Stoppa
2007-07-22 21:21 ` david
2007-07-22 23:09 ` Arjan van de Ven
2007-07-23 2:45 ` david
2007-07-23 3:50 ` Arjan van de Ven
2007-07-23 4:04 ` david
2007-07-23 4:19 ` Arjan van de Ven
2007-07-23 5:25 ` david
2007-07-23 14:12 ` Arjan van de Ven
2007-07-23 18:19 ` david
2007-07-23 8:56 ` Ondrej Zajicek
2007-07-23 17:33 ` david
2007-07-27 12:04 ` Pavel Machek
2007-07-23 10:48 ` Igor Stoppa
2007-07-23 18:14 ` david
2007-07-24 8:43 ` Jerome Glisse
2007-07-24 14:18 ` Igor Stoppa
2007-07-24 20:13 ` david
2007-07-24 20:06 ` david
2007-07-24 23:14 ` Jerome Glisse
2007-07-25 0:40 ` david
2007-07-25 12:49 ` Jerome Glisse
2007-07-29 21:56 ` david
2007-07-22 17:26 ` Arjan van de Ven
2007-07-22 18:56 ` david
2007-07-22 22:27 ` Arjan van de Ven
2007-07-23 3:51 ` david
2007-07-23 4:00 ` Arjan van de Ven
2007-07-23 4:09 ` david
2007-07-27 11:46 ` Pavel Machek
2007-07-29 22:00 ` david
2007-07-30 1:05 ` Matthew Garrett [this message]
2007-07-23 22:23 ` Benjamin Herrenschmidt
2007-07-24 20:14 ` david
2007-07-24 21:38 ` Benjamin Herrenschmidt
2007-07-24 23:02 ` david
2007-07-24 23:47 ` Benjamin Herrenschmidt
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=20070730010520.GC27398@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=arjan@infradead.org \
--cc=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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