From: Darren Hart <dvhart@infradead.org>
To: "João Paulo Rechi Vita" <jprvita@gmail.com>
Cc: "Lee, Chun-Yi" <jlee@suse.com>,
"Carlos Corbacho" <carlos@strangeworlds.co.uk>,
"Andy Shevchenko" <andy@infradead.org>,
"Platform Driver" <platform-driver-x86@vger.kernel.org>,
linux@endlessm.com,
"João Paulo Rechi Vita" <jprvita@endlessm.com>
Subject: Re: Supporting status LEDs in acer-wmi
Date: Wed, 12 Apr 2017 16:56:32 -0700 [thread overview]
Message-ID: <20170412235632.GB11963@fury> (raw)
In-Reply-To: <CA+A7VXXd5mvMVJCzrz-oecS6jFdD7G4C=TxkEcH_SkxWvNWXiw@mail.gmail.com>
On Tue, Apr 11, 2017 at 03:31:34PM -0400, João Paulo Rechi Vita wrote:
> Hello,
>
> I'm working to support the status LEDs embedded in the "mic mute" and
> "radio toggle" buttons on a Acer TravelMate P648-G2-MG laptop, but
> can't quite get how these are controlled. I have traced the ACPI
> execution from Windows for both buttons, and tried to compare with a
> method tracing on Linux, but couldn't get much out of it.
>
> For the mic mute button, I see _Q45, WMID._WED, WMID.EVBC and
> WMID.CLBC being called on both platforms. For the radios button, I see
> WMID.WMAA and WMID.WSMI on both platforms as well. Only on windows the
> LEDs change status when the buttons are pressed, on Linux the LEDs are
> always on.
>
> I'm attaching the acpidump and the Windows traces, in case you guys
> have any suggestion on what should I try to poke at.
We would need to compare the input buffers used in each case for those WMI
methods. If you can find the MOF data, you may be able to get a better idea of
what those methods are expecting as input. Not something I've done myself, but
there are a few tools out there to extract the MOF data, and you can readily
find tutorials on how to use that data from within Windows.
For example:
http://blog.nietrzeba.pl/2011/12/mof-decompilation.html
--
Darren Hart
VMware Open Source Technology Center
next parent reply other threads:[~2017-04-12 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+A7VXXd5mvMVJCzrz-oecS6jFdD7G4C=TxkEcH_SkxWvNWXiw@mail.gmail.com>
2017-04-12 23:56 ` Darren Hart [this message]
2017-04-14 5:19 ` Supporting status LEDs in acer-wmi joeyli
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=20170412235632.GB11963@fury \
--to=dvhart@infradead.org \
--cc=andy@infradead.org \
--cc=carlos@strangeworlds.co.uk \
--cc=jlee@suse.com \
--cc=jprvita@endlessm.com \
--cc=jprvita@gmail.com \
--cc=linux@endlessm.com \
--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