linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikel Astiz <mikel.astiz.oss@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Mikel Astiz <mikel.astiz@bmw-carit.de>
Subject: [RFC BlueZ v0 1/5] doc: Add D-Bus signal to provide disconnect reason
Date: Mon, 14 May 2012 17:33:00 +0200	[thread overview]
Message-ID: <1337009584-17181-2-git-send-email-mikel.astiz.oss@gmail.com> (raw)
In-Reply-To: <1337009584-17181-1-git-send-email-mikel.astiz.oss@gmail.com>

From: Mikel Astiz <mikel.astiz@bmw-carit.de>

This signal is needed to propagate the reason in case of disconnection.
Some use-cases require this information, for example if there is a
policy to automatically reconnect in case of connection timeout.
---
 doc/device-api.txt |   14 ++++++++++++++
 1 files changed, 14 insertions(+), 0 deletions(-)

diff --git a/doc/device-api.txt b/doc/device-api.txt
index 4a170e4..58b0957 100644
--- a/doc/device-api.txt
+++ b/doc/device-api.txt
@@ -108,6 +108,20 @@ Signals		PropertyChanged(string name, variant value)
 			disconnection to a remote device has been requested.
 			The actual disconnection will happen 2 seconds later.
 
+		Disconnected(uint8 reason)
+
+			This signal will be sent when the low-level ACL link
+			is disconnected, either because is was explicitly
+			requested (locally initiated) or not.
+
+			The actual reason of the disconnection is given by
+			the first parameter, which is a 8-bit error code as
+			defined in the HCI specification (or 0 if the
+			disconnection is due to a previous request).
+
+			This signal will be sent just before the corresponding
+			state property change to "disconnected".
+
 		NodeCreated(object node)
 
 			Parameter is object path of created device node.
-- 
1.7.7.6


  reply	other threads:[~2012-05-14 15:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 15:32 [RFC BlueZ v0 0/5] ACL disconnect reason Mikel Astiz
2012-05-14 15:33 ` Mikel Astiz [this message]
2012-05-14 15:33 ` [RFC BlueZ v0 2/5] Use defines instead of magic numbers Mikel Astiz
2012-07-18 11:49   ` Mikel Astiz
2012-07-18 12:23     ` Johan Hedberg
2012-05-14 15:33 ` [RFC BlueZ v0 3/5] Propagate disconnect reason to adapter Mikel Astiz
2012-05-14 15:33 ` [RFC BlueZ v0 4/5] Propagate disconnect reason to device Mikel Astiz
2012-05-14 15:33 ` [RFC BlueZ v0 5/5] Send D-Bus signal to propagate disconnect reason Mikel Astiz
2012-05-14 17:00 ` [RFC BlueZ v0 0/5] ACL " Luiz Augusto von Dentz
2012-05-15  6:46   ` Mikel Astiz
2012-05-15  8:10     ` Luiz Augusto von Dentz
2012-05-15  8:45       ` Mikel Astiz
2012-05-15  9:58         ` Luiz Augusto von Dentz
2012-05-16  7:12           ` Mikel Astiz
2012-05-16 14:28             ` Mike
2012-05-17 13:41               ` Luiz Augusto von Dentz
2012-05-17 14:00                 ` Mike

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=1337009584-17181-2-git-send-email-mikel.astiz.oss@gmail.com \
    --to=mikel.astiz.oss@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mikel.astiz@bmw-carit.de \
    /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).