From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 0ae2a2: shared/bap: handle inverted order of stop ready an...
Date: Sun, 22 Jun 2025 04:56:03 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/974594/000000-0ae2a2@github.com> (raw)
Branch: refs/heads/974594
Home: https://github.com/bluez/bluez
Commit: 0ae2a2f77f007a43ec075dc13d605851df1d6e4c
https://github.com/bluez/bluez/commit/0ae2a2f77f007a43ec075dc13d605851df1d6e4c
Author: Pauli Virtanen <pav@iki.fi>
Date: 2025-06-22 (Sun, 22 Jun 2025)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: handle inverted order of stop ready and disabling->qos
DISABLING->QOS transition and Receiver Stop Ready reply may arrive in
any order. BAP v1.0.2 (Sec. 5.6.5.1): CIS may be terminated by either
side after Receiver Stop Ready has successfully completed. However,
when we get the reply, the stream may be in either state.
Instead of client detaching the IO on stop ready reply, rely on
detaching IO on entering QOS, where Receiver Stop Ready has then
necessarily completed. On DISABLING, mark stream io as not connecting,
so that it gets detached even if CIS was not yet established.
Seen to occur with Samsung Galaxy Buds2 Pro, when it refuses Enable for
32/32kHz duplex on one of the earbuds.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-06-22 11:56 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/974594/000000-0ae2a2@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