public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: David Brownell <david-b@pacbell.net>
Cc: linux-pm@lists.osdl.org, Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: RE: on-ness
Date: Mon, 24 Apr 2006 23:32:45 +0200	[thread overview]
Message-ID: <20060424213245.GP3386@elf.ucw.cz> (raw)
In-Reply-To: <200604241404.41122.david-b@pacbell.net>

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

On Po 24-04-06 14:04:40, David Brownell wrote:
> 
> > > > > Uh. Not /sys/power/state. But /sys/devices/...../power/{[a],[b],[c]} where
> > > > > [a], [b] and [c] need sensible names.
> > > > 
> > > > Well, "on" could have one defined meaning.  Maybe it's the only option
> > > > available, until drivers add intelligence.  I don't see any problem
> > > > with the other names being system-specific, since it's rather unlikely
> > > > that a PCI_D3hot state will ever appear on most embedded ARM boxes.
> > > > And if any userspace code tries to set power states, it had darn well
> > > > better understand exactly what's going on.
> > > 
> > > Yes. However if a network managing userspace code wants to set the power
> > > conusmption of a WLAN device to the lowest possible setting, it shouldn't
> > > need a configuration file specific for each platform.
> > 
> > I'd say that "on" and "off" are well defined.
> 
> Are they?  Does "off" imply the device will have been reset the next
> time it goes to "on"?  If not, there would seem to be two "off" states.
> Or maybe more ... PCI_D0 is probably "on", but all of the other PCI
> device states seem to be variants of "off", not of "on".

I'd say "off" is as low as possible, perhaps including device reset.

> And for that matter, "on" doesn't seem to me to imply anything more
> than "full functionality from external POV".  That doesn't necessarily
> imply "full power-on", and in fact it'd be better if it were using the
> lowest power state(s) available.  That state might be compatible with
> certain system sleep states, or not, depending on the device's
> workload.

Agreed.

> > For certain classes (like ethernet), other states may be common
> > between platforms, too, like "off-with-WOL".
> 
> Actually the wakeup characteristics are orthogonal, there are per-device
> bits controlling whether a device can and should do the wakeup.  We don't
> for example treat "PCI_D3hot with wakeup" as a distinct state.

Ok, "off-with-WOL" was example. Hopefully there's better example. 
								Pavel
-- 
Thanks for all the (sleeping) penguins.

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



  reply	other threads:[~2006-04-24 21:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18 18:39 RE: on-ness 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:04                 ` [OT] debugfs and sysfs [Was: Re: RE: on-ness] Dominik Brodowski
2006-04-21 19:01               ` RE: on-ness Pavel Machek
2006-04-24 21:04                 ` David Brownell
2006-04-24 21:32                   ` Pavel Machek [this message]
2006-04-24 23:21                     ` David Brownell
2006-04-21 17:15     ` David Brownell
  -- strict thread matches above, loose matches on Subject: below --
2006-04-21 17:58 Preece Scott-PREECE
2006-04-21 18:15 ` David Brownell
2006-04-24 21:32 Woodruff, Richard
2006-04-27  1:39 ` Patrick Mochel
2006-05-01 21:35 ` David Brownell
2006-04-27 14:12 Scott E. Preece
2006-04-27 17:01 ` Patrick Mochel
2006-05-01 21:58 ` 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=20060424213245.GP3386@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=david-b@pacbell.net \
    --cc=linux-pm@lists.osdl.org \
    --cc=linux@dominikbrodowski.net \
    /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