linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen Ganir <chen.ganir@ti.com>
To: Joao Paulo Rechi Vita <jprvita@openbossa.org>
Cc: <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH 07/10] battery: Add Battery to device
Date: Wed, 12 Sep 2012 07:54:52 +0300	[thread overview]
Message-ID: <5050159C.7030307@ti.com> (raw)
In-Reply-To: <CAAngNMbnRc-JxTP_aGwVbyov3bsd=dVgAC=GkjMM9mnzgtNPQQ@mail.gmail.com>

On 09/12/2012 12:40 AM, Joao Paulo Rechi Vita wrote:
> On Tue, Sep 11, 2012 at 4:38 AM,  <chen.ganir@ti.com> wrote:
>> From: Chen Ganir <chen.ganir@ti.com>
>>
>> Add/Remove battery from device
>> ---
>>   profiles/battery/battery.c |   14 ++++++++++----
>>   1 file changed, 10 insertions(+), 4 deletions(-)
>>
>> diff --git a/profiles/battery/battery.c b/profiles/battery/battery.c
>> index d1e0b6e..31f2297 100644
>> --- a/profiles/battery/battery.c
>> +++ b/profiles/battery/battery.c
>> @@ -49,8 +49,9 @@ struct battery {
>>   static GSList *servers;
>>
>>   struct characteristic {
>> -       struct gatt_char        attr;   /* Characteristic */
>> -       struct battery          *batt;  /* Parent Battery Service */
>> +       struct device_battery  *devbatt;        /* device_battery pointer */
>> +       struct gatt_char        attr;           /* Characteristic */
>> +       struct battery          *batt;          /* Parent Battery Service */
>
> Just a minor pick here: the comment alignment of attr and batt should
> have been fixed on the previous commit, to keep it consistent along
> the series.
>
You are correct. That should have been like that, but i missed it. Will 
fix it.

>>          GSList                          *desc;  /* Descriptors */
>>          uint8_t                 ns;             /* Battery Namespace */
>>          uint16_t                description;    /* Battery description */
>> @@ -79,6 +80,8 @@ static void char_free(gpointer user_data)
>>
>>          g_slist_free_full(c->desc, g_free);
>>
>> +       btd_device_remove_battery(c->devbatt);
>> +
>>          g_free(c);
>>   }
>>
>> @@ -160,12 +163,12 @@ static void discover_desc_cb(guint8 status, const guint8 *pdu, guint16 len,
>>          if (status != 0) {
>>                  error("Discover all characteristic descriptors failed [%s]: %s",
>>                                          ch->attr.uuid, att_ecode2str(status));
>> -               return;
>> +               goto update_char;
>>          }
>>
>>          list = dec_find_info_resp(pdu, len, &format);
>>          if (list == NULL)
>> -               return;
>> +               goto update_char;
>>
>>          for (i = 0; i < list->num; i++) {
>>                  struct descriptor *desc;
>> @@ -186,6 +189,9 @@ static void discover_desc_cb(guint8 status, const guint8 *pdu, guint16 len,
>>          }
>>
>>          att_data_list_free(list);
>> +
>> +update_char:
>> +       ch->devbatt = btd_device_add_battery(ch->batt->dev);
>
> If I understood correctly, adding a battery to the device is a
> consequence of finding the "Battery Level" characteristic, and not
> related to the descriptors discovery. So the call to
> btd_device_add_battery() should be done inside the
> configure_battery_cb() instead of the discover_desc_cb(). This way
> you'll not need all these goto's.
>
You are correct. It can be done there.

>>   }
>>
>>
>> --
>> 1.7.9.5
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>

Thanks,

-- 
BR,
Chen Ganir


  reply	other threads:[~2012-09-12  4:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-11  7:38 [PATCH 00/10] Implement Generic battery and LE Battery client chen.ganir
2012-09-11  7:38 ` [PATCH 01/10] battery: Add generic device battery documentation chen.ganir
2012-09-11 15:34   ` Joao Paulo Rechi Vita
2012-09-12  4:45     ` Chen Ganir
2012-09-11  7:38 ` [PATCH 02/10] battery: Implement Generic device battery chen.ganir
2012-09-11 18:27   ` Joao Paulo Rechi Vita
2012-09-12  4:48     ` Chen Ganir
2012-09-12  8:45       ` Johan Hedberg
2012-09-12 10:30         ` Chen Ganir
2012-09-12 10:57           ` Anderson Lizardo
2012-09-13 11:32             ` Chen Ganir
2012-09-11  7:38 ` [PATCH 03/10] battery: Add GATT Battery Client Service skeleton chen.ganir
2012-09-11  7:38 ` [PATCH 04/10] battery: Add client connection logic chen.ganir
2012-09-11  7:38 ` [PATCH 05/10] battery: Discover Characteristic Descriptors chen.ganir
2012-09-11 20:52   ` Joao Paulo Rechi Vita
2012-09-12  4:49     ` Chen Ganir
2012-09-11  7:38 ` [PATCH 06/10] battery: Get Battery ID chen.ganir
2012-09-11  7:38 ` [PATCH 07/10] battery: Add Battery to device chen.ganir
2012-09-11 21:40   ` Joao Paulo Rechi Vita
2012-09-12  4:54     ` Chen Ganir [this message]
2012-09-11  7:38 ` [PATCH 08/10] battery: Read Battery level characteristic chen.ganir
2012-09-11 21:50   ` Joao Paulo Rechi Vita
2012-09-12  4:55     ` Chen Ganir
2012-09-11  7:38 ` [PATCH 09/10] battery: Add support for notifications chen.ganir
2012-09-11 22:08   ` Joao Paulo Rechi Vita
2012-09-12  4:58     ` Chen Ganir
2012-09-13 11:27       ` Chen Ganir

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=5050159C.7030307@ti.com \
    --to=chen.ganir@ti.com \
    --cc=jprvita@openbossa.org \
    --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;
as well as URLs for NNTP newsgroup(s).