public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Seifert <lathander-Mmb7MZpHnFY@public.gmane.org>
To: Timo Hoenig <thoenig-dCxI//HcOdFeoWH0uzbU5w@public.gmane.org>
Cc: ML ACPI-devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: clear/enable power button on resume
Date: Sun, 7 Mar 2004 23:43:18 +0100	[thread overview]
Message-ID: <20040307224318.GA1551@ergo.gotdns.org> (raw)
In-Reply-To: <1078689765.541.20.camel-eqrHSpLoP5M@public.gmane.org>

On Sun, Mar 07, 2004 at 09:02:46PM +0100, Timo Hoenig wrote:
> Thanks. But I don't use the power event anyway. As long as acpi works I
> am happy with suspend / resume. rm -rf /etc/acpi/events/powerbtn did it
> for me.

That's what I did, too. On my system, it happens after S3 sleep (I
haven't tested S1/S2). 

And the power button is the only way to power on after S3, since all
other wake-capable devices aren't enabled.

> Isn't the acpi spec telling whether the pressing of the power button
> after suspending has to be reported to the OS?

The ACPI spec says that the pressing of a button (e.g. the power button)
that leads to a wake event is reported differently to the OS. The Notify
value (second column in output of /proc/acpi/event) of a regular button event 
is 0x80, that of a wake event is 0x02. Nevertheless, on my system, 0x80
is generated for a power button wake. Strange.

Sebastian


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  parent reply	other threads:[~2004-03-07 22:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-07 18:52 clear/enable power button on resume Timo Hoenig
     [not found] ` <1078685555.541.9.camel-eqrHSpLoP5M@public.gmane.org>
2004-03-07 19:38   ` Luca Capello
     [not found]     ` <404B7A1B.80006-wlebWZzHoyE@public.gmane.org>
2004-03-07 20:02       ` Timo Hoenig
     [not found]         ` <1078689765.541.20.camel-eqrHSpLoP5M@public.gmane.org>
2004-03-07 22:43           ` Sebastian Seifert [this message]
     [not found]             ` <20040307224318.GA1551-nlVyBo/8EO9N0TnZuCh8vA@public.gmane.org>
2004-03-07 23:27               ` Timo Hoenig

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=20040307224318.GA1551@ergo.gotdns.org \
    --to=lathander-mmb7mzphnfy@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=thoenig-dCxI//HcOdFeoWH0uzbU5w@public.gmane.org \
    /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