From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v1 3/3] bass: Fix restricting the BIS indexes to 1 as assistant
Date: Thu, 9 Oct 2025 12:21:11 -0400 [thread overview]
Message-ID: <20251009162111.221677-3-luiz.dentz@gmail.com> (raw)
In-Reply-To: <20251009162111.221677-1-luiz.dentz@gmail.com>
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
MediaAssistant are created per BIS which creates a problem since
MediaAssistant.Push could only push one index at the time, so instead
of always using the index use 0xFFFFFF (no preference) and leave it up
to the delegator to decide.
---
profiles/audio/bass.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/profiles/audio/bass.c b/profiles/audio/bass.c
index b7d39165fb13..70ef6f932ec7 100644
--- a/profiles/audio/bass.c
+++ b/profiles/audio/bass.c
@@ -1034,7 +1034,10 @@ static DBusMessage *push(DBusConnection *conn, DBusMessage *msg,
util_iov_append(&iov, &meta_len, sizeof(meta_len));
}
- bis_sync = (1 << (assistant->bis - 1));
+ /* Use 0xFFFFFFFF to indicate no preference (any BIS index) to allow
+ * delegators to sync with BIG with multiple BIS
+ */
+ bis_sync = 0xFFFFFFFF;
meta_len = assistant->meta->iov_len;
util_iov_append(&iov, &bis_sync, sizeof(bis_sync));
--
2.51.0
next prev parent reply other threads:[~2025-10-09 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 16:21 [PATCH BlueZ v1 1/3] monitor: Fix instance where BN is printed as PTO Luiz Augusto von Dentz
2025-10-09 16:21 ` [PATCH BlueZ v1 2/3] client/player: Fix prompting for bcode when one is already set Luiz Augusto von Dentz
2025-10-09 16:21 ` Luiz Augusto von Dentz [this message]
2025-10-09 17:44 ` [BlueZ,v1,1/3] monitor: Fix instance where BN is printed as PTO bluez.test.bot
2025-10-09 19:40 ` [PATCH BlueZ v1 1/3] " 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=20251009162111.221677-3-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