platform_hardware_interfaces/bluetooth/1.0
Zach Johnson fed25ad256 Fix MCT data transport for the BT HAL
The vendor open interface command returns the total number
of FDs opened. (2 or 4 if the interface is MCT)

However, the list of FDs is always 4 in either case. If the
open command returns 2, the FDs are shared cmd/event and
data in/out.

2 FDs example
[41, 41, 42, 42]

4 FDs example
[41, 42, 43, 44]

If we condition the registration of ACL_IN on the total
number of FDs, then 2 FD MCT interfaces will not get data.

Fixes: 36067612, 36035039, 36188793
Test: manual, pairing is quick and data does transfer
Change-Id: Icc8728239ba81426d5fc0e678c5c5480fd9b5081
2017-03-15 13:50:36 -07:00
..
default Fix MCT data transport for the BT HAL 2017-03-15 13:50:36 -07:00
vts/functional Change vts target base test class name 2017-03-10 00:42:13 -08:00
Android.bp Use filegroup as genrule srcs. 2017-02-10 02:18:07 +00:00
Android.mk Updated makefiles 2017-02-09 16:56:56 -08:00
IBluetoothHci.hal bluetooth: Add initialization completed callback 2017-01-18 19:38:57 +00:00
IBluetoothHciCallbacks.hal bluetooth: Add initialization completed callback 2017-01-18 19:38:57 +00:00
types.hal Add Bluetooth HAL definition 2016-10-13 22:32:38 +00:00