From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752495AbcFVNlc (ORCPT <rfc822;w@1wt.eu>);
	Wed, 22 Jun 2016 09:41:32 -0400
Received: from ausc60ps301.us.dell.com ([143.166.148.206]:28271 "EHLO
	ausc60ps301.us.dell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751543AbcFVNlV (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 22 Jun 2016 09:41:21 -0400
DomainKey-Signature: s=smtpout; d=dell.com; c=nofws; q=dns;
  h=X-LoopCount0:X-IronPort-AV:From:To:CC:Subject:
   Thread-Topic:Thread-Index:Date:Message-ID:References:
   In-Reply-To:Accept-Language:Content-Language:
   X-MS-Has-Attach:X-MS-TNEF-Correlator:
   x-ms-exchange-transport-fromentityheader:x-originating-ip:
   Content-Type:Content-Transfer-Encoding:MIME-Version:
   Return-Path;
  b=rjU7XSrk40jsoJnbLJ4uWyg1iwDmHJFaBK6q3Bjp/2eBkCLdFGnwF+cK
   F/WVzw2kCpdyxJ3SF3BjDO2lx4v+Lvmb2HF9mk1UTu3Tx1La7JJKTkZgU
   7GUj5LS3LWbZR8Mv5DZttrzLFWgGLmnnhKESvZq1m/64WOTEiIjoJEndC
   o=;
X-LoopCount0: from 10.170.28.39
X-IronPort-AV: E=Sophos;i="5.26,509,1459832400"; 
   d="scan'208";a="837789283"
From: <Mario_Limonciello@Dell.com>
To: <pali.rohar@gmail.com>
CC: <gabriele.mzt@gmail.com>, <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
Thread-Topic: [PATCH 3/4] dell-wmi: Add information about other WMI event
 codes
Thread-Index: AQHRtB42hzf3HHxGtEu99Pj4tlzQap/MILSAgBLrjQCAACDR8IAApAwAgAuY+oCACRdL8IABITwAgAAJTLA=
Date: Wed, 22 Jun 2016 13:40:57 +0000
Message-ID: <41f11bb2917349919e0b4eb21fab9a46@ausx13mpc124.AMER.DELL.COM>
References: <1463916983-12562-1-git-send-email-pali.rohar@gmail.com>
 <01b8e172bca546728b596c8cc4ebd932@ausx13mpc124.AMER.DELL.COM>
 <0d5a8762-b849-41c6-bfe5-e00da25d26d5@gmail.com> <201606152151.07407@pali>
 <efa30ea0242d4d2fa1b1f594b2e238c5@ausx13mpc120.AMER.DELL.COM>
 <20160622075602.GA29844@pali>
In-Reply-To: <20160622075602.GA29844@pali>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.132.208.210]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id u5MDfZDE010059

> > You aren't seeing this on the DSDT of your Latitude right?
> 
> Yes, I do not see it on Latitude.

Thanks, the usage of this scan code is specific to consumer BIOSes.

> 
> > 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"?

When a battery is removed or inserted this event is supposed to be received
by quickset over WMI and then Quickset will re-read battery information.

For Linux I don’t think this is necessary and a NOOP is appropriate.

There is also a second place that some older laptops had a battery "hotkey"
that would also emit 0xE00E.  This was also picked up by quickset and would
show battery information.

This shouldn't be blocked by kernel, I'd expect if someone wants to bind this
to another application from userspace they should be able to.