From: "Šimon Mikuda" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 80ec1f: test-bap: Fix using BT_ISO_QOS_CIG_UNSET for CIS_ID
Date: Mon, 15 Jun 2026 14:16:50 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/9c36e4-5297cf@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 80ec1f9d01c44768219c2842795652c6b6bb291c
https://github.com/bluez/bluez/commit/80ec1f9d01c44768219c2842795652c6b6bb291c
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-15 (Mon, 15 Jun 2026)
Changed paths:
M unit/test-bap.c
Log Message:
-----------
test-bap: Fix using BT_ISO_QOS_CIG_UNSET for CIS_ID
Although there are the same value the proper define is
BT_ISO_QOS_CIS_UNSET.
Commit: 64ae65d8958e67fb65f7413ef4ceab2ad51a6b28
https://github.com/bluez/bluez/commit/64ae65d8958e67fb65f7413ef4ceab2ad51a6b28
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-15 (Mon, 15 Jun 2026)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Initialize ucast/bcast IDs as unset
Also change some lines where CIS should be used instead of CIG.
Commit: 5297cf2b6af6970e12081e20f1a978c2bf52fd1f
https://github.com/bluez/bluez/commit/5297cf2b6af6970e12081e20f1a978c2bf52fd1f
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-15 (Mon, 15 Jun 2026)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Don't link server ucast streams before CIS IDs are assigned
bap_ucast_io_link pairs streams whose CIG/CIS IDs match, but the IDs
are unset in Codec Configured state, so a Sink and Source bound for
different CISes get linked. The stray link later propagates a
disconnect to the wrong ASE and breaks Receiver Start Ready.
Skip linking until QoS Configured assigns the IDs.
Fixes PTS test BAP/USR/STR/BV-362-C
Compare: https://github.com/bluez/bluez/compare/9c36e4189e32...5297cf2b6af6
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-15 21:16 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/master/9c36e4-5297cf@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