* [bluez/bluez] f6b70a: bap: Start BIG sync after receiving BIGInfo
@ 2026-07-27 4:44 github-actions[bot]
0 siblings, 0 replies; only message in thread
From: github-actions[bot] @ 2026-07-27 4:44 UTC (permalink / raw)
To: linux-bluetooth
Branch: refs/heads/1134824
Home: https://github.com/bluez/bluez
Commit: f6b70a1afbdf89527768b89de141e45d41255413
https://github.com/bluez/bluez/commit/f6b70a1afbdf89527768b89de141e45d41255413
Author: Yang Li <yang.li@amlogic.com>
Date: 2026-07-27 (Mon, 27 Jul 2026)
Changed paths:
M profiles/audio/bap.c
Log Message:
-----------
bap: Start BIG sync after receiving BIGInfo
The current implementation starts BIG sync before receiving a BIGInfo
report. According to the Bluetooth Core Specification, BIG sync should
only be initiated after BIGInfo has been received.
Starting BIG sync too early may cause unexpected controller behavior.
Trigger BIG sync from the BIGInfo callback, following the same approach
used by the short PA flow.
Fixes: https://github.com/bluez/bluez/issues/2345
Signed-off-by: Yang Li <yang.li@amlogic.com>
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-07-27 4:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-27 4:44 [bluez/bluez] f6b70a: bap: Start BIG sync after receiving BIGInfo github-actions[bot]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox