From: Gabriele Mazzotta <gabriele.mzt@gmail.com>
To: Mario_Limonciello@Dell.com, pali.rohar@gmail.com
Cc: mjg59@srcf.ucam.org, dvhart@infradead.org, kernel@kempniu.pl,
luto@kernel.org, alex.hung@canonical.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] dell-wmi: Add information about other WMI event codes
Date: Wed, 8 Jun 2016 12:44:44 +0200 [thread overview]
Message-ID: <0d5a8762-b849-41c6-bfe5-e00da25d26d5@gmail.com> (raw)
In-Reply-To: <01b8e172bca546728b596c8cc4ebd932@ausx13mpc124.AMER.DELL.COM>
On 08/06/2016 08:02, Mario_Limonciello@Dell.com wrote:
>> -----Original Message-----
>> From: Pali Rohár [mailto:pali.rohar@gmail.com]
>> Sent: Tuesday, June 7, 2016 6:00 PM
>> To: Gabriele Mazzotta <gabriele.mzt@gmail.com>; Limonciello, Mario
>> <Mario_Limonciello@Dell.com>
>> Cc: Matthew Garrett <mjg59@srcf.ucam.org>; Darren Hart
>> <dvhart@infradead.org>; Michał Kępień <kernel@kempniu.pl>; Andy Lutomirski
>> <luto@kernel.org>; Alex Hung <alex.hung@canonical.com>; platform-driver-
>> x86@vger.kernel.org; linux-kernel@vger.kernel.org
>> Subject: Re: [PATCH 3/4] dell-wmi: Add information about other WMI event
>> codes
>>
>> On Friday 27 May 2016 00:04:23 Gabriele Mazzotta wrote:
>>> On 22/05/2016 13:36, Pali Rohár wrote:
>>>> ACPI DSDT tables have defined other WMI codes, but does not contain
>>>> any description when those codes are emitted. Some other codes can
>>>> be found in logs on internet. In this patch are all which I saw, but
>>>> lot of them are not tested properly (e.g. for duplicate events with
>>>> AT keyboard). Now we have all WMI event codes at one place and in
>>>> future after proper testing those codes can be correctly enabled or
>> disabled...
>>>>
>>>> Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
>>>> ---
>>>> drivers/platform/x86/dell-wmi.c | 32
>> ++++++++++++++++++++++++++++++++
>>>> 1 file changed, 32 insertions(+)
>>>>
>>>> diff --git a/drivers/platform/x86/dell-wmi.c
>>>> b/drivers/platform/x86/dell-wmi.c index 363d927..7aac1dc 100644
>>>> --- a/drivers/platform/x86/dell-wmi.c
>>>> +++ b/drivers/platform/x86/dell-wmi.c
>>>> @@ -110,6 +110,9 @@ static const struct key_entry
>> dell_wmi_legacy_keymap[] __initconst = {
>>>> /* BIOS error detected */
>>>> { KE_IGNORE, 0xe00d, { KEY_RESERVED } },
>>>>
>>>> + /* Unknown, defined in ACPI DSDT */
>>>> + /* { KE_IGNORE, 0xe00e, { KEY_RESERVED } }, */
>>>> +
>>>
>>> I'm interested in knowing what's the meaning of this 0xe00e. This
>>> event is sent multiple times when I suspend/resume my laptop and it's
>>> definitely not a keypress.
>>
>> From DSDT dumps which I have seen, I guess it could be something with battery
>> charging... but that is only my guess.
>>
>> Mario, do you have any idea, what these unknown events are?
>
> Off-hand I'm not sure, it would require some more digging.
>
> Can you please remind me what model numbers and BIOS combinations you have
> found e00e in DSDT and what context the events are actually happening?
> Anything released in the past two years?
>
XPS13 9333, BIOS A07.
I think I saw the event only after resuming from suspend and
it's sent four times in a row.
As Pali says, it seems to be related to the battery. There are
three _Qxx ACPI methods in my DSDT sending this event: one stops
battery charging, one detaches the battery and the last one stores
a value on the GNVS.
next prev parent reply other threads:[~2016-06-08 10:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 11:36 [PATCH 0/4] dell-wmi: Changes in WMI event code handling Pali Rohár
2016-05-22 11:36 ` [PATCH 1/4] dell-wmi: Ignore WMI event code 0xe045 Pali Rohár
2016-05-22 11:36 ` [PATCH 2/4] dell-wmi: Sort WMI event codes and update comments Pali Rohár
2016-06-02 10:41 ` Michał Kępień
2016-06-07 22:03 ` Pali Rohár
2016-06-08 19:48 ` Darren Hart
2016-06-08 19:57 ` Pali Rohár
2016-06-08 20:15 ` Darren Hart
2016-06-08 20:27 ` Pali Rohár
2016-06-08 20:43 ` Darren Hart
2016-06-08 20:49 ` Pali Rohár
2016-05-22 11:36 ` [PATCH 3/4] dell-wmi: Add information about other WMI event codes Pali Rohár
2016-05-26 22:04 ` Gabriele Mazzotta
2016-06-07 23:00 ` Pali Rohár
2016-06-08 6:02 ` Mario_Limonciello
2016-06-08 10:44 ` Gabriele Mazzotta [this message]
2016-06-15 19:51 ` Pali Rohár
2016-06-21 19:51 ` Mario_Limonciello
2016-06-22 7:56 ` Pali Rohár
2016-06-22 13:40 ` Mario_Limonciello
2016-06-22 14:12 ` Pali Rohár
2016-06-22 14:21 ` Mario_Limonciello
2016-06-22 14:24 ` Pali Rohár
2016-06-22 14:28 ` Mario_Limonciello
2016-06-22 14:31 ` Pali Rohár
2016-06-22 14:34 ` Mario_Limonciello
2016-06-22 14:38 ` Pali Rohár
2016-06-22 14:39 ` Gabriele Mazzotta
2016-06-22 14:46 ` Mario_Limonciello
2016-06-02 10:41 ` Michał Kępień
2016-06-07 22:06 ` Pali Rohár
2016-05-22 11:36 ` [PATCH 4/4] dell-wmi: Rework code for generating sparse keymap and processing WMI events Pali Rohár
2016-05-23 17:07 ` Andy Lutomirski
2016-06-02 10:42 ` Michał Kępień
2016-06-07 22:30 ` Pali Rohár
2016-06-02 10:52 ` [PATCH 0/4] dell-wmi: Changes in WMI event code handling Michał Kępień
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=0d5a8762-b849-41c6-bfe5-e00da25d26d5@gmail.com \
--to=gabriele.mzt@gmail.com \
--cc=Mario_Limonciello@Dell.com \
--cc=alex.hung@canonical.com \
--cc=dvhart@infradead.org \
--cc=kernel@kempniu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pali.rohar@gmail.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