From: Iulia Tanasescu <iulia.tanasescu@nxp.com>
To: linux-bluetooth@vger.kernel.org
Cc: claudia.rosu@nxp.com, mihai-octavian.urzica@nxp.com,
andrei.istodorescu@nxp.com, luiz.dentz@gmail.com,
Iulia Tanasescu <iulia.tanasescu@nxp.com>
Subject: [PATCH BlueZ 0/3] client/player: Make QoS sync_factor configurable
Date: Fri, 13 Dec 2024 13:31:10 +0200 [thread overview]
Message-ID: <20241213113113.64818-1-iulia.tanasescu@nxp.com> (raw)
This adds a new user input prompt when configuring a Broadcast Source
endpoint, to configure a QoS sync_factor value. This is useful for the
user to adjust how frequent PA announcements should be sent by the
Source, depending on scenario, instead of always using a hardcoded
value.
Since all BISes in a BIG must be configured with the same QoS settings,
a check is added in the BAP plugin, to ensure that the QoS matches for
all streams. Otherwise, connecting multiple BIS sockets bound for the
same BIG will fail.
Iulia Tanasescu (3):
lib: Add BT_ISO_SYNC_FACTOR
client/player: Make QoS sync_factor configurable
bap: Do not allow BIS QoS mismatch
client/player.c | 30 +++++++++-
client/scripts/broadcast-source.bt | 1 +
lib/bluetooth.h | 12 ++++
profiles/audio/bap.c | 88 +++++++++++++++++++++++++++++-
4 files changed, 127 insertions(+), 4 deletions(-)
base-commit: 92f3a3b108c22e3395c9dab0acefdfb894404cfe
--
2.43.0
next reply other threads:[~2024-12-13 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 11:31 Iulia Tanasescu [this message]
2024-12-13 11:31 ` [PATCH BlueZ 1/3] lib: Add BT_ISO_SYNC_FACTOR Iulia Tanasescu
2024-12-13 12:35 ` client/player: Make QoS sync_factor configurable bluez.test.bot
2024-12-13 11:31 ` [PATCH BlueZ 2/3] " Iulia Tanasescu
2024-12-13 11:31 ` [PATCH BlueZ 3/3] bap: Do not allow BIS QoS mismatch Iulia Tanasescu
2024-12-16 21:50 ` [PATCH BlueZ 0/3] client/player: Make QoS sync_factor configurable 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=20241213113113.64818-1-iulia.tanasescu@nxp.com \
--to=iulia.tanasescu@nxp.com \
--cc=andrei.istodorescu@nxp.com \
--cc=claudia.rosu@nxp.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=mihai-octavian.urzica@nxp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.