From: Florian Echtler <floe@butterbrot.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Corentin Chary <corentin.chary@gmail.com>,
linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: Looking for some pointers on WMI/EC access
Date: Wed, 21 Apr 2010 16:30:06 +0200 [thread overview]
Message-ID: <1271860206.1537.1914.camel@pancake> (raw)
In-Reply-To: <20100421133305.GA28710@srcf.ucam.org>
> Yes, _Q indicates that it's an embedded controller event (_L and _E are
> level or edge triggered events from GPEs). Unless either DSGO or DSSV
> trigger a notification I'd hope that the EC fires some other event after
> the hotkey has been stored.
Thanks - now let me try to sum this up in order to get it straight (I've been
reading the ACPI spec and had to fight sleep really hard :-).
1. EC detects an event (hotkey), raises an SCI.
2. Linux ec.c driver services the SCI, queries the EC for event code.
3. If available, ec.c calls ACPI _Qxx method for received event code.
4. _Qxx method changes some internal state and MAY again call
Notify(...) to pass the event to some other ACPI device.
5. If Notify() was called, second-level ACPI driver (e.g. battery.c,
thermal.c, ...) gets event and handles it accordingly.
If that's correct so far, couldn't I just print the EC event code in
acpi_ec_sync_query and see what it's spitting out on hotkey press?
Florian
--
0666 - Filemode of the Beast
next prev parent reply other threads:[~2010-04-21 14:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 15:37 Looking for some pointers on WMI/EC access Florian Echtler
2010-04-18 19:21 ` Corentin Chary
2010-04-19 14:25 ` Florian Echtler
2010-04-19 15:46 ` Corentin Chary
[not found] ` <1271746353.16585.9.camel@flunder>
2010-04-20 7:21 ` Corentin Chary
2010-04-20 7:30 ` Corentin Chary
2010-04-20 11:21 ` Florian Echtler
2010-04-20 12:09 ` Corentin Chary
2010-04-21 12:46 ` Florian Echtler
2010-04-21 13:33 ` Matthew Garrett
2010-04-21 14:30 ` Florian Echtler [this message]
2010-04-21 14:32 ` Matthew Garrett
2010-04-22 8:21 ` Florian Echtler
2010-04-22 13:36 ` Matthew Garrett
[not found] ` <1271944219.29664.42.camel@pancake.fritz.box>
2010-04-22 13:53 ` Matthew Garrett
2010-04-22 14:05 ` Matthew Garrett
2010-04-23 11:24 ` Florian Echtler
2010-04-23 17:47 ` Matthew Garrett
2010-04-22 14:33 ` Corentin Chary
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=1271860206.1537.1914.camel@pancake \
--to=floe@butterbrot.org \
--cc=corentin.chary@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).