From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 31c0e0: bap: Start BIG sync after receiving BIGInfo
Date: Fri, 24 Jul 2026 03:37:12 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1133845/000000-31c0e0@github.com> (raw)
Branch: refs/heads/1133845
Home: https://github.com/bluez/bluez
Commit: 31c0e034141e0066a32bdf19f7b29194393c03a5
https://github.com/bluez/bluez/commit/31c0e034141e0066a32bdf19f7b29194393c03a5
Author: Yang Li <yang.li@amlogic.com>
Date: 2026-07-24 (Fri, 24 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
reply other threads:[~2026-07-24 10:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1133845/000000-31c0e0@github.com \
--to=noreply@github.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