Thread (4 messages) 4 messages, 1 author, 2016-08-25

[PATCH BlueZ 3/3] doc/device-api: Document Connect behavior for dual-mode

flat view
STALE3712d

From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date: 2016-08-23 10:17:48
Subsystem: the rest · Maintainer: Linus Torvalds

From: Luiz Augusto von Dentz <redacted>

Adds description of how Device1.Connect behave with dual-mode devices.
---
 doc/device-api.txt | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
diff --git a/doc/device-api.txt b/doc/device-api.txt
index 087efb9..3938539 100644
--- a/doc/device-api.txt
+++ b/doc/device-api.txt
@@ -21,6 +21,20 @@ Methods		void Connect()
 			If at least one profile was connected successfully this
 			method will indicate success.
 
+			For dual-mode devices only one bearer is connected at
+			time, the conditions are in the following order:
+
+				1. Connect the disconnected bearer if already
+				connected.
+
+				2. Connect first the bonded bearer. If no
+				bearers are bonded or both both skip and check
+				latest seen bearer.
+
+				3. Connect last seen bearer, in case the
+				timestamps are the same BR/EDR takes
+				precedence.
+
 			Possible errors: org.bluez.Error.NotReady
 					 org.bluez.Error.Failed
 					 org.bluez.Error.InProgress
-- 
2.7.4
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help