diff options
| author | Benson Leung <bleung@chromium.org> | 2017-11-22 23:56:39 +0300 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2017-11-27 16:05:31 +0300 |
| commit | 8ee649283b1e542aedba007f6c828d6767c48e0d (patch) | |
| tree | 840050afbe2045b1387206404ddc3414c7900468 /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | cc20c4df1627dd515ea90dd20e2684a8a1c76693 (diff) | |
| download | linux-8ee649283b1e542aedba007f6c828d6767c48e0d.tar.xz | |
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>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions