Skip to contentSkip to conversation

doc/advertising-api: Add support for setting Secondary Channel

RFC New Luiz Augusto von Dentz 1 participant 1 message Feb 15, 2019 Bluetooth drivers

lore
Share & tools
lore

Luiz Augusto von Dentz

author maintainer
#0 lore raw

RFC 1/1 doc/advertising-api: Add support for setting Secondary Channel

From: Luiz Augusto von Dentz <[email protected]>

This enables reading and setting the Secondary Channel/PHY supported by the controller.

---
 doc/advertising-api.txt | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
doc/advertising-api.txt +19 -0
index cfce0f9a3..5cc76f49e 100644
@@ -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"
Signature · 1 line
2.17.2