From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752537AbcFVOMz (ORCPT ); Wed, 22 Jun 2016 10:12:55 -0400 Received: from mail-wm0-f42.google.com ([74.125.82.42]:36825 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750910AbcFVOMy (ORCPT ); Wed, 22 Jun 2016 10:12:54 -0400 Date: Wed, 22 Jun 2016 16:12:39 +0200 From: Pali =?utf-8?B?Um9ow6Fy?= To: Mario_Limonciello@Dell.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 Message-ID: <20160622141239.GG29844@pali> 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> <20160622075602.GA29844@pali> <41f11bb2917349919e0b4eb21fab9a46@ausx13mpc124.AMER.DELL.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <41f11bb2917349919e0b4eb21fab9a46@ausx13mpc124.AMER.DELL.COM> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 22 June 2016 13:40:57 Mario_Limonciello@Dell.com wrote: > > > 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. So event is sent only if battery is removed or inserted? > 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. Great! Can I send patch after which 0xe00e will be send to input layer as event KEY_BATTERY? -- Pali Rohár pali.rohar@gmail.com