linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-pm@lists.osdl.org
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	nigel@nigel.suspend2.net,
	"linux-acpi@vger" <linux-acpi@vger.kernel.org>,
	linux-pm@osdl.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: [linux-pm] [PATCH 0/6] [-mm]: ACPI: duplicate ACPI procfs functions in sysfs
Date: Thu, 25 Jan 2007 02:00:25 -0800	[thread overview]
Message-ID: <200701250200.26338.david-b@pacbell.net> (raw)
In-Reply-To: <200701250917.48689.rjw@sisk.pl>

> > > I think we need to make /sys/power/state handle S1.
> > > 
> > > There are two cases
> > > 
> > > 1. Platform supports S1, but does not support S3.
> > > 
> > > This is more common.  You see this a lot on server-class machines.
> > > 
> > > We could make "mem" simply mean S1 here b/c it is effectively
> > > the closest thing to S3.

Today, this system would list "standby" in /sys/power/state,
but not "mem".  I have a system like that here ...


> > > 2. Platform supports both S1 and S3.
> > > 
> > > This is pretty rare -- at least on the systems I've got.
> > > I'd  like the generic interface be able to describe and handle this case.

Today, this system would list both "standby" and "mem"
in /sys/power/state.  I have a system like that here ...


      3. (ACPI) platform supports S3 but not S1

Today, this system would list "mem" in /sys/power/state,
but not "standby".  I have a system like that here ...



> > > I'm open to suggestions on what to call S1 if it isn't called "mem".
> > 
> > 'standby'? That's what occurs to me from previous M$ usage.
> 
> Yes, something like that, I think..

Good news ... it already works that way!!!  :)

- Dave


  reply	other threads:[~2007-01-25 10:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-06 11:35 [PATCH 0/6] [-mm]: ACPI: duplicate ACPI procfs functions in sysfs Zhang Rui
2007-01-06 22:21 ` David Brownell
2007-01-07  5:54   ` [linux-pm] " Matthew Garrett
2007-01-08  3:31     ` David Brownell
2007-01-08 13:10       ` Pavel Machek
2007-01-25  4:14       ` Len Brown
2007-01-25  5:50         ` Matthew Garrett
2007-01-25  9:35         ` David Brownell
2007-01-08 11:40     ` Zhang Rui
2007-01-08 13:13       ` Pavel Machek
2007-01-25  2:28         ` Len Brown
2007-01-25 12:08           ` Pavel Machek
2007-01-25 13:15             ` David Brownell
2007-01-25 19:51               ` Pavel Machek
2007-01-26  1:36                 ` Zhang Rui
2007-01-10 20:53       ` David Brownell
2007-01-25  4:17         ` Len Brown
2007-01-25 13:15           ` Pavel Machek
2007-01-25  3:33     ` [linux-pm] " Len Brown
2007-01-25  3:28   ` Len Brown
2007-01-25  9:54     ` David Brownell
2007-01-25 19:37     ` Pavel Machek
2007-01-07 11:15 ` Pavel Machek
2007-01-25  2:03   ` Len Brown
2007-01-25  2:52     ` Nigel Cunningham
2007-01-25  8:17       ` Rafael J. Wysocki
2007-01-25 10:00         ` David Brownell [this message]
2007-01-18  6:53 ` Zhang Rui
2007-01-21  5:48 ` [PATCH 0/3] " Zhang Rui
2007-01-25  3:50   ` Len Brown

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=200701250200.26338.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=linux-pm@osdl.org \
    --cc=nigel@nigel.suspend2.net \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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;
as well as URLs for NNTP newsgroup(s).