All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Subject: Bluetooth LE battery reporting?
Date: Tue, 05 Sep 2017 18:03:22 +0200	[thread overview]
Message-ID: <1504627402.6911.48.camel@hadess.net> (raw)

Hey,

I'm back looking into Bluetooth LE battery reporting, and I'm a bit
stumped as to what would need to be done to add support for it.

First, I've already found a few old implementations:

- I cleaned this up a couple of years ago, to try it out, and it spit
debug information as expected. Doesn't compile anymore:
https://gfiber.googlesource.com/vendor/opensource/bluez/+/42bc327d464b1f7c2c73b3fecb2e9a8d3dc01035/profiles/battery/battery.c

- chen.ganir@ti.com 's "Add Battery Service GATT Client" patchset that
was posted to the list in 2012 (!)

- and finally, there's bluez' very own "bas", the last commit touching it says:
commit b6cb2d3ec320bdfdf1cdcdf750e767d214170efd
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date:   Wed Nov 11 13:08:52 2015 +0200

    bas: Move code from android to profiles
    
    This is a place holder until the code is ported to use shared API so it
    can be shared by android and D-Bus daemon.

That last one is compiled, but doesn't seem to be hooked up (?). I
tested this with a Microsoft Arc Touch Mouse SE (the same mouse I
tested that first patch with).

Is this all hooked up and I'd just need to export the battery
information through D-Bus?

Or does it need fixing, in which case, which plugin could I use as an
example of what porting to that elusive "shared API" should look like?

Cheers

             reply	other threads:[~2017-09-05 16:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 16:03 Bastien Nocera [this message]
2017-09-05 17:37 ` Bluetooth LE battery reporting? Szymon Janc
2017-09-05 17:44   ` Marcel Holtmann
2017-09-06  8:29     ` Luiz Augusto von Dentz
2017-09-06  8:40       ` Marcel Holtmann
2017-09-06 14:37         ` Bastien Nocera
2017-09-06 23:16           ` Bastien Nocera
2017-09-07 14:03             ` Bastien Nocera
2017-09-07 14:15               ` Luiz Augusto von Dentz
2017-09-07 14:42                 ` Bastien Nocera
2017-09-07 15:56                 ` Bastien Nocera
2017-09-21 15:03                 ` Bastien Nocera

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=1504627402.6911.48.camel@hadess.net \
    --to=hadess@hadess.net \
    --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 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.