From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 5d9d39: audio: Add ability to force CIS transport Links pr...
Date: Thu, 23 Apr 2026 03:59:31 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1084652/000000-ed9b9a@github.com> (raw)
Branch: refs/heads/1084652
Home: https://github.com/bluez/bluez
Commit: 5d9d394b23b77074a7426dc86dc2738f0ac4a970
https://github.com/bluez/bluez/commit/5d9d394b23b77074a7426dc86dc2738f0ac4a970
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-04-23 (Thu, 23 Apr 2026)
Changed paths:
M profiles/audio/bap.c
M profiles/audio/transport.c
Log Message:
-----------
audio: Add ability to force CIS transport Links property
If bluetoothd is started in testing mode the Links property for CIS
is readwrite and can be used to force transport objects Links.
This can used to unlink transport objects by sending an empty array.
For unlinked transport objects, each transports needs to be acquired
separately.
This allows to pass PTS tests BAP/UCL/STR/BV-543-C and BV-546-C.
Commit: 5bb06b0f3ae0ede93d527685cfe02f35027a5b10
https://github.com/bluez/bluez/commit/5bb06b0f3ae0ede93d527685cfe02f35027a5b10
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-04-23 (Thu, 23 Apr 2026)
Changed paths:
M doc/org.bluez.MediaTransport.rst
Log Message:
-----------
doc: Add documentation for readwrite CIS transport Links property
This is only supported when bluetoothd is started in testing mode.
Commit: ed9b9a29eb03f91729ea5af221598fe257017d64
https://github.com/bluez/bluez/commit/ed9b9a29eb03f91729ea5af221598fe257017d64
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-04-23 (Thu, 23 Apr 2026)
Changed paths:
M client/player.c
Log Message:
-----------
client/player: Add support to unlink transports
This is used to pass PTS tests BAP/UCL/STR/BV-543-C and BV-546-C.
Compare: https://github.com/bluez/bluez/compare/5d9d394b23b7%5E...ed9b9a29eb03
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-23 10:59 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/1084652/000000-ed9b9a@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