releases/4.4.173/platform-x86-asus-nb-wmi-drop-mapping-of-0x33-and-0x.patch

   1 From daa5fb744878fbc8b762137268cd668452466486 Mon Sep 17 00:00:00 2001
   2 From: =?UTF-8?q?Jo=C3=A3o=20Paulo=20Rechi=20Vita?= <jprvita@gmail.com>
   3 Date: Wed, 31 Oct 2018 17:21:28 -0700
   4 Subject: platform/x86: asus-nb-wmi: Drop mapping of 0x33 and 0x34 scan codes
   5 MIME-Version: 1.0
   6 Content-Type: text/plain; charset=UTF-8
   7 Content-Transfer-Encoding: 8bit
   8
   9 [ Upstream commit 71b12beaf12f21a53bfe100795d0797f1035b570 ]
  10
  11 According to Asus firmware engineers, the meaning of these codes is only
  12 to notify the OS that the screen brightness has been turned on/off by
  13 the EC. This does not match the meaning of KEY_DISPLAYTOGGLE /
  14 KEY_DISPLAY_OFF, where userspace is expected to change the display
  15 brightness.
  16
  17 Signed-off-by: João Paulo Rechi Vita <jprvita@endlessm.com>
  18 Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
  19 Signed-off-by: Sasha Levin <sashal@kernel.org>
  20 ---
  21  drivers/platform/x86/asus-nb-wmi.c |    2 --
  22  1 file changed, 2 deletions(-)
  23
  24 --- a/drivers/platform/x86/asus-nb-wmi.c
  25 +++ b/drivers/platform/x86/asus-nb-wmi.c
  26 @@ -339,8 +339,6 @@ static const struct key_entry asus_nb_wm
  27         { KE_KEY, 0x30, { KEY_VOLUMEUP } },
  28         { KE_KEY, 0x31, { KEY_VOLUMEDOWN } },
  29         { KE_KEY, 0x32, { KEY_MUTE } },
  30 -       { KE_KEY, 0x33, { KEY_DISPLAYTOGGLE } }, /* LCD on */
  31 -       { KE_KEY, 0x34, { KEY_DISPLAY_OFF } }, /* LCD off */
  32         { KE_KEY, 0x35, { KEY_SCREENLOCK } },
  33         { KE_KEY, 0x40, { KEY_PREVIOUSSONG } },
  34         { KE_KEY, 0x41, { KEY_NEXTSONG } },