Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Alex Deymo <deymo@chromium.org>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
	keybuk@chromium.org
Subject: Re: [PATCH v3 3/8] core: Add support for retrying a bonding
Date: Wed, 24 Apr 2013 14:29:02 +0300	[thread overview]
Message-ID: <20130424112902.GB15231@x220.ger.corp.intel.com> (raw)
In-Reply-To: <1366740247-368-4-git-send-email-deymo@chromium.org>

Hi Alex,

On Tue, Apr 23, 2013, Alex Deymo wrote:
> --- a/src/adapter.c
> +++ b/src/adapter.c
> @@ -4253,7 +4253,7 @@ static void adapter_remove_connection(struct btd_adapter *adapter,
>  	if (device_is_authenticating(device))
>  		device_cancel_authentication(device, TRUE);
>  
> -	if (device_is_temporary(device)) {
> +	if (device_is_temporary(device) && !device_is_retrying(device)) {
>  		const char *path = device_get_path(device);
>  
>  		DBG("Removing temporary device %s", path);
> diff --git a/src/device.c b/src/device.c
> index 5686443..291ae5f 100644
> --- a/src/device.c
> +++ b/src/device.c
> @@ -86,6 +86,9 @@ struct bonding_req {
>  	struct btd_device *device;
>  	struct agent *agent;
>  	struct pincb_iter *cb_iter;
> +	uint8_t capability;
> +	uint8_t status;
> +	guint retry_timer;
>  };
>  
>  typedef enum {
> @@ -1400,7 +1403,8 @@ static void device_svc_resolved(struct btd_device *dev, int err)
>  
>  static struct bonding_req *bonding_request_new(DBusMessage *msg,
>  						struct btd_device *device,
> -						struct agent *agent)
> +						struct agent *agent,
> +						uint8_t io_cap)
>  {
>  	struct bonding_req *bonding;
>  	char addr[18];
> @@ -1414,6 +1418,8 @@ static struct bonding_req *bonding_request_new(DBusMessage *msg,
>  
>  	bonding->cb_iter = pincb_iter_new(device->adapter);
>  
> +	bonding->capability = io_cap;

Do you really need to store this? Since you've got bonding->agent you
could just use agent_get_io_capability()?

> +gboolean device_is_retrying(struct btd_device *device)
> +{
> +	struct bonding_req *bonding = device->bonding;
> +
> +	return bonding && bonding->retry_timer != 0;

We try to keep the convention of using > 0 instead of != 0 for testing
for valid GSource ID values.

Johan

  reply	other threads:[~2013-04-24 11:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 18:03 [PATCH v3 0/8] Autopair plugin Alex Deymo
2013-04-23 18:04 ` [PATCH v3 1/8] core: Convert the pincode callback to an interable list Alex Deymo
2013-04-24 11:24   ` Johan Hedberg
2013-04-24 11:42   ` Johan Hedberg
2013-04-23 18:04 ` [PATCH v3 2/8] plugins: Extend the pin code callback with the call number Alex Deymo
2013-04-23 18:04 ` [PATCH v3 3/8] core: Add support for retrying a bonding Alex Deymo
2013-04-24 11:29   ` Johan Hedberg [this message]
2013-04-23 18:04 ` [PATCH v3 4/8] core: retry bonding attempt until the iterator reaches the end Alex Deymo
2013-04-24 11:32   ` Johan Hedberg
2013-04-23 18:04 ` [PATCH v3 5/8] core: Add device_get_class to the public interface Alex Deymo
2013-04-23 18:04 ` [PATCH v3 6/8] autopair: Add the autopair plugin Alex Deymo
2013-04-23 18:04 ` [PATCH v3 7/8] core: Expose the last bonding attempt timeout on retry Alex Deymo
2013-04-24 11:37   ` Johan Hedberg
2013-04-24 14:03     ` Marcel Holtmann
2013-04-23 18:04 ` [PATCH v3 8/8] autopair: Try a fixed pincode for keyboards rejecting random codes Alex Deymo

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=20130424112902.GB15231@x220.ger.corp.intel.com \
    --to=johan.hedberg@gmail.com \
    --cc=deymo@chromium.org \
    --cc=keybuk@chromium.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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