On Wednesday 22 June 2016 13:40:57 Mario_Limonciello@xxxxxxxx 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@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
