| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I47d7d59c49d06149cbf27e0ac570188b451197f8
Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
|
|
|
|
|
|
|
|
| |
First release under Apache source license with updated header files
and whitespace cleanups. Also fixed file permission to remove executable
bit from source files.
Change-Id: I7155903edfc2f491c1cbbd0db108f207852caaa0
|
|
|
|
|
|
|
|
| |
This reverts commit cc914cffd521b2e6e1be804c82aea2388b843ebf
More changes in the original CL after my cherry-pick.
Change-Id: Ic144dba96aeb8a60611baac7565c9f628ab8f9eb
|
|
|
|
|
|
|
| |
Also fixed file permission to remove executable bit
from source files.
Change-Id: I6954c2d16190bc35b1b0d38386543253696b1112
|
|
|
|
|
|
|
|
|
|
|
|
| |
From time to time, we had seen some GKI_exception error messages showing up
in adb log during turning BT off. Those were triggered by a HCI event which
arrived after BTU task had been terminated. The early termination of BTU task
had also become a contributing factor to the BT-OFF hung issue.
Revise the termination sequence between BTU and HCI/Vendor tasks to address
the issues.
Change-Id: I094104943275b3b1fb95aef514936e28394615eb
|
|
|
|
|
|
| |
While enabling BT, Do not toggle the chip power if the target is wingray.
Change-Id: If044361d51354cfd3695d84895dada4342ef28c8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
external/bluetooth/bluedroid).
1. Split the original external/bluetooth/bluedroid/vendor directory to two parts: external/bluetooth/bluedroid/hci and vendor/broadcom/libbt-vendor. Each part produces a .so library (libbt-hci.so and libbt-vendor.so).
2. libbt-hci.so contains:
+ HCI H4 send & receive functions
+ Userial read & write functions
+ LPM common logic operations
+ btsnoop functions.
3. No build-time (.txt) and run-time (.conf) configuration for libbt-hci.so.
4. libbt-vendor.so contains:
+ firmware patch download function
+ SCO configuration
+ LPM VSC and BT_WAKE control
+ UART port open
+ upio control for BT chip power on/off.
5. libbt-vendor.so has build-time and run-time configuration support.
Change-Id: I61d55c75c66d25459d80893a5f72bccce2b54770
|
|
|
|
|
|
|
| |
the HAL init/cleanup. This allows Java/JNI to query BD_ADDR and BD_NAME
prior to HAL BT_enable.
Change-Id: Ic56d859d75d6adaa134d42bb31da4f2c45e349d9
|
|
|
|
|
|
|
|
| |
off and
vendor lib cleanup.
Change-Id: Ie4c4d06db38117175a1c53c9794d69b2f5147425
|
|
|
|
|
|
| |
reset/reclaimed after every enable/disable cycle
Change-Id: Ifc84b9bdaefa91096fe3da369d31884bbac8eaa0
|
|
|
|
|
|
|
| |
1) Run-time configuration: configure stack and vendor at run-time using bt_stack.conf and bt_vendor.conf in /etc/bluetooth/
2) Build-time configuration: Auto-generate buildcfg.h header file from the target config bdroid_$(TARGET_DEVICE).txt file
Change-Id: Ieebb71081b7de404eab37f9ff4596d3dc94547a7
|
|
|
|
|
|
| |
stress tests.
Change-Id: I3c2ed587ddddb293f14c281ccdebb5ba4bf23a7e
|
|
|