From: Arman Uguray <armansito@chromium.org>
To: linux-bluetooth@vger.kernel.org
Cc: Arman Uguray <armansito@chromium.org>
Subject: [RFC BlueZ 0/1] Introduce bt_gatt.
Date: Fri, 16 May 2014 13:37:15 -0700 [thread overview]
Message-ID: <1400272636-31555-1-git-send-email-armansito@chromium.org> (raw)
bt_gatt implements GATT client operations and will be backed by bt_att. It is
effectively a rewrite of attrib/gatt, where it provides a more high-level
abstraction over GATT operation results (instead of returning raw PDUs) so that
ATT protocol level encoding/decoding is taken care of by the internal bt_att
instance. This is also meant to be a more thorough implementation of GATT
procedures, however some of them are omitted (for now):
- "Read Using Characteristic UUID"
- "Read Multiple Characteristic Values"
- "Signed Write Without Response"
- "Characteristic Value Reliable Writes"
These operations can be easily added in the future as needed, since bt_att will
provide all possible ATT protocol interactions.
bt_gatt doesn't implement attribute caching and is not a complete client
implementation on its own. It will be used together with gatt_db, where a higher
level abstraction will be responsible for managing lookups from the database vs
over-the-air and updating the database as needed. bt_gatt only provides the
hooks for performing all the necessary over-the-air GATT procedures.
Comments welcome.
Arman Uguray (1):
src/shared/gatt: Introduce bt_gatt skeleton.
Makefile.am | 3 +-
src/shared/gatt.c | 192 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
src/shared/gatt.h | 189 +++++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 383 insertions(+), 1 deletion(-)
create mode 100644 src/shared/gatt.c
create mode 100644 src/shared/gatt.h
--
1.8.3.2
next reply other threads:[~2014-05-16 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 20:37 Arman Uguray [this message]
2014-05-16 20:37 ` [RFC BlueZ 1/1] src/shared/gatt: Introduce bt_gatt skeleton Arman Uguray
2014-05-25 6:01 ` Marcel Holtmann
2014-05-28 6:20 ` Arman Uguray
2014-05-28 8:53 ` Marcel Holtmann
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=1400272636-31555-1-git-send-email-armansito@chromium.org \
--to=armansito@chromium.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).