diff mbox series

[Bluez,v4,3/3] doc/advertising-api: Add adv SupportedFeatures to doc

Message ID 20210316162044.Bluez.v4.3.Ieb6522963e3f54b0d63dd88ed3ce24a8942ed73e@changeid (mailing list archive)
State Accepted
Delegated to: Luiz Von Dentz
Headers show
Series Expose extended adv feature support via bluez API | expand

Commit Message

Daniel Winkler March 16, 2021, 11:22 p.m. UTC 
Add supported features to advertising dbus api.

Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
---

Changes in v4: None
Changes in v3:
- Rebased onto master

Changes in v2:
- Doc: Expect empty SupportedFeatures if no support available

 doc/advertising-api.txt | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
diff mbox series

Patch

diff --git a/doc/advertising-api.txt b/doc/advertising-api.txt
index 541c57004..6c0e52358 100644
--- a/doc/advertising-api.txt
+++ b/doc/advertising-api.txt
@@ -257,3 +257,21 @@  Properties	byte ActiveInstances
 				int16 MaxTxPower
 
 					Max advertising tx power (dBm)
+
+		array{string} SupportedFeatures [readonly,optional,Experimental]
+
+			List of supported platform features. If no features
+			are available on the platform, the SupportedFeatures
+			array will be empty.
+
+			Possible values: "CanSetTxPower"
+
+						Indicates whether platform can
+						specify tx power on each
+						advertising instance.
+
+					 "HardwareOffload"
+
+						Indicates whether multiple
+						advertising will be offloaded
+						to the controller.