This patch adds the new scannable flag to the Add Extended Advertising
Parameters MGMT API documentation.
Reviewed-by: Alain Michaud <[email protected]>
Reviewed-by: Sonny Sasaka <[email protected]>
---
Changes in v2: None
doc/mgmt-api.txt | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt
index 1736ef009..cab1fffc5 100644
--- a/doc/mgmt-api.txt
+++ b/doc/mgmt-api.txt
@@ -3632,6 +3632,7 @@ Add Extended Advertising Parameters Command
13 The Timeout parameter should be used
14 The Interval parameters should be used
15 The Tx Power parameter should be used
+ 16 The advertisement will contain a scan response
When the connectable flag is set, then the controller will use
undirected connectable advertising. The value of the connectable
@@ -3708,6 +3709,10 @@ Add Extended Advertising Parameters Command
chosen by the controller. If the requested Tx Power is outside
the valid range, the registration will fail.
+ When flag bit 16 is enabled, it indicates that the subsequent request
+ to set advertising data will contain a scan response, and that the
+ parameters should set a PDU type that is scannable.
+
Re-adding an already existing instance (i.e. issuing the Add Extended
Advertising Parameters command with an Instance identifier of an
existing instance) will update that instance's configuration. In this
--
2.30.1.766.gb4fecdf3b7-goog