linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ 3/3] doc/device-api: Document Connect behavior for dual-mode
Date: Tue, 23 Aug 2016 13:17:48 +0300	[thread overview]
Message-ID: <1471947468-12696-3-git-send-email-luiz.dentz@gmail.com> (raw)
In-Reply-To: <1471947468-12696-1-git-send-email-luiz.dentz@gmail.com>

From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

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


  parent reply	other threads:[~2016-08-23 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 10:17 [PATCH BlueZ 1/3] core/device: Fix marking auto-connect flag Luiz Augusto von Dentz
2016-08-23 10:17 ` [PATCH BlueZ 2/3] core/device: Prefer bonded bearers when connecting Luiz Augusto von Dentz
2016-08-23 10:17 ` Luiz Augusto von Dentz [this message]
2016-08-25 12:59 ` [PATCH BlueZ 1/3] core/device: Fix marking auto-connect flag Luiz Augusto von Dentz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1471947468-12696-3-git-send-email-luiz.dentz@gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).