Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Lukasz Rymanowski <lukasz.rymanowski@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/5] android/bluetooth: Extract function sending bond state
Date: Tue, 02 Sep 2014 18:04:08 +0200	[thread overview]
Message-ID: <2746016.MXfPcXTOpL@uw000953> (raw)
In-Reply-To: <1409666103-14663-1-git-send-email-lukasz.rymanowski@tieto.com>

Hi Łukasz,

On Tuesday 02 of September 2014 15:54:59 Lukasz Rymanowski wrote:
> ---
>  android/bluetooth.c | 36 ++++++++++++++++++++++--------------
>  1 file changed, 22 insertions(+), 14 deletions(-)
> 
> diff --git a/android/bluetooth.c b/android/bluetooth.c
> index bd1e747..7c3c198 100644
> --- a/android/bluetooth.c
> +++ b/android/bluetooth.c
> @@ -877,6 +877,27 @@ static uint8_t device_bond_state(struct device *dev)
>  	return HAL_BOND_STATE_NONE;
>  }
>  
> +static void update_bond_state(struct device *dev, uint8_t status,
> +					uint8_t old_bond, uint8_t new_bond)
> +{
> +	if (old_bond == new_bond)
> +		return;
> +
> +	/*
> +	 * For incoming just works bonding we will switch here from
> +	 * non bonded to bonded directly. This is something Android
> +	 * will not handle in their bond state machine. To make Android
> +	 * handle it corretly we need to send BONDING state before BOND
> +	 */
> +	if (old_bond == HAL_BOND_STATE_NONE &&
> +				new_bond == HAL_BOND_STATE_BONDED)
> +		send_bond_state_change(dev, status,
> +						HAL_BOND_STATE_BONDING);
> +
> +	send_bond_state_change(dev, status, new_bond);
> +
> +}
> +
>  static void update_device_state(struct device *dev, uint8_t addr_type,
>  				uint8_t status, bool pairing, bool paired,
>  				bool bonded)
> @@ -892,20 +913,7 @@ static void update_device_state(struct device *dev, uint8_t addr_type,
>  
>  	new_bond = device_bond_state(dev);
>  
> -	if (old_bond != new_bond) {
> -		/*
> -		 * For incoming just works bonding we will switch here from
> -		 * non bonded to bonded directly. This is something Android
> -		 * will not handle in their bond state machine. To make Android
> -		 * handle it corretly we need to send BONDING state before BOND
> -		 */
> -		if (old_bond == HAL_BOND_STATE_NONE &&
> -					new_bond == HAL_BOND_STATE_BONDED)
> -			send_bond_state_change(dev, status,
> -							HAL_BOND_STATE_BONDING);
> -
> -		send_bond_state_change(dev, status, new_bond);
> -	}
> +	update_bond_state(dev, status, old_bond, new_bond);
>  }
>  
>  static void send_device_property(struct device *dev, uint8_t type,
> 

All 5 patches applied. Thanks.

-- 
Best regards, 
Szymon Janc

      parent reply	other threads:[~2014-09-02 16:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 13:54 [PATCH 1/5] android/bluetooth: Extract function sending bond state Lukasz Rymanowski
2014-09-02 13:55 ` [PATCH 2/5] android/bluetooth: Fix status in "fake" bonding notification Lukasz Rymanowski
2014-09-02 13:55 ` [PATCH 3/5] android/bluetooth: Improve sending bond state notification Lukasz Rymanowski
2014-09-02 13:55 ` [PATCH 4/5] android/bluetooth: Fix bond state for non-bonded devices Lukasz Rymanowski
2014-09-02 13:55 ` [PATCH 5/5] android/tester: Add test verifying correct bond state notification Lukasz Rymanowski
2014-09-02 16:04 ` 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=2746016.MXfPcXTOpL@uw000953 \
    --to=szymon.janc@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lukasz.rymanowski@tieto.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