Eric, > -----Original Message----- > From: Pali Rohár [mailto:pali.rohar@xxxxxxxxx] > Sent: Sunday, February 4, 2018 6:05 AM > To: Limonciello, Mario <Mario_Limonciello@xxxxxxxx> > Cc: platform-driver-x86@xxxxxxxxxxxxxxx; Eric Light <eric@xxxxxxxxxxxxx> > Subject: dell_wmi: Unknown key on Dell Latitude E6410 > > Hi Mario! > > Eric Light wrote me that on his Dell Latitude E6410 laptop, dell_wmi > prints following messages into dmesg at every boot. > > [ 14.254258] dell_wmi: Unknown key with type 0x0011 and code 0xffd0 pressed > [ 14.254259] dell_wmi: Unknown WMI event type 0x12 > [ 14.487922] dell_wmi: Unknown key with type 0x0011 and code 0xffd1 pressed > [ 15.014983] dell_wmi: Unknown key with type 0x0011 and code 0x01e3 pressed > It almost sounds to me like B2 table is missing entries. Is this a regression after a BIOS update? Or it's always been this way? > Seems that in dell_wmi we are completely missing processing of WMI > events which starts with 0x0012 and then there are some unknown codes > 0xffd0 and 0xffd1. > > Do you have access to documentation what are those code at all? And what > is hidden behind WMI events which starts with 0x0012? > > Also Eric wrote me that pressing brightness up or down key generates > following events: > > Brightness Up: > > [ 1103.717988] dell_wmi: Unknown key with type 0x0011 and code 0xffae pressed > [ 1103.717990] dell_wmi: Unknown key with type 0x0011 and code 0xff81 pressed > > Brightness Down: > > [ 1157.078641] dell_wmi: Unknown key with type 0x0011 and code 0xffac pressed > [ 1157.078644] dell_wmi: Unknown key with type 0x0011 and code 0xff80 pressed > > For me it looks suspicious because why pressing one key generates those > two 0x0011 events and why next one is generated after 2-3s... > > I think the best way is to define all those events in dell_wmi to be > ignored (as I have not heard that brightness does not work), but it > would be a good idea to know we are going to ignore. > > -- > Pali Rohár > pali.rohar@xxxxxxxxx
