Following patches moves reconnect feature from GATT clients to GATT. GATT is in charge to decide if white list is used or legacy "passive scan" There are also couple of fixes found in HOG during testing. Tested on Android against kernel with mgmt version 1.6 and 1.7 Lukasz Rymanowski (16): android/gatt: Fix for device type in gatt android/hidhost: Remove invalid connecting state notification android/hidhost: Allow to use cached dev when connecting android/bluetooth: Add tracking if device is in white list android/gatt: Add tracking for autoconnect apps android/gatt: Add API to autoconnect GATT based devices android/gatt: Add API to remove autoconnect GATT based device android/gatt: Unsubscribe from autoconnect on unregister android/gatt: Extract remove_autoconnect_device helper android/gatt: Move find_conn up in the file android/gatt: Notify apps interested in autoconnect about connection android/gatt: Extract trigger le connection to new function android/gatt: Move auto_connect_le() up in the file android/gatt: Make sure GATT will reconnect after disconnection android/gatt: Remove device from white list on device destroy android/hidhost: Remove reconnect logic android/bluetooth.c | 23 ++++- android/gatt.c | 246 +++++++++++++++++++++++++++++++++++++++------------- android/gatt.h | 2 + android/hidhost.c | 38 +++----- 4 files changed, 218 insertions(+), 91 deletions(-) -- 1.8.4 -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
