Joao,
On 08/07/2012 07:29 PM, Joao Paulo Rechi Vita wrote:
Hello Chen,
On Mon, Aug 6, 2012 at 2:52 AM, Chen Ganir <chen.ganir@xxxxxx> wrote:
Claudio,
On 08/03/2012 03:57 PM, Claudio Takahasi wrote:
Hi Chen Ganir:
On Wed, Aug 1, 2012 at 3:40 AM, Chen Ganir <chen.ganir@xxxxxx> wrote:
On 07/25/2012 08:42 AM, Chen Ganir wrote:
Add suupport for LE GATT Client Battery Service.
This plugin adds battery list to the btd_device, exposes DBUS API to
list
the
device batteries, and allows querying for battery information. In
addition
this
patch allows getting notifications for battery level changes.
Look at doc/device-api.txt and doc/battery-api.txt for more information.
This is version 2 of this patch set, rebased on top of the latest
sources
and
fixes some issues found during testing and in the ML comments.
Chen Ganir (9):
Battery: Add Battery Service GATT Client
Battery: Add connection logic
Battery: Discover Characteristic Descriptors
Battery: Get Battery ID
Battery: Add Battery list to btd_device
Battery: Add Battery D-BUS API
Battery: Read Battery level characteristic
Battery: Add support for notifications
Battery: Emit property changed on first read
Makefile.am | 10 +-
doc/battery-api.txt | 38 +++
doc/device-api.txt | 5 +
profiles/batterystate/batterystate.c | 518
++++++++++++++++++++++++++++++++++
profiles/batterystate/batterystate.h | 24 ++
profiles/batterystate/main.c | 67 +++++
profiles/batterystate/manager.c | 93 ++++++
profiles/batterystate/manager.h | 24 ++
src/device.c | 66 +++++
src/device.h | 3 +
10 files changed, 846 insertions(+), 2 deletions(-)
create mode 100644 doc/battery-api.txt
create mode 100644 profiles/batterystate/batterystate.c
create mode 100644 profiles/batterystate/batterystate.h
create mode 100644 profiles/batterystate/main.c
create mode 100644 profiles/batterystate/manager.c
create mode 100644 profiles/batterystate/manager.h
Ping anyone ? Did anyone get to review this ?
Thanks,
Chen Ganir
not yet.
We have an INTERNAL release in two weeks, next week we will send
comments in the ML.
Thanks. I'll be waiting.
I've been reviewing and did some quick tests on your code. It's
working with some minor issues, and I'll comment them on each commit.
But first I have a few more general questions:
1. Any specific reason for calling the plugin directory and files
'batterystate'? I don't see any reference to this name on the
documentation.
No specific reason. I will rename it to Battery, to correspond with the
BAS spec.
2. The spec recommends reading the battery level value with very
little frequency. Quoting the section 3.1.1:
"For example, if the expected battery life is in the order of years,
reading the battery level value more frequently than once a week is
not recommended."
And on the same section:
"The value of the Client Characteristic Configuration descriptor is
persistent for bonded devices when not in a connection."
At the moment the plugin is reading it every time it is probed, which
is a lot more than recommended. What do you think about only enabling
notifications after paring, and not reading the value at all and just
wait for the notifications. If the device doesn't support
notifications (which I *think* should be uncommon) we can read the
value after pairing and refresh it every week or so. For this to work
well we'll need characteristics value storage support, but that will
improve other things as well. While we don't support that, I don't
have other ideas to improve this.
I agree with you that we will need some storage to allow following the
specs correctly. I could just read the battery level on pairing only,
and then rely on notifications (if supported) or read battery level on
each connect. However, what happens if the device remains connected for
a long period of time (more than a week) ? I will need to add some kind
of mechanism to check how much time has passed since last reading, and
invoke battery level readout for each battery level characteristic. Do
you have any suggestions for improvement here ?
BR,
Claudio
Chen Ganir.
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Thanks for reviewing this patch set. I will try to send revised and
fixed set today or tomorrow with the fixes mentioned in your other patch
review.
Chen Ganir.
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
