diff options
| author | Mac Chiang <mac.chiang@intel.com> | 2019-05-02 14:12:04 +0800 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2019-05-03 15:37:09 +0900 |
| commit | 16ec5dfe0327ddcf279957bffe4c8fe527088c63 (patch) | |
| tree | 9fed35b19ca033655f7b3b2d49adde9db1ffd8a2 /sound/soc/fsl/eukrea-tlv320.c | |
| parent | f70abd75b7c6c04d3219d0b3a0f3f15411b042fb (diff) | |
| download | linux-16ec5dfe0327ddcf279957bffe4c8fe527088c63.tar.bz2 | |
ASoC: Intel: kbl_da7219_max98357a: Map BTN_0 to KEY_PLAYPAUSE
On kbl_rt5663_max98927, commit 38a5882e4292
("ASoC: Intel: kbl_rt5663_max98927: Map BTN_0 to KEY_PLAYPAUSE")
This key pair mapping to play/pause when playing Youtube
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
The same fix is required on Chrome kbl_da7219_max98357a.
Signed-off-by: Mac Chiang <mac.chiang@intel.com>
Reviewed-by: Benson Leung <bleung@chromium.org>
Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'sound/soc/fsl/eukrea-tlv320.c')
0 files changed, 0 insertions, 0 deletions