From: Frédéric Dalleau <frederic.dalleau@linux.intel.com>
Date: Tue, 4 Oct 2011 07:37:22 +0000 (+0200)
Subject: bluetooth: Do not unload module-bluetooth-device on ERR or HUP
X-Git-Tag: 1.0_branch~257
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=54f3b9a6fa47b618a31474d3786ed26248d3091d;p=profile%2Fivi%2Fpulseaudio.git

bluetooth: Do not unload module-bluetooth-device on ERR or HUP

This happens in the following scenario :
An HandsfreeGateway connects RFCOMM and then SCO. A card appears in
PA and can be used. If for some reason, SCO is disconnected,
module-bluetooth-device is unloaded. The card will disappear, even
if RFCOMM is still connected. After that, it is not possible to
connect SCO again from PA.
---

diff --git a/src/modules/bluetooth/module-bluetooth-device.c b/src/modules/bluetooth/module-bluetooth-device.c
index ac76a19..81abcd6 100644
--- a/src/modules/bluetooth/module-bluetooth-device.c
+++ b/src/modules/bluetooth/module-bluetooth-device.c
@@ -1721,7 +1721,6 @@ static void thread_func(void *userdata) {
 fail:
     /* If this was no regular exit from the loop we have to continue processing messages until we receive PA_MESSAGE_SHUTDOWN */
     pa_log_debug("IO thread failed");
-    pa_asyncmsgq_post(u->thread_mq.outq, PA_MSGOBJECT(u->core), PA_CORE_MESSAGE_UNLOAD_MODULE, u->module, 0, NULL, NULL);
     pa_asyncmsgq_wait_for(u->thread_mq.inq, PA_MESSAGE_SHUTDOWN);
 
 finish: