From: Archie Pusaka <[email protected]>
Userspace should use this new flag to decide whether to do the remote
name resolving or not.
---
Changes in v3:
* Update the flag name to be more inlined with the spec.
Changes in v2:
* Update docs to reflect not sending DONT_CARE flag behavior.
doc/mgmt-api.txt | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt
index 97d33e30a1..845031b017 100644
--- a/doc/mgmt-api.txt
+++ b/doc/mgmt-api.txt
@@ -4089,6 +4089,7 @@ Device Connected Event
1 Legacy Pairing
2 Reserved (not in use)
3 Initiated Connection
+ 4 Reserved (not in use)
Device Disconnected Event
@@ -4263,6 +4264,7 @@ Device Found Event
1 Legacy Pairing
2 Not Connectable
3 Reserved (not in use)
+ 4 Name Request Failed
For the RSSI field a value of 127 indicates that the RSSI is
not available. That can happen with Bluetooth 1.1 and earlier
@@ -4285,6 +4287,11 @@ Device Found Event
accept any connections. This can be indicated by Low Energy
devices that are in broadcaster role.
+ The Name Request Failed flag indicates that name resolving
+ procedure has ended with failure for this device. The user space
+ should use this information to determine when is a good time to
+ retry the name resolving procedure.
+
Discovering Event
=================
--
2.34.0.rc1.387.gb447b232ab-goog