linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Scott James Remnant <scott@netsplit.com>
Cc: linux-bluetooth@vger.kernel.org, keybuk@chromium.org
Subject: Re: [PATCHv2 0/4] Add support for bonding callbacks and retrying
Date: Mon, 30 Jan 2012 11:41:20 -0800	[thread overview]
Message-ID: <1327952480.1955.154.camel@aeonflux> (raw)
In-Reply-To: <1327430878-23913-1-git-send-email-scott@netsplit.com>

Hi Scott,

> Thanks for the comments on the autopair plugin patches, I'm still
> working on updating that but I wanted to submit the underlying core
> changes necessary while I do so.
> 
> This adds plugin support for a callback called when bonding completes,
> either successfully or fails, or is cancelled. In the success or failure
> cases the callback may return TRUE, in which case the bonding is retried
> after a short backoff period.
> 
> The (to be submitted) autopair plugin will use this to retry bonding if
> a fixed PIN it provides fails, and ignore the subsequent attempt so that
> the ordinary PIN handling (user agent, keyboard auto-generation, etc.)
> happens.

yesterday Johan and talked about this a little bit and I just wanna
quickly iterate some small comments here.

So we should only allow retrying when we initiated the bonding. If the
other side started the pairing, then retrying should not even be
considered.

We have to also ensure that we do not disconnect the ACL in between the
retry attempts. Otherwise some car kits might cancel their pairing
procedure and you have to have user interaction to get it back into
pairing mode. So if the ACL gets disconnect, then we should just fail
and cancel the bonding.

For some extra credit we might need to retry the pairing in the kernel
if we happen to run into an LMP collision due to role switch changes or
similar issues. And hide that from the user if this happens.

Regards

Marcel



  parent reply	other threads:[~2012-01-30 19:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24 18:47 [PATCHv2 0/4] Add support for bonding callbacks and retrying Scott James Remnant
2012-01-24 18:47 ` [PATCHv2 1/4] Add support for retrying a bonding Scott James Remnant
2012-01-24 18:47 ` [PATCHv2 2/4] plugin: Add bonding callback support for plugins Scott James Remnant
2012-01-24 18:47 ` [PATCHv2 3/4] bonding: retry if callback returns TRUE Scott James Remnant
2012-01-24 18:47 ` [PATCHv2 4/4] bonding: call plugin callback on cancellation Scott James Remnant
2012-01-30 19:41 ` Marcel Holtmann [this message]
2012-01-30 21:38   ` [PATCHv2 0/4] Add support for bonding callbacks and retrying Scott James Remnant
2012-01-30 21:51     ` Marcel Holtmann
2012-01-30 21:57       ` Scott James Remnant
2012-01-30 22:08         ` Marcel Holtmann

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=1327952480.1955.154.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=keybuk@chromium.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=scott@netsplit.com \
    /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;
as well as URLs for NNTP newsgroup(s).