From: Greg Sarjeant <greg-QNIYhHqVzB9kr2E5YSwMOQ@public.gmane.org>
To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: RE: Gateway 200X (again) - No power button events
Date: Tue, 20 Jan 2004 15:28:44 -0500 [thread overview]
Message-ID: <1074630523.3313.17.camel@localhost> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A84702C93238-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
Nate and Andy, thanks for the replies.
On Tue, 2004-01-20 at 15:15, Grover, Andrew wrote:
> > From: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > [mailto:acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of
> > Nate Lawson
> > On Mon, 19 Jan 2004, Greg Sarjeant wrote:
> > > So, it looks like it is specified in the DSDT. I'm not sure
> > why I don't
> > > get an event when I press the button. I do get events from the sleep
> > > button, but the two are declared somewhat differently. Here
>
> > You have no _STA method for PWRB. On FreeBSD, we say hw is
> > always present
> > if there is no _STA method. If it is present, it must return
> > the proper
> > flags for the hw to be used. Perhaps Linux always thinks
> > it's not present
> > if _STA is not there. Note that SLPB returns the proper _STA result.
>
> The ACPI spec in fact says that the absence of _STA implies the device
> is present and functioning. Linux has code for this case, which I am
> assuming (?) works.
>
> In the ASL, you might make sure there are _Qxx methods that call
> Notify() on these respective devices. Also, does dmesg indicate the
> presence of a fixed-feature power button?
>
> Regards -- Andy
>
I had tried adding an _STA method earlier today with no success, but I
may have done something wrong (I just copied the SLPB _STA method).
I think it may be detecting a Fixed Feature power button. Here are the
relevant dmesg lines:
ACPI: Power Button (FF) [PWRF]
ACPI: Lid Switch [LID0]
ACPI: Sleep Button (CM) [SLPB]
ACPI: AC Adapter [ADP1] (on-line)
ACPI: Battery Slot [BAT1] (battery present)
[ACPI Debug] String: Not Support
ACPI: Thermal Zone [THRM] (47 C)
ACPI: Fan [FAN0] (on)
(That "Not Support" is raised by the thermal zone's _SCP Method in the
DSDT. Guess I can't set the cooling policy on this machine).
So, unless the FF cleverly stands for something other than Fixed
Feature, I imagine that that is what I've got. I was just starting to
read up about Fixed vs Control Method Power Buttons, and I am a bit
confused. It seems from the spec that a Fixed Feature Power Button
shouldn't have an implementation in the DSDT. Is that correct, or am I
misreading? I do see methods for the Power button in the DSDT. Here is
the _Q50 method, which is defined in the Embedded Control block:
Method (_Q50, 0, NotSerialized)
{
Notify (PWRB, 0x80)
}
According to the spec, I think that that should trigger the sleep event.
Interestingly, when I added the _STA method to the PWRB device, dmesg
did not report an additional _STA method found. It reports 58 devices
and 58 _STA methods regardless of whether or not I include a _STA
method. Is it disregarding the DSDT device definition because it detects
the fixed feature power button?
I apologize if this is a bit rambly, or if I'm butchering the
terminology. I'm trying to work this out as I go along.
Thanks,
Greg
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-20 20:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 20:15 Gateway 200X (again) - No power button events Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84702C93238-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2004-01-20 20:17 ` Nate Lawson
2004-01-20 20:28 ` Greg Sarjeant [this message]
[not found] ` <1074630523.3313.17.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-01-20 21:17 ` Greg Sarjeant
[not found] ` <1074633425.3317.20.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-01-21 10:23 ` Ducrot Bruno
[not found] ` <20040121102356.GU25416-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-01-21 15:25 ` Greg Sarjeant
-- strict thread matches above, loose matches on Subject: below --
2004-01-21 0:23 Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84702C9323C-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2004-01-24 19:58 ` Greg Sarjeant
2004-01-20 23:27 Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A8470255EFE4-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2004-01-21 0:07 ` Greg Sarjeant
2004-01-19 17:34 Greg Sarjeant
[not found] ` <1074533658.11008.18.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-01-19 19:51 ` Greg Sarjeant
[not found] ` <1074541900.2813.5.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-01-20 15:57 ` Greg Sarjeant
2004-01-20 20:03 ` Nate Lawson
[not found] ` <20040120120211.U96919-Y6VGUYTwhu0@public.gmane.org>
2004-01-21 10:11 ` Ducrot Bruno
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=1074630523.3313.17.camel@localhost \
--to=greg-qniyhhqvzb9kr2e5yswmoq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=nate-Y6VGUYTwhu0@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