From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] bcfaf5: audio: Add ability to force CIS transport Links pr...
Date: Mon, 20 Apr 2026 09:47:03 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1083418/000000-2a5c70@github.com> (raw)
Branch: refs/heads/1083418
Home: https://github.com/bluez/bluez
Commit: bcfaf58269f745f22fd00dff381e5b243e816e2d
https://github.com/bluez/bluez/commit/bcfaf58269f745f22fd00dff381e5b243e816e2d
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-04-20 (Mon, 20 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: b4d9604598d75c3636f378b814cea745d47be818
https://github.com/bluez/bluez/commit/b4d9604598d75c3636f378b814cea745d47be818
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-04-20 (Mon, 20 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: 2a5c70a0a783d8b745187ce3bd9a0e7006cffd06
https://github.com/bluez/bluez/commit/2a5c70a0a783d8b745187ce3bd9a0e7006cffd06
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-04-20 (Mon, 20 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/bcfaf58269f7%5E...2a5c70a0a783
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-20 16:47 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/1083418/000000-2a5c70@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