diff options
| author | Benson Leung <bleung@chromium.org> | 2017-11-22 12:56:42 -0800 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2017-11-27 13:01:57 +0000 |
| commit | af1b1cefd735c919d3185ce06b549c2b121067ba (patch) | |
| tree | 54df48edbc2515b6d2b5ac07f2695d9a17e543c8 /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | c20c6704bf2dafaba0d90c8310ef9e919fe4d2e2 (diff) | |
ASoC: rk3399_gru_sound: 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/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions