From: Len Brown <lenb@kernel.org>
To: corentincj@iksaif.net
Cc: acpi4asus-user@lists.sourceforge.net,
Szymon Olko <szymonolko@o2.pl>,
linux-acpi@vger.kernel.org
Subject: Notify(0x88) (was Re: Asus V1j)
Date: Mon, 26 Mar 2007 00:32:46 -0400 [thread overview]
Message-ID: <200703260032.46355.lenb@kernel.org> (raw)
In-Reply-To: <200703241415.04656.corentincj@iksaif.net>
> > 1. In /proc/acpi/events few keys which looks normal in DSDT are not
> > reported. I found that all of them have code bigger than 0x80. I founded
> > those lines and changed them to return codes below 0x80 (to ones that
> > are not used) and that solved problem. I did not have time to look into
> > acpi source code and maybe my solution is not the best way to do it, and
> > maybe not solves the problem, but works for me.
> > Example:
> >
> > - F2 wifi button
> > //Notify (\_SB.ATKD, 0x88)
> > Notify (\_SB.ATKD, 0x56)
> >
> > The only exception is sleep button F1 but it is notified not to
> > \_SB.ATKD but to \_SB.SLPB and is processed by buttons module.
> >
> > Notify (\_SB.SLPB, 0x80)
> >
> > Is it a bug or a feature that codes over 0x80 are not reported?
> I don't know :/ So, let's ask linux-acpi@vger.kernel.org
According to the ACPI spec, section 5.6.3 "Device Object Notifications"
0-7f common for all devices
80-bf device specific
c0-ff vendor specific
so I think that what happens to codes of 80 and above should
depend on the device driver that is bound to the device
that handles the notify.
I'll venture that SLPB is the sleep button, and the standard button driver
is already bound to handle that one.
-Len
next prev parent reply other threads:[~2007-03-26 4:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46051CEE.4030402@o2.pl>
2007-03-24 13:15 ` Asus V1j Corentin CHARY
2007-03-24 13:46 ` Szymon Olko
2007-03-24 13:47 ` Szymon Olko
2007-03-26 4:32 ` Len Brown [this message]
2007-03-26 19:26 ` Notify(0x88) (was Re: Asus V1j) Szymon Olko
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=200703260032.46355.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentincj@iksaif.net \
--cc=linux-acpi@vger.kernel.org \
--cc=szymonolko@o2.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