Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Benson Leung <bleung@chromium.org>
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>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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

From 1585257044325120275@xxx Mon Nov 27 21:42:08 +0000 2017
X-GM-THRID: 1585257044325120275
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread