From: "Frédéric Danis" <frederic.danis@collabora.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v2 2/3] doc: Add documentation for CIS transport Desynchronized property
Date: Tue, 28 Apr 2026 10:03:13 +0200 [thread overview]
Message-ID: <20260428080314.180777-3-frederic.danis@collabora.com> (raw)
In-Reply-To: <20260428080314.180777-1-frederic.danis@collabora.com>
This is only supported when bluetoothd is started in testing mode.
Assisted-by: GPT:GPT-5.3-Codex
---
doc/org.bluez.MediaTransport.rst | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/doc/org.bluez.MediaTransport.rst b/doc/org.bluez.MediaTransport.rst
index 81cf9e4da..e50ec3f20 100644
--- a/doc/org.bluez.MediaTransport.rst
+++ b/doc/org.bluez.MediaTransport.rst
@@ -357,3 +357,17 @@ Possible values for both Unicast and Broadcast:
:byte Retransmissions:
Indicates configured retransmissions.
+
+boolean Desynchronized [readwrite, optional, CIS only, testing, experimental]
+`````````````````````````````````````````````````````````````````````````````
+
+Available only when D-Bus testing interfaces are enabled and the transport has
+the **Links** property.
+
+Controls whether linked transports are acquired together.
+
+When set to False (default), acquiring one linked transport automatically
+acquires all links.
+
+When set to True, links are not acquired automatically and each link must be
+acquired separately.
--
2.43.0
next prev parent reply other threads:[~2026-04-28 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 8:03 [PATCH BlueZ v2 0/3] Add ability to desynchronized transports for PTS tests Frédéric Danis
2026-04-28 8:03 ` [PATCH BlueZ v2 1/3] audio: Add ability to desynchronized linked transport Frédéric Danis
2026-04-28 11:02 ` Add ability to desynchronized transports for PTS tests bluez.test.bot
2026-04-28 8:03 ` Frédéric Danis [this message]
2026-04-28 8:03 ` [PATCH BlueZ v2 3/3] client/player: Add support to desynchronize linked transports Frédéric Danis
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=20260428080314.180777-3-frederic.danis@collabora.com \
--to=frederic.danis@collabora.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