public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Tehn Yit Chin <tehn-yit.chin@greyinnovation.com>
Cc: Li Qiang-E3422C <E3422C@motorola.com>, linux-pm@lists.osdl.org
Subject: Re: apm for individual devices
Date: Thu, 9 Mar 2006 02:55:18 +0100	[thread overview]
Message-ID: <20060309015518.GE2084@elf.ucw.cz> (raw)
In-Reply-To: <440F8B96.5080802@greyinnovation.com>

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

On Čt 09-03-06 12:57:42, Tehn Yit Chin wrote:
> Pavel Machek wrote:
> >On Út 07-03-06 10:11:31, Li Qiang-E3422C wrote:
> >
> >>'0' indicates the device is on. Other values (1-3) indicate the device
> >>is in a low power state. 
> >>You can see ACPI's spec.
> >
> >
> >Actually, no. This is broken interface, please do not use it. 0 == on,
> >2 or 3 == off. But do not use it.
> 
> Are you saying not to the the power/state that is present in the 
> device's sysfs entry? What interface do you recommend that I use?

Parse error. But I'm trying to say that <device>/power/state should
not be used -- it is ugly/broken. Replacement interface is being
prepared by Patrick, I believe, but is not yet in mainline. Feel free
to help Patrick :-).

								Pavel
-- 
Web maintainer for suspend.sf.net (www.sf.net/projects/suspend) wanted...

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



  reply	other threads:[~2006-03-09  1:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07  2:11 apm for individual devices Li Qiang-E3422C
2006-03-08 15:51 ` Pavel Machek
2006-03-09  1:57   ` Tehn Yit Chin
2006-03-09  1:55     ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-07  0:44 Tehn Yit Chin
2006-03-07  1:30 ` Tehn Yit Chin
2006-03-07  2:58   ` Patrick Mochel
2006-03-08 15:50   ` Pavel Machek
2006-03-07  3:50 ` Adam Belay
2006-03-07  4:06   ` Tehn Yit Chin

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=20060309015518.GE2084@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=E3422C@motorola.com \
    --cc=linux-pm@lists.osdl.org \
    --cc=tehn-yit.chin@greyinnovation.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