* [RFC BlueZ] doc/advertising-api: Add support for setting Secondary Channel
@ 2019-02-15 10:14 Luiz Augusto von Dentz
0 siblings, 0 replies; only message in thread
From: Luiz Augusto von Dentz @ 2019-02-15 10:14 UTC (permalink / raw)
To: linux-bluetooth
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..5cc76f49e 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} SupportedSecondaryChannel [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
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2019-02-15 10:14 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-15 10:14 [RFC BlueZ] doc/advertising-api: Add support for setting Secondary Channel Luiz Augusto von Dentz
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).