From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] f8f43f: audio: Add ability to force CIS transport Links pr...
Date: Thu, 23 Apr 2026 01:13:30 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1084559/000000-f44f8c@github.com> (raw)
Branch: refs/heads/1084559
Home: https://github.com/bluez/bluez
Commit: f8f43f9bcd6f3507e7e258fb7abeda0e43168a16
https://github.com/bluez/bluez/commit/f8f43f9bcd6f3507e7e258fb7abeda0e43168a16
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: 7bd76e0b3708985aade4e5db8457142e19a973fc
https://github.com/bluez/bluez/commit/7bd76e0b3708985aade4e5db8457142e19a973fc
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: f44f8c555c8b923e7b8f1c01b71a9e68a79477b2
https://github.com/bluez/bluez/commit/f44f8c555c8b923e7b8f1c01b71a9e68a79477b2
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/f8f43f9bcd6f%5E...f44f8c555c8b
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-23 8:13 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/1084559/000000-f44f8c@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