[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201606152151.07407@pali>
Date: Wed, 15 Jun 2016 21:51:07 +0200
From: Pali Rohár <pali.rohar@...il.com>
To: Mario_Limonciello@...l.com
Cc: Gabriele Mazzotta <gabriele.mzt@...il.com>, mjg59@...f.ucam.org,
dvhart@...radead.org, kernel@...pniu.pl, luto@...nel.org,
alex.hung@...onical.com, platform-driver-x86@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/4] dell-wmi: Add information about other WMI event codes
On Wednesday 08 June 2016 12:44:44 Gabriele Mazzotta wrote:
> On 08/06/2016 08:02, Mario_Limonciello@...l.com wrote:
> >> -----Original Message-----
> >> From: Pali Rohár [mailto:pali.rohar@...il.com]
> >> Sent: Tuesday, June 7, 2016 6:00 PM
> >> To: Gabriele Mazzotta <gabriele.mzt@...il.com>; Limonciello, Mario
> >> <Mario_Limonciello@...l.com>
> >> Cc: Matthew Garrett <mjg59@...f.ucam.org>; Darren Hart
> >> <dvhart@...radead.org>; Michał Kępień <kernel@...pniu.pl>; Andy
> >> Lutomirski <luto@...nel.org>; Alex Hung
> >> <alex.hung@...onical.com>; platform-driver- x86@...r.kernel.org;
> >> linux-kernel@...r.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@...il.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.
Mario, were you able to identify something?
--
Pali Rohár
pali.rohar@...il.com
Download attachment "signature.asc " of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists