From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH v2 1/8] doc/gatt-api: Add Handle property
Date: Thu, 31 Jan 2019 14:17:58 +0200 [thread overview]
Message-ID: <CABBYNZ+ygRJJmc+4ckU32xQzxwKxRXy2PoVds6LbczuwK3mZjQ@mail.gmail.com> (raw)
In-Reply-To: <20190130135424.2091-1-luiz.dentz@gmail.com>
Hi,
On Wed, Jan 30, 2019 at 3:54 PM Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
>
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> When acting as server it is useful to select where to allocate the
> handle for an attribute so it can be restored in the same position when
> restarting the daemon or rebooting the system.
>
> In order to do that the application also needs to know in which handle
> the attribute is allocated the very first time it is registered, this
> also allows for a better integration with PTS and tools like auto-pts
> which needs to know the handles where the attributes have been
> allocated.
> ---
> v2: Fixes inserting characteristics and descriptors with handle 0x0000,
> add a patch to enable list-attribute to list with local attributes and
> print changes to attribute Handle property.
>
> doc/gatt-api.txt | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/doc/gatt-api.txt b/doc/gatt-api.txt
> index 8dda60b8a..491eb026a 100644
> --- a/doc/gatt-api.txt
> +++ b/doc/gatt-api.txt
> @@ -50,6 +50,14 @@ Properties string UUID [read-only]
> Array of object paths representing the included
> services of this service.
>
> + uint16 Handle [read-write, optional] (Server Only)
> +
> + Service handle. When available in the server it
> + would attempt to use to allocate into the database
> + which may fail, to auto allocate the value 0x0000
> + shall be used which will cause the allocated handle to
> + be set once registered.
> +
>
> Characteristic hierarchy
> ========================
> @@ -257,6 +265,14 @@ Properties string UUID [read-only]
> "secure-write" (Server only)
> "authorize"
>
> + uint16 Handle [read-write, optional] (Server Only)
> +
> + Characteristic handle. When available in the server it
> + would attempt to use to allocate into the database
> + which may fail, to auto allocate the value 0x0000
> + shall be used which will cause the allocated handle to
> + be set once registered.
> +
> Characteristic Descriptors hierarchy
> ====================================
>
> @@ -332,6 +348,14 @@ Properties string UUID [read-only]
> "secure-write" (Server Only)
> "authorize"
>
> + uint16 Handle [read-write, optional] (Server Only)
> +
> + Characteristic handle. When available in the server it
> + would attempt to use to allocate into the database
> + which may fail, to auto allocate the value 0x0000
> + shall be used which will cause the allocated handle to
> + be set once registered.
> +
> GATT Profile hierarchy
> =====================
>
> --
> 2.17.2
Applied.
--
Luiz Augusto von Dentz
prev parent reply other threads:[~2019-01-31 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 13:54 [PATCH v2 1/8] doc/gatt-api: Add Handle property Luiz Augusto von Dentz
2019-01-30 13:54 ` [PATCH v2 2/8] shared/gatt-db: Allow passing 0 as handle to gatt_db_insert_* Luiz Augusto von Dentz
2019-01-30 13:54 ` [PATCH v2 3/8] gatt: Implement Handle property Luiz Augusto von Dentz
2019-01-30 13:54 ` [PATCH v2 4/8] gatt: Write back the handle to " Luiz Augusto von Dentz
2019-01-30 13:54 ` [PATCH v2 5/8] client: Enable Handle property for GATT attributes Luiz Augusto von Dentz
2019-01-30 13:54 ` [PATCH v2 6/8] client: Enable setting attribute handles Luiz Augusto von Dentz
2019-01-30 13:54 ` [PATCH v2 7/8] client: Enable list-attributes to print local attributes Luiz Augusto von Dentz
2019-01-30 13:54 ` [PATCH v2 8/8] client: Don't expose pointer value in attribute path Luiz Augusto von Dentz
2019-01-31 12:17 ` Luiz Augusto von Dentz [this message]
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=CABBYNZ+ygRJJmc+4ckU32xQzxwKxRXy2PoVds6LbczuwK3mZjQ@mail.gmail.com \
--to=luiz.dentz@gmail.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).