All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Rymanowski <lukasz.rymanowski@tieto.com>
To: linux-bluetooth@vger.kernel.org
Cc: Lukasz Rymanowski <lukasz.rymanowski@tieto.com>
Subject: [PATCH 00/16] Move reconnect logic from HOG to GATT
Date: Tue,  2 Sep 2014 12:09:45 +0200	[thread overview]
Message-ID: <1409652601-28689-1-git-send-email-lukasz.rymanowski@tieto.com> (raw)

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


             reply	other threads:[~2014-09-02 10:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 10:09 Lukasz Rymanowski [this message]
2014-09-02 10:09 ` [PATCH 01/16] android/gatt: Fix for device type in gatt Lukasz Rymanowski
2014-09-02 10:09 ` [PATCH 02/16] android/hidhost: Remove invalid connecting state notification Lukasz Rymanowski
2014-09-02 10:09 ` [PATCH 03/16] android/hidhost: Allow to use cached dev when connecting Lukasz Rymanowski
2014-09-02 10:09 ` [PATCH 04/16] android/bluetooth: Add tracking if device is in white list Lukasz Rymanowski
2014-09-02 10:09 ` [PATCH 05/16] android/gatt: Add tracking for autoconnect apps Lukasz Rymanowski
2014-09-02 10:09 ` [PATCH 06/16] android/gatt: Add API to autoconnect GATT based devices Lukasz Rymanowski
2014-09-02 10:09 ` [PATCH 07/16] android/gatt: Add API to remove autoconnect GATT based device Lukasz Rymanowski
2014-09-02 15:27   ` Szymon Janc
2014-09-03  6:55     ` Lukasz Rymanowski
2014-09-02 10:09 ` [PATCH 08/16] android/gatt: Unsubscribe from autoconnect on unregister Lukasz Rymanowski
2014-09-02 10:09 ` [PATCH 09/16] android/gatt: Extract remove_autoconnect_device helper Lukasz Rymanowski
2014-09-02 10:09 ` [PATCH 10/16] android/gatt: Move find_conn up in the file Lukasz Rymanowski
2014-09-02 10:09 ` [PATCH 11/16] android/gatt: Notify apps interested in autoconnect about connection Lukasz Rymanowski
2014-09-02 10:09 ` [PATCH 12/16] android/gatt: Extract trigger le connection to new function Lukasz Rymanowski
2014-09-02 10:09 ` [PATCH 13/16] android/gatt: Move auto_connect_le() up in the file Lukasz Rymanowski
2014-09-02 10:09 ` [PATCH 14/16] android/gatt: Make sure GATT will reconnect after disconnection Lukasz Rymanowski
2014-09-02 10:10 ` [PATCH 15/16] android/gatt: Remove device from white list on device destroy Lukasz Rymanowski
2014-09-02 10:10 ` [PATCH 16/16] android/hidhost: Remove reconnect logic Lukasz Rymanowski
2014-09-02 15:19 ` [PATCH 00/16] Move reconnect logic from HOG to GATT Szymon Janc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1409652601-28689-1-git-send-email-lukasz.rymanowski@tieto.com \
    --to=lukasz.rymanowski@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.