From: Arik Nemtsov <arik@wizery.com>
To: <linux-bluetooth@vger.kernel.org>
Cc: Arik Nemtsov <arik@wizery.com>
Subject: [PATCH 0/8] Implement ProximityReporter profiles
Date: Thu, 8 Mar 2012 15:57:04 +0200 [thread overview]
Message-ID: <1331215032-27695-1-git-send-email-arik@wizery.com> (raw)
This patch-set implements the Link loss and Immediate Alert GATT
server profiles.
A few API calls are added/changed in preparation, the most notable of
which is the addition of the remote-device to each GATT read/write callback.
The new profiles are separated into their own files for clarity.
A ProximityReporter D-Bus interface is registered for each remote device.
Property queries and PropertyChanged notifications are implemented, in
accordance to doc/proximity-api.txt.
Comments are welcome.
Arik Nemtsov (8):
att: add remote btd_device to ATT read/write callbacks
adapter: add API to find an existing device by D-Bus path
adapter: add DeviceAdded signal when existing device is added
proximity: reporter: save global D-Bus connection
proximity: reporter: move definitions to .h and add util function
proximity: link loss: implement link loss server
proximity: immediate alert: implement immediate alert server
proximity: reporter: implement D-Bus API
Makefile.am | 4 +-
attrib/att.h | 6 +-
doc/adapter-api.txt | 5 +
plugins/gatt-example.c | 3 +-
proximity/immalert.c | 288 +++++++++++++++++++++++++++++++++++++++
proximity/immalert.h | 26 ++++
proximity/linkloss.c | 350 ++++++++++++++++++++++++++++++++++++++++++++++++
proximity/linkloss.h | 26 ++++
proximity/reporter.c | 275 +++++++++++++++++++++++++++----------
proximity/reporter.h | 16 +++
src/adapter.c | 32 +++++
src/adapter.h | 2 +
src/attrib-server.c | 19 ++-
time/server.c | 6 +-
14 files changed, 972 insertions(+), 86 deletions(-)
create mode 100644 proximity/immalert.c
create mode 100644 proximity/immalert.h
create mode 100644 proximity/linkloss.c
create mode 100644 proximity/linkloss.h
--
1.7.5.4
next reply other threads:[~2012-03-08 13:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 13:57 Arik Nemtsov [this message]
2012-03-08 13:57 ` [PATCH 1/8] att: add remote btd_device to ATT read/write callbacks Arik Nemtsov
2012-03-08 13:57 ` [PATCH 2/8] adapter: add API to find an existing device by D-Bus path Arik Nemtsov
2012-03-08 13:57 ` [PATCH 3/8] adapter: add DeviceAdded signal when existing device is added Arik Nemtsov
2012-03-08 13:57 ` [PATCH 4/8] proximity: reporter: save global D-Bus connection Arik Nemtsov
2012-03-08 13:57 ` [PATCH 5/8] proximity: reporter: move definitions to .h and add util function Arik Nemtsov
2012-03-08 13:57 ` [PATCH 6/8] proximity: link loss: implement link loss server Arik Nemtsov
2012-03-14 13:09 ` Anderson Lizardo
2012-03-14 20:54 ` Arik Nemtsov
2012-03-08 13:57 ` [PATCH 7/8] proximity: immediate alert: implement immediate alert server Arik Nemtsov
2012-03-08 13:57 ` [PATCH 8/8] proximity: reporter: implement D-Bus API Arik Nemtsov
2012-03-14 13:19 ` Anderson Lizardo
2012-03-14 20:56 ` Arik Nemtsov
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=1331215032-27695-1-git-send-email-arik@wizery.com \
--to=arik@wizery.com \
--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).