diff options
| author | YK Jeffrey Chao <jechao@broadcom.com> | 2012-07-18 14:57:38 -0700 |
|---|---|---|
| committer | Matthew Xie <mattx@google.com> | 2012-07-26 17:55:17 -0700 |
| commit | 0604d2d72ff493bfe710f95c20f6a3bbc2a2cb38 (patch) | |
| tree | bf1663143515c1157a231135c71eaf4df85b0947 /main/bte_logmsg.c | |
| parent | 4f2d8177155f253cda00490912bbcc66466c0c73 (diff) | |
| download | external_bluetooth_bluedroid-0604d2d72ff493bfe710f95c20f6a3bbc2a2cb38.zip external_bluetooth_bluedroid-0604d2d72ff493bfe710f95c20f6a3bbc2a2cb38.tar.gz external_bluetooth_bluedroid-0604d2d72ff493bfe710f95c20f6a3bbc2a2cb38.tar.bz2 | |
Fix for BT-OFF hung issue seen in BT on/off instrumentation test.
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
Diffstat (limited to 'main/bte_logmsg.c')
0 files changed, 0 insertions, 0 deletions