public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Frédéric Danis" <frederic.danis@collabora.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v2 0/3] Add ability to desynchronized transports for PTS tests
Date: Tue, 28 Apr 2026 10:03:11 +0200	[thread overview]
Message-ID: <20260428080314.180777-1-frederic.danis@collabora.com> (raw)

If bluetoothd is started in testing mode a new Desynchronized property
is added to org.bluez.MediaTransport1, allowing to prevent automatic
acquire of linked transport objects.

When desynchronized, each transports needs to be acquired separately.

This allows to pass PTS tests BAP/UCL/STR/BV-543-C and BV-546-C which
requires to connect the ISO streams with one ASE in "Enable" state
while the other is in "Config QoS" state.

v1->v2:
  - renamed 'desynchronized' to 'desync' in profiles/audio/transport.c
  - added a comment for the 'desync' variable of 'struct bap_transport'
    in profiles/audio/transport.c 

Frédéric Danis (3):
  audio: Add ability to desynchronized linked transport
  doc: Add documentation for CIS transport Desynchronized property
  client/player: Add support to desynchronize linked transports

 client/player.c                  |  76 +++++++++++++++++++-
 doc/org.bluez.MediaTransport.rst |  14 ++++
 profiles/audio/transport.c       | 116 +++++++++++++++++++++++++++----
 3 files changed, 192 insertions(+), 14 deletions(-)

-- 
2.43.0


             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 Frédéric Danis [this message]
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 ` [PATCH BlueZ v2 2/3] doc: Add documentation for CIS transport Desynchronized property Frédéric Danis
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-1-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