Re: [PATCH 3/4] dell-wmi: Add information about other WMI event codes

[Pali RohÃr]

On Tuesday 21 June 2016 19:51:06 Mario_Limonciello@xxxxxxxx wrote:
> > -----Original Message-----
> > From: Pali RohÃr [mailto:pali.rohar@xxxxxxxxx]
> > Sent: Wednesday, June 15, 2016 2:51 PM
> > To: Limonciello, Mario <Mario_Limonciello@xxxxxxxx>
> > Cc: Gabriele Mazzotta <gabriele.mzt@xxxxxxxxx>; mjg59@xxxxxxxxxxxxx;
> > dvhart@xxxxxxxxxxxxx; kernel@xxxxxxxxxx; luto@xxxxxxxxxx;
> > alex.hung@xxxxxxxxxxxxx; platform-driver-x86@xxxxxxxxxxxxxxx; linux-
> > kernel@xxxxxxxxxxxxxxx
> > 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@xxxxxxxx wrote:
> > > >> -----Original Message-----
> > > >> From: Pali RohÃr [mailto:pali.rohar@xxxxxxxxx]
> > > >> Sent: Tuesday, June 7, 2016 6:00 PM
> > > >> To: Gabriele Mazzotta <gabriele.mzt@xxxxxxxxx>; Limonciello, Mario
> > > >> <Mario_Limonciello@xxxxxxxx>
> > > >> Cc: Matthew Garrett <mjg59@xxxxxxxxxxxxx>; Darren Hart
> > > >> <dvhart@xxxxxxxxxxxxx>; MichaÅ KÄpieÅ <kernel@xxxxxxxxxx>; Andy
> > > >> Lutomirski <luto@xxxxxxxxxx>; Alex Hung
> > > >> <alex.hung@xxxxxxxxxxxxx>; platform-driver- x86@xxxxxxxxxxxxxxx;
> > > >> linux-kernel@xxxxxxxxxxxxxxx
> > > >> 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@xxxxxxxxx>
> > > >>>> ---
> > > >>>>
> > > >>>>  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,
> 
> You aren't seeing this on the DSDT of your Latitude right?

Yes, I do not see it on Latitude.

> Gabriele,
> 
> Your machine is from the year before XPS switched over to running
> the Dell business client (eg Latitude, Precision, Optiplex) BIOS.
> 
> The EC in that machine does have support for "Battery Health" via
> that scancode.  On Windows it's used for relaying battery information
> to an application called Quick Set.

Do you have some details when it is send to OS? And how to read that
that "battery health"?

-- 
Pali RohÃr
pali.rohar@xxxxxxxxx