diff options
| author | Hashcode <hashcode0f@gmail.com> | 2016-11-07 16:33:26 -0800 |
|---|---|---|
| committer | Michael Bestas <mikeioannina@gmail.com> | 2017-01-02 01:03:18 +0200 |
| commit | 1aa05753dfa52cea2d173739a0ce165cf9909a01 (patch) | |
| tree | f26b3463e55c2a15ad98e39fcf823e40664bb753 | |
| parent | aa4939b4e214cd4e3406d590e5a9b8ada8f74ed3 (diff) | |
| download | android_system_bt-1aa05753dfa52cea2d173739a0ce165cf9909a01.tar.gz android_system_bt-1aa05753dfa52cea2d173739a0ce165cf9909a01.tar.bz2 android_system_bt-1aa05753dfa52cea2d173739a0ce165cf9909a01.zip | |
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)
| -rw-r--r-- | hci/src/hci_hal.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/hci/src/hci_hal.c b/hci/src/hci_hal.c index f2b48153f..ace622e95 100644 --- 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(); |