aboutsummaryrefslogtreecommitdiffstats
path: root/sound
diff options
context:
space:
mode:
authorAyman Bagabas <ayman.bagabas@gmail.com>2018-12-12 18:07:58 -0500
committerTakashi Iwai <tiwai@suse.de>2018-12-13 09:23:27 +0100
commitbf4fb28c6e74495de9e1e4ad359cd2272ac12c53 (patch)
treeb6855511ddbc1e5d6d54ad7585cb3ffcc4e2f708 /sound
parentALSA: hda: fix front speakers on Huawei MBXP (diff)
downloadlinux-dev-bf4fb28c6e74495de9e1e4ad359cd2272ac12c53.tar.xz
linux-dev-bf4fb28c6e74495de9e1e4ad359cd2272ac12c53.zip
platform/x86: add support for Huawei WMI hotkeys
This driver adds support for missing hotkeys on some Huawei laptops. Laptops such as the Matebook X have non functioning hotkeys. Whereas newer laptops such as the Matebook X Pro come with working hotkeys out of the box. Old laptops, such as the Matebook X, report hotkey events through ACPI device "\WMI0". However, new laptops, such as the Matebook X Pro, does not have this WMI device. All the hotkeys on the Matebook X Pro work fine without this patch except (micmute, wlan, and huawei key). These keys and the brightness keys report events to "\AMW0" ACPI device. One problem is that brightness keys on the Matebook X Pro work without this patch. This results in reporting two brightness key press events one is captured by ACPI and another by this driver. A solution would be to check if such event came from the "\AMW0" WMI driver then skip reporting event. Another solution would be to leave this to user-space to handle. Which can be achieved by using "hwdb" tables and remap those keys to "unknown". This solution seems more natural to me because it leaves the decision to user-space. Acked-by: Andy Shevchenko <andy.shevchenko@gmail.com> Reviewed-by: Takashi Iwai <tiwai@suse.de> Signed-off-by: Ayman Bagabas <ayman.bagabas@gmail.com> Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'sound')
0 files changed, 0 insertions, 0 deletions