From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ 1/4] doc/advertising-api: Add support for setting Secondary Channel
Date: Fri, 15 Feb 2019 16:22:58 +0200 [thread overview]
Message-ID: <20190215142301.30909-1-luiz.dentz@gmail.com> (raw)
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
This enables reading and setting the Secondary Channel/PHY supported
by the controller.
---
doc/advertising-api.txt | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/doc/advertising-api.txt b/doc/advertising-api.txt
index cfce0f9a3..b0565eab2 100644
--- a/doc/advertising-api.txt
+++ b/doc/advertising-api.txt
@@ -129,6 +129,15 @@ Properties string Type
Timeout of the advertisement in seconds. This defines
the lifetime of the advertisement.
+ string SecondaryChannel [Experimental]
+
+ Secondary channel to be used. Primary channel is
+ always set to "1M" except when "Coded" is set.
+
+ Possible value: "1M" (default)
+ "2M"
+ "Coded"
+
LE Advertising Manager hierarchy
================================
@@ -190,3 +199,13 @@ Properties byte ActiveInstances
Possible values: "tx-power"
"appearance"
"local-name"
+
+ array{string} SupportedSecondaryChannels [Experimental]
+
+ List of supported Secondary channels. Secondary
+ channels can be used to advertise with the
+ corresponding PHY.
+
+ Possible values: "1M"
+ "2M"
+ "Coded"
--
2.17.2
next reply other threads:[~2019-02-15 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 14:22 Luiz Augusto von Dentz [this message]
2019-02-15 14:22 ` [PATCH BlueZ 2/4] advertising: Add implementation of SupportedSecondaryChannels Luiz Augusto von Dentz
2019-02-15 14:23 ` [PATCH BlueZ 3/4] advertising: Add implementation of SecondaryChannel Luiz Augusto von Dentz
2019-02-15 14:23 ` [PATCH BlueZ 4/4] client: Add advertise.secondary command Luiz Augusto von Dentz
2019-02-21 12:09 ` [PATCH BlueZ 1/4] doc/advertising-api: Add support for setting Secondary Channel Luiz Augusto von Dentz
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=20190215142301.30909-1-luiz.dentz@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).