From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v1 05/11] doc: describe the BAP coordinated set test cases
Date: Tue, 15 Sep 2026 17:15:22 -0400 [thread overview]
Message-ID: <20260915211528.1223784-6-luiz.dentz@gmail.com> (raw)
In-Reply-To: <20260915211528.1223784-1-luiz.dentz@gmail.com>
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Assisted-by: opencode:claude-opus-5
---
doc/functional-bap.rst | 101 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 101 insertions(+)
diff --git a/doc/functional-bap.rst b/doc/functional-bap.rst
index f9392bd2dbce..78411f4dd47d 100644
--- a/doc/functional-bap.rst
+++ b/doc/functional-bap.rst
@@ -288,3 +288,104 @@ test_bass_past_transport_acquire
The stream is verified on the delegator rather than through the
state of the MediaAssistant object, as an object created for a
local stream stays in the ``local`` state.
+
+COORDINATED SET
+===============
+
+Three hosts, with the two acceptors forming a coordinated set, one for
+each side, so the initiator has to discover both before it can stream:
+
+.. code-block::
+
+ +------------------------+ +------------------------+
+ | host1 | LE ACL | host0 |
+ | acceptor, left | <-------------- | initiator (central) |
+ | bluetoothctl -a auto | | bluetoothctl -a auto |
+ | bap-sink-lc3-left.bt | CIS 0x00 (LC3) | bap-source-lc3.bt |
+ | PAC Sink, Front Left | <============== | PAC Source endpoint |
+ +------------------------+ | |
+ | |
+ +------------------------+ LE ACL | |
+ | host2 | <-------------- | |
+ | acceptor, right | | |
+ | bluetoothctl -a auto | CIS 0x01 (LC3) | |
+ | bap-sink-lc3-right.bt | <============== | |
+ | PAC Sink, Front Right | | |
+ +------------------------+ +------------------------+
+
+ both acceptors share the same SIRK, so they are resolved into a
+ single set, and one CIS per member carries its channel
+
+ --> connection is initiated by ==> audio flows towards
+
+The acceptors run `bluetoothd` with the same SIRK, so the initiator
+resolves them into one set:
+
+.. code-block::
+
+ [CSIS]
+ SIRK = 861FAE703ED681F0C50B34155B6434FB
+ Size = 2
+ Rank = 1
+
+``Rank`` differs per member, 1 for the left and 2 for the right one,
+while ``SIRK`` and ``Size`` are the same, as they describe the set.
+
+Each acceptor also has to include the RSI in its advertising, with
+``advertise.rsi on``, otherwise the initiator cannot tell the two are
+members of the same set, and the resolved set does not appear as a
+**org.bluez.DeviceSet(5)** object.
+
+``client/scripts/bap-sink-lc3-left.bt`` on host1
+ Registers a local PAC Sink endpoint
+ (``00002bc9-0000-1000-8000-00805f9b34fb``) with LC3 and Front Left
+ as its only location, and advertises with the RSI.
+
+``client/scripts/bap-sink-lc3-right.bt`` on host2
+ As above, with Front Right as its only location.
+
+Each acceptor takes a single channel, unlike the stereo unicast case
+where one acceptor takes both: registering exactly one location makes
+`bluetoothctl` add the channel count to the capabilities, so a member
+is only ever configured for its own channel.
+
+test_bap_unicast_set_transport_created
+--------------------------------------
+
+:Setup: As above.
+
+:Steps:
+ 1. Start `bluetoothctl` with the scripts on the three hosts.
+ 2. Pair the initiator with each acceptor over LE.
+ 3. Initiator: ``endpoint.config <remote endpoint>
+ /local/endpoint/ep0 16_2_1``, for the remote PAC Sink endpoint
+ of each member.
+
+:Expected:
+ 1. ``Endpoint /local/endpoint/ep0 registered`` on the three hosts.
+ 2. ``Pairing successful`` for both, and the members are resolved
+ into a single set, reported as
+ ``[NEW] DeviceSet /org/bluez/hci0/set_<sirk>`` listing both
+ devices.
+ 3. A transport is created for each member, one per channel, i.e.
+ one for the Front Left endpoint and one for the Front Right
+ one.
+
+:Notes: Without the same SIRK, or without the RSI in the advertising,
+ the members are not resolved into a set and each is streamed to
+ on its own, which is not what this test covers.
+
+test_bap_unicast_set_transport_acquire
+--------------------------------------
+
+:Setup: As above, with the transports already created.
+
+:Steps: Initiator: ``transport.acquire <left> <right>``, for the
+ transports of both members.
+
+:Expected: ``Acquire successful: fd <fd> MTU <read>:<write>`` for each
+ transport, and both move to ``State: active``.
+
+:Notes: As for a stereo stream to a single acceptor, the CIS are only
+ created once every CIS of the CIG is ready, so the transports of
+ both members have to be acquired.
--
2.55.0
next prev parent reply other threads:[~2026-09-15 21:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 21:15 [PATCH BlueZ v1 00/11] Cover a BAP stream to a coordinated set Luiz Augusto von Dentz
2026-09-15 21:15 ` [PATCH BlueZ v1 01/11] shared/bass: add a ready callback Luiz Augusto von Dentz
2026-09-15 21:58 ` Cover a BAP stream to a coordinated set bluez.test.bot
2026-09-16 0:55 ` bluez.test.bot
2026-09-15 21:15 ` [PATCH BlueZ v1 02/11] bass: wait for the session to be ready before pushing a source Luiz Augusto von Dentz
2026-09-15 21:15 ` [PATCH BlueZ v1 03/11] test: functional: report what a test is waiting for Luiz Augusto von Dentz
2026-09-15 21:15 ` [PATCH BlueZ v1 04/11] test: functional: answer the notification registered by the victim Luiz Augusto von Dentz
2026-09-15 21:15 ` Luiz Augusto von Dentz [this message]
2026-09-15 21:15 ` [PATCH BlueZ v1 06/11] emulator: use the handle of the receiving side Luiz Augusto von Dentz
2026-09-15 21:15 ` [PATCH BlueZ v1 07/11] emulator: allow the maximum number of CIS of a CIG Luiz Augusto von Dentz
2026-09-15 21:15 ` [PATCH BlueZ v1 08/11] device: keep the long term key of both roles Luiz Augusto von Dentz
2026-09-15 21:15 ` [PATCH BlueZ v1 09/11] client: allow a capability with the auto agent Luiz Augusto von Dentz
2026-09-15 21:15 ` [PATCH BlueZ v1 10/11] test: functional: fail as soon as an operation fails Luiz Augusto von Dentz
2026-09-15 21:15 ` [PATCH BlueZ v1 11/11] test: functional: add the BAP coordinated set tests Luiz Augusto von Dentz
2026-09-16 18:30 ` [PATCH BlueZ v1 00/11] Cover a BAP stream to a coordinated set patchwork-bot+bluetooth
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=20260915211528.1223784-6-luiz.dentz@gmail.com \
--to=luiz.dentz@gmail.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