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: [PATCH v2 3/3] audio: do not disconnect on gateway SCO failure
Date: Tue, 14 Feb 2012 10:06:34 +0100	[thread overview]
Message-ID: <1329210394-31405-4-git-send-email-mikel.astiz.oss@gmail.com> (raw)
In-Reply-To: <1329210394-31405-1-git-send-email-mikel.astiz.oss@gmail.com>

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

Failure on BlueZ-initiated SCO requests should not drop the RFCOMM
connection to the gateway. Instead, considering the stream as suspended
should be enough.
---
 audio/gateway.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/audio/gateway.c b/audio/gateway.c
index bde3e02..163f7b5 100644
--- a/audio/gateway.c
+++ b/audio/gateway.c
@@ -255,7 +255,7 @@ static void sco_connect_cb(GIOChannel *chan, GError *err, gpointer user_data)
 
 	if (err) {
 		error("sco_connect_cb(): %s", err->message);
-		gateway_close(dev);
+		gateway_suspend_stream(dev);
 		return;
 	}
 
-- 
1.7.6.5


  parent reply	other threads:[~2012-02-14  9:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14  9:06 [PATCH v2 0/3] Minor audio-related fixes Mikel Astiz
2012-02-14  9:06 ` [PATCH v2 1/3] audio: gateway_unlock together with in_use = FALSE Mikel Astiz
2012-02-14  9:28   ` Luiz Augusto von Dentz
2012-02-14  9:06 ` [PATCH v2 2/3] a2dp: return NotSupported error if no server found Mikel Astiz
2012-02-14  9:29   ` Luiz Augusto von Dentz
2012-02-14  9:06 ` Mikel Astiz [this message]
2012-02-14  9:29   ` [PATCH v2 3/3] audio: do not disconnect on gateway SCO failure Luiz Augusto von Dentz
2012-02-14 10:49 ` [PATCH v2 0/3] Minor audio-related fixes Johan Hedberg

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=1329210394-31405-4-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).