ASoC: Intel: kbl_rt5663_rt5514_max98927: Map BTN_0 to KEY_PLAYPAUSE
authorBenson Leung <bleung@chromium.org>
Wed, 22 Nov 2017 20:56:39 +0000 (12:56 -0800)
committerMark Brown <broonie@kernel.org>
Mon, 27 Nov 2017 13:05:31 +0000 (13:05 +0000)
commit8ee649283b1e542aedba007f6c828d6767c48e0d
tree840050afbe2045b1387206404ddc3414c7900468
parentcc20c4df1627dd515ea90dd20e2684a8a1c76693
ASoC: Intel: kbl_rt5663_rt5514_max98927: Map BTN_0 to KEY_PLAYPAUSE

The Android 3.5mm Headset jack specification mentions that BTN_0 should
be mapped to KEY_MEDIA, but this is less logical than KEY_PLAYPAUSE,
which has much broader userspace support.

For example, the Chrome OS userspace now supports KEY_PLAYPAUSE to toggle
play/pause of videos and audio, but does not handle KEY_MEDIA.

Furthermore, Android itself now supports KEY_PLAYPAUSE equivalently, as the
new USB headset spec requires KEY_PLAYPAUSE for BTN_0.
https://source.android.com/devices/accessories/headset/usb-headset-spec

Signed-off-by: Benson Leung <bleung@chromium.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
sound/soc/intel/boards/kbl_rt5663_rt5514_max98927.c