public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH BlueZ v2] a2dp: connect source profile after sink
@ 2026-02-16 16:17 Pauli Virtanen
  2026-02-16 17:16 ` [BlueZ,v2] " bluez.test.bot
  2026-02-17 14:50 ` [PATCH BlueZ v2] " patchwork-bot+bluetooth
  0 siblings, 2 replies; 3+ messages in thread
From: Pauli Virtanen @ 2026-02-16 16:17 UTC (permalink / raw)
  To: linux-bluetooth; +Cc: Pauli Virtanen

Since cdcd845f87ee the order in which profiles with the same priority
are connected is the same order as btd_profile_register() is called,
instead of being the opposite order.  When initiating connections, we
want to prefer a2dp-sink profile over a2dp-source, as connecting both at
the same time does not work currently.

Add .after_services to specify the order.

Fixes: https://github.com/bluez/bluez/issues/1898
---
 profiles/audio/a2dp.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/profiles/audio/a2dp.c b/profiles/audio/a2dp.c
index 7a37003a2..c7e0fc75c 100644
--- a/profiles/audio/a2dp.c
+++ b/profiles/audio/a2dp.c
@@ -3769,6 +3769,9 @@ static struct btd_profile a2dp_source_profile = {
 
 	.adapter_probe	= a2dp_sink_server_probe,
 	.adapter_remove	= a2dp_sink_server_remove,
+
+	/* Connect source after sink, to prefer sink when conflicting */
+	.after_services = BTD_PROFILE_UUID_CB(NULL, A2DP_SINK_UUID),
 };
 
 static struct btd_profile a2dp_sink_profile = {
-- 
2.53.0


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* RE: [BlueZ,v2] a2dp: connect source profile after sink
  2026-02-16 16:17 [PATCH BlueZ v2] a2dp: connect source profile after sink Pauli Virtanen
@ 2026-02-16 17:16 ` bluez.test.bot
  2026-02-17 14:50 ` [PATCH BlueZ v2] " patchwork-bot+bluetooth
  1 sibling, 0 replies; 3+ messages in thread
From: bluez.test.bot @ 2026-02-16 17:16 UTC (permalink / raw)
  To: linux-bluetooth, pav

[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]

This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1054617

---Test result---

Test Summary:
CheckPatch                    PENDING   0.52 seconds
GitLint                       PENDING   0.43 seconds
BuildEll                      PASS      21.07 seconds
BluezMake                     PASS      659.15 seconds
MakeCheck                     PASS      18.73 seconds
MakeDistcheck                 PASS      248.08 seconds
CheckValgrind                 PASS      299.93 seconds
CheckSmatch                   PASS      363.60 seconds
bluezmakeextell               PASS      185.67 seconds
IncrementalBuild              PENDING   0.35 seconds
ScanBuild                     PASS      1048.60 seconds

Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:

##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:

##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH BlueZ v2] a2dp: connect source profile after sink
  2026-02-16 16:17 [PATCH BlueZ v2] a2dp: connect source profile after sink Pauli Virtanen
  2026-02-16 17:16 ` [BlueZ,v2] " bluez.test.bot
@ 2026-02-17 14:50 ` patchwork-bot+bluetooth
  1 sibling, 0 replies; 3+ messages in thread
From: patchwork-bot+bluetooth @ 2026-02-17 14:50 UTC (permalink / raw)
  To: Pauli Virtanen; +Cc: linux-bluetooth

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Mon, 16 Feb 2026 18:17:08 +0200 you wrote:
> Since cdcd845f87ee the order in which profiles with the same priority
> are connected is the same order as btd_profile_register() is called,
> instead of being the opposite order.  When initiating connections, we
> want to prefer a2dp-sink profile over a2dp-source, as connecting both at
> the same time does not work currently.
> 
> Add .after_services to specify the order.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2] a2dp: connect source profile after sink
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=066a164a524e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-02-17 14:50 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-02-16 16:17 [PATCH BlueZ v2] a2dp: connect source profile after sink Pauli Virtanen
2026-02-16 17:16 ` [BlueZ,v2] " bluez.test.bot
2026-02-17 14:50 ` [PATCH BlueZ v2] " patchwork-bot+bluetooth

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox