* [bluez/bluez] ddb5d4: media: use custom DBus timeouts only when remote s...
@ 2026-06-14 12:08 Pauli Virtanen
0 siblings, 0 replies; only message in thread
From: Pauli Virtanen @ 2026-06-14 12:08 UTC (permalink / raw)
To: linux-bluetooth
Branch: refs/heads/1111256
Home: https://github.com/bluez/bluez
Commit: ddb5d4c135465f5645d42dbe978912fbf0552ee1
https://github.com/bluez/bluez/commit/ddb5d4c135465f5645d42dbe978912fbf0552ee1
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-06-14 (Sun, 14 Jun 2026)
Changed paths:
M profiles/audio/media.c
Log Message:
-----------
media: use custom DBus timeouts only when remote side is waiting
Under high system load (VM instance on boot) it's observed the 3 sec
timeout BlueZ uses for BAP broadcast SetConfiguration may be missed by
Wireplumber, as these are set up immediately on startup together with
any other setup (eg ALSA) that may need time.
There's no actual need for using a short custom timeout in BlueZ for
this, as in this case there is no remote side that is waiting for a reply.
Fix by limiting custom timeouts to cases where there is a waiting
remote, and use separate defines for A2DP and BAP.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-06-14 12:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-06-14 12:08 [bluez/bluez] ddb5d4: media: use custom DBus timeouts only when remote s Pauli Virtanen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox