Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Jakub Tyszkowski <jakub.tyszkowski@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC 00/13] Connection and request handling improvements
Date: Tue, 10 Jun 2014 13:45:21 +0200	[thread overview]
Message-ID: <2612948.surRFizXAZ@uw000953> (raw)
In-Reply-To: <1402062386-4632-1-git-send-email-jakub.tyszkowski@tieto.com>

Hi Jakub,

On Friday 06 of June 2014 15:46:13 Jakub Tyszkowski wrote:
> Patches from 1 to 9 adds subtle improvements to the existing functionality to
> prepare ground for patches 10 to 13, which adds proper handling of server app
> connections.
> 
> Server app connections should exist for all devices currently connected and for
> each server app registered so we properly propagate requests for reads and
> writes. Such connections are not owned by server apps so they cannot disconnect
> connections owned by other. But they should be notified of any connection state
> changes.
> 
> For this kind of functionality app_connection received owner flag to control
> disconnection permissions. Ownerless connections are created automatically for
> every device if server app registers. and for every server app on device
> connecting for proper event propagation purpose.
> 
> This fixes some issues spotted on the UPF.
> 
> Jakub Tyszkowski (13):
>   android/gatt: Rename app connection handling function
>   android/gatt: Always check for complete response queue
>   android/gatt: Dont process pending requests if queue is empty
>   android/gatt: Fix double processing of pending responses list
>   android/gatt: Improve response filling function
>   android/gatt: Move response filling functions up
>   android/gatt: Use fill_gatt_response in response processing
>   android/gatt: Use common code for server and client apps unregister
>   android/gatt: Rename app unregister function
>   android/gatt: Factor out device disconn. part from app disconn.
>   android/gatt: Create server connections on register
>   android/gatt: Verify client and server disconnect callers
>   android/gatt: Postpone disconnect notifications sent to server apps
> 
>  android/gatt.c | 399 +++++++++++++++++++++++++++++++--------------------------
>  1 file changed, 217 insertions(+), 182 deletions(-)
> 

Patches 1-9 are now applied, thanks.

-- 
Best regards, 
Szymon Janc

      parent reply	other threads:[~2014-06-10 11:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06 13:46 [RFC 00/13] Connection and request handling improvements Jakub Tyszkowski
2014-06-06 13:46 ` [RFC 01/13] android/gatt: Rename app connection handling function Jakub Tyszkowski
2014-06-06 13:46 ` [RFC 02/13] android/gatt: Always check for complete response queue Jakub Tyszkowski
2014-06-06 13:46 ` [RFC 03/13] android/gatt: Dont process pending requests if queue is empty Jakub Tyszkowski
2014-06-06 13:46 ` [RFC 04/13] android/gatt: Fix double processing of pending responses list Jakub Tyszkowski
2014-06-06 13:46 ` [RFC 05/13] android/gatt: Improve response filling function Jakub Tyszkowski
2014-06-06 13:46 ` [RFC 06/13] android/gatt: Move response filling functions up Jakub Tyszkowski
2014-06-06 13:46 ` [RFC 07/13] android/gatt: Use fill_gatt_response in response processing Jakub Tyszkowski
2014-06-06 13:46 ` [RFC 08/13] android/gatt: Use common code for server and client apps unregister Jakub Tyszkowski
2014-06-06 13:46 ` [RFC 09/13] android/gatt: Rename app unregister function Jakub Tyszkowski
2014-06-06 13:46 ` [RFC 10/13] android/gatt: Factor out device disconn. part from app disconn Jakub Tyszkowski
2014-06-06 13:46 ` [RFC 11/13] android/gatt: Create server connections on register Jakub Tyszkowski
2014-06-06 13:46 ` [RFC 12/13] android/gatt: Verify client and server disconnect callers Jakub Tyszkowski
2014-06-06 13:46 ` [RFC 13/13] android/gatt: Postpone disconnect notifications sent to server apps Jakub Tyszkowski
2014-06-10 11:45 ` Szymon Janc [this message]

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=2612948.surRFizXAZ@uw000953 \
    --to=szymon.janc@tieto.com \
    --cc=jakub.tyszkowski@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox