public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mochel <mochel@linux.intel.com>
To: "Scott E. Preece" <preece@motorola.com>
Cc: david-b@pacbell.net, linux-pm@lists.osdl.org, linux@dominikbrodowski.net
Subject: Re: RE: on-ness
Date: Thu, 27 Apr 2006 10:01:15 -0700	[thread overview]
Message-ID: <20060427170115.GB3113@linux.intel.com> (raw)
In-Reply-To: <200604271412.k3RECVA2009467@olwen.urbana.css.mot.com>

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]

On Thu, Apr 27, 2006 at 09:12:31AM -0500, Scott E. Preece wrote:

> So, is the sum of this conversation to this point that it simply isn't
> possible to come up with a set of names and attributes that are
> meaningful across devices? Or might it be possible to map the set of
> special conditions (like the "NoSoftReset" below) to a common vocabulary
> that a device could expose to power management and that a generic,
> cross-platform power management facility could map to system states and
> transitions?

Both. :-)

You can come up with some names and attributes that are common across
devices, and those should be leveraged when possible. But, I don't think
it's possible, or worthwhile, to try to map every device state to a common,
generic (i.e. limited) vocabulary. 

You want drivers to export the states that they know about, in the format
that makes the most to them (e.g. PCI D0-D3), instead of having them 
scratch their head about what to name the states. 

>From that point (when they're exported), it's pretty simple to condense the
vocbulary into something that makes more sense for the platform (like, "on",
"off", "more off", etc).


	Patrick

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2006-04-27 17:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27 14:12 RE: on-ness Scott E. Preece
2006-04-27 17:01 ` Patrick Mochel [this message]
2006-05-01 21:58 ` David Brownell
  -- strict thread matches above, loose matches on Subject: below --
2006-04-24 21:32 Woodruff, Richard
2006-04-27  1:39 ` Patrick Mochel
2006-05-01 21:35 ` David Brownell
2006-04-21 17:58 Preece Scott-PREECE
2006-04-21 18:15 ` David Brownell
2006-04-18 18:39 Brown, Len
2006-04-20 13:25 ` Pavel Machek
2006-04-21 15:27   ` David Brownell
2006-04-21 15:40     ` Dominik Brodowski
2006-04-21 17:03       ` David Brownell
2006-04-21 17:12         ` Dominik Brodowski
2006-04-21 18:30           ` David Brownell
2006-04-21 18:33             ` Dominik Brodowski
2006-04-21 19:00               ` David Brownell
2006-04-21 19:01               ` Pavel Machek
2006-04-24 21:04                 ` David Brownell
2006-04-24 21:32                   ` Pavel Machek
2006-04-24 23:21                     ` David Brownell
2006-04-21 17:15     ` David Brownell

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=20060427170115.GB3113@linux.intel.com \
    --to=mochel@linux.intel.com \
    --cc=david-b@pacbell.net \
    --cc=linux-pm@lists.osdl.org \
    --cc=linux@dominikbrodowski.net \
    --cc=preece@motorola.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox