Commit: 7924a3226dbd5b89e8c2ee23a7e0192e799a3496 - system-bt (git)

system/bt

Commit MetaInfo

• Revisão: 7924a3226dbd5b89e8c2ee23a7e0192e799a3496 (tree)
• Hora: 2016-11-08 09:46:50
• Autor: Hashcode <hashcode0f@gmai...>
• Commiter: Ethan Chen

Mensagem de Log

bt: Use HCI H4 HAL for BT SOC ATH3K

The Kindle HDX devices use an Atheros SoC for WIFI/BT and previously used the
H4 HCI driver in the system/bt HAL. However, due to CAF commit:
https://github.com/CyanogenMod/android_system_bt/commit/eb46fdb217ac117b83202d7471199e6042ed18a9

The logic changed from using a BLUETOOTH_HCI_USE_MCT define to instead
looking at BT SOC chip property. Unfortunately, it looks like CAF left
BT_SOC_ATH3K out of the H4 selection check (it's not a common configuration
now in QCOM devices). Adding it to the H4 HAL check fixes bluetooth on
the HDX devices.

Change-Id: Ic8ebfb83627537d71b117dfc83a07e0a1f9f4749
(cherry picked from commit e3044f640516b2e0960e2d20c2211d48738dafdd)

Mudança Sumário

• modified: hci/src/hci_hal.c

Diff

--- a/hci/src/hci_hal.c
+++ b/hci/src/hci_hal.c
@@ -32,7 +32,7 @@ const hci_hal_t *hci_hal_get_interface() {
     soc_type = get_soc_type();
 
     if (soc_type == BT_SOC_ROME || soc_type == BT_SOC_CHEROKEE
-            || soc_type == BT_SOC_DEFAULT) {
+            || soc_type == BT_SOC_AR3K || soc_type == BT_SOC_DEFAULT) {
         return hci_hal_h4_get_interface();
     } else {
         return hci_hal_mct_get_interface();