From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751875AbdKVU6P (ORCPT ); Wed, 22 Nov 2017 15:58:15 -0500 Received: from mail-io0-f196.google.com ([209.85.223.196]:41551 "EHLO mail-io0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751376AbdKVU4u (ORCPT ); Wed, 22 Nov 2017 15:56:50 -0500 X-Google-Smtp-Source: AGs4zMbaNw/aS9sq2CkFltWrneRzMVk2VwJAF0Jujba/FyLBG2urrj3Y2DYF8Cs/h7TDG8lvizcYRw== From: Benson Leung To: broonie@kernel.org, linux-kernel@vger.kernel.org Cc: harshapriya.n@intel.com, naveen.m@intel.com, srinivas.kandagatla@linaro.org, cychiang@chromium.org, dgreid@chromium.org, anatol.pomozov@gmail.com, bleung@chromium.org, bleung@google.com Subject: [PATCH 0/5] ASoC: Map BTN_0 for Android Headsets to KEY_PLAYPAUSE Date: Wed, 22 Nov 2017 12:56:38 -0800 Message-Id: <20171122205643.99783-1-bleung@chromium.org> X-Mailer: git-send-email 2.15.0.448.gf294e3d99a-goog Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 [PATCH 1/5] ASoC: Intel: kbl_rt5663_rt5514_max98927: Map BTN_0 to [PATCH 2/5] ASoC: Intel: kbl_rt5663_max98927: Map BTN_0 to [PATCH 3/5] ASoC: ts3a227e: Map BTN_0 to KEY_PLAYPAUSE [PATCH 4/5] ASoC: rk3399_gru_sound: Map BTN_0 to KEY_PLAYPAUSE [PATCH 5/5] ASoC: qcom: apq8016-sbc: Map BTN_0 to KEY_PLAYPAUSE