Linux bluetooth development
 help / color / mirror / Atom feed
From: chanyeol.park@samsung.com
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH v3 4/5] audio: Fix audio driver is not probed
Date: Tue, 09 Oct 2012 20:35:47 +0900	[thread overview]
Message-ID: <1349782548-27923-4-git-send-email-chanyeol.park@samsung.com> (raw)
In-Reply-To: <1349782548-27923-1-git-send-email-chanyeol.park@samsung.com>

From: Chan-yeol Park <chanyeol.park@samsung.com>

This patch fix the bugs that when handling an AVDTP incoming connection,
audio-a2dp driver is not probed because advanced audio UUID is missed.
---
 audio/manager.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/audio/manager.c b/audio/manager.c
index 26cd9bf..b052009 100644
--- a/audio/manager.c
+++ b/audio/manager.c
@@ -1093,7 +1093,8 @@ static struct btd_profile gateway_profile = {
 static struct btd_profile a2dp_profile = {
 	.name		= "audio-a2dp",
 
-	.remote_uuids	= BTD_UUIDS(A2DP_SOURCE_UUID, A2DP_SINK_UUID),
+	.remote_uuids	= BTD_UUIDS(A2DP_SOURCE_UUID, A2DP_SINK_UUID,
+							ADVANCED_AUDIO_UUID),
 	.device_probe	= a2dp_probe,
 	.device_remove	= audio_remove,
 
-- 
1.7.9.5


  parent reply	other threads:[~2012-10-09 11:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09 11:35 [PATCH v3 1/5] audio: Add check for vendor specific A2DP codec chanyeol.park
2012-10-09 11:35 ` [PATCH v3 2/5] avinfo: Replace definitions with a2dp-codecs.h's chanyeol.park
2012-10-09 11:35 ` [PATCH v3 3/5] avinfo: Print a2dp vendor codec info chanyeol.park
2012-10-09 11:35 ` chanyeol.park [this message]
2012-10-09 11:35 ` [PATCH v3 5/5] audio: Remove redundant procedure when a2dp connect chanyeol.park
2012-10-09 21:33 ` [PATCH v3 1/5] audio: Add check for vendor specific A2DP codec 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=1349782548-27923-4-git-send-email-chanyeol.park@samsung.com \
    --to=chanyeol.park@samsung.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