All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Rymanowski <lukasz.rymanowski@tieto.com>
To: Szymon Janc <szymon.janc@tieto.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] android/bluetooth: Add support to read LE features by Android
Date: Wed, 3 Dec 2014 10:27:03 +0100	[thread overview]
Message-ID: <CAMudyAtzWsPZ-0nStmA-O7X2muuVfAXxx5RB+Hv-cDWgfyJG=g@mail.gmail.com> (raw)
In-Reply-To: <3501439.5pFPeTDH5C@uw000953>

Hi Szymon,

On 3 December 2014 at 10:04, Szymon Janc <szymon.janc@tieto.com> wrote:
> Hi Łukasz,
>
> On Monday 01 of December 2014 15:18:00 Lukasz Rymanowski wrote:
>> This patch adds support to read LE features by Android framework.
>> For now we set all to 0.
>> ---
>>  android/bluetooth.c | 18 ++++++++++++++++++
>>  android/hal-msg.h   |  1 +
>>  2 files changed, 19 insertions(+)
>>
>> diff --git a/android/bluetooth.c b/android/bluetooth.c
>> index f79ca37..989f5d5 100644
>> --- a/android/bluetooth.c
>> +++ b/android/bluetooth.c
>> @@ -176,6 +176,7 @@ static struct {
>>
>>       char *name;
>>
>> +     uint8_t le_features[8];
>
> I'm still not sure how we get required info but I think we should construct
> this on-demand to avoid doubling state ie. local_privacy_enabled can be get
> from current_settings.
>

What we can do here is name all the features instead and omit privacy
(I believe it is the only one feature we already have somewhere else)
In that case when we construct response to Android we will build out
of those params.

\Lukasz

>>       uint32_t current_settings;
>>       uint32_t supported_settings;
>>
>> @@ -189,6 +190,7 @@ static struct {
>>       .index = MGMT_INDEX_NONE,
>>       .dev_class = 0,
>>       .name = NULL,
>> +     .le_features = {0},
>>       .current_settings = 0,
>>       .supported_settings = 0,
>>       .cur_discovery_type = SCAN_TYPE_NONE,
>> @@ -3784,6 +3786,14 @@ static uint8_t get_adapter_discoverable_timeout(void)
>>       return HAL_STATUS_SUCCESS;
>>  }
>>
>> +static uint8_t get_adapter_le_features(void)
>> +{
>> +     send_adapter_property(HAL_PROP_ADAPTER_LOCAL_LE_FEAT,
>> +                                     sizeof(adapter.le_features),
>> +                                     &adapter.le_features[0]);
>> +     return HAL_STATUS_SUCCESS;
>> +}
>> +
>>  static void handle_get_adapter_prop_cmd(const void *buf, uint16_t len)
>>  {
>>       const struct hal_cmd_get_adapter_prop *cmd = buf;
>> @@ -3817,6 +3827,9 @@ static void handle_get_adapter_prop_cmd(const void *buf, uint16_t len)
>>       case HAL_PROP_ADAPTER_DISC_TIMEOUT:
>>               status = get_adapter_discoverable_timeout();
>>               break;
>> +     case HAL_PROP_ADAPTER_LOCAL_LE_FEAT:
>> +             status = get_adapter_le_features();
>> +             break;
>>       default:
>>               status = HAL_STATUS_FAILED;
>>               break;
>> @@ -3898,6 +3911,11 @@ static void get_adapter_properties(void)
>>                                                                       uuids);
>>       ev->num_props++;
>>
>> +     size += fill_hal_prop(buf + size, HAL_PROP_ADAPTER_LOCAL_LE_FEAT,
>> +                     sizeof(adapter.le_features), &adapter.le_features[0]);
>
> adapter.le_features instead of &adapter.le_features[0]
>
>> +
>> +     ev->num_props++;
>> +
>>       ipc_send_notif(hal_ipc, HAL_SERVICE_ID_BLUETOOTH,
>>                               HAL_EV_ADAPTER_PROPS_CHANGED, size, buf);
>>  }
>> diff --git a/android/hal-msg.h b/android/hal-msg.h
>> index 33b53c5..67c6573 100644
>> --- a/android/hal-msg.h
>> +++ b/android/hal-msg.h
>> @@ -142,6 +142,7 @@ struct hal_prop_device_info {
>>       uint16_t manufacturer;
>>  } __attribute__((packed));
>>
>> +#define HAL_PROP_ADAPTER_LOCAL_LE_FEAT               0x0d
>>  #define HAL_PROP_DEVICE_TIMESTAMP            0xFF
>>
>>  #define HAL_ADAPTER_SCAN_MODE_NONE           0x00
>>
>
> --
> Best regards,
> Szymon Janc

      reply	other threads:[~2014-12-03  9:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01 14:18 [PATCH] android/bluetooth: Add support to read LE features by Android Lukasz Rymanowski
2014-12-03  9:04 ` Szymon Janc
2014-12-03  9:27   ` Lukasz Rymanowski [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='CAMudyAtzWsPZ-0nStmA-O7X2muuVfAXxx5RB+Hv-cDWgfyJG=g@mail.gmail.com' \
    --to=lukasz.rymanowski@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=szymon.janc@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 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.