From: iulia-tanasescu <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 4b4c93: shared/bap: Add support to register bis callbacks
Date: Thu, 27 Feb 2025 10:19:14 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/f4617c-d68dc1@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 4b4c9383d58ad63faf18908e5d3864d52dc686c1
https://github.com/bluez/bluez/commit/4b4c9383d58ad63faf18908e5d3864d52dc686c1
Author: Iulia Tanasescu <iulia.tanasescu@nxp.com>
Date: 2025-02-27 (Thu, 27 Feb 2025)
Changed paths:
M src/shared/bap.c
M src/shared/bap.h
Log Message:
-----------
shared/bap: Add support to register bis callbacks
This adds support for registering BIS probe/remove calllbacks with
shared/bap. This is needed by the BAP Broadcast Assistant (BASS Client)
implementation, so that the BAP plugin can notify BISes discovered
after parsing the BASE to BASS, avoiding direct function calls
between plugins.
Commit: f49953d96fab77fccf80ab5af56538ac749c3489
https://github.com/bluez/bluez/commit/f49953d96fab77fccf80ab5af56538ac749c3489
Author: Iulia Tanasescu <iulia.tanasescu@nxp.com>
Date: 2025-02-27 (Thu, 27 Feb 2025)
Changed paths:
M profiles/audio/bass.c
Log Message:
-----------
bass: Create BASS session with Broadcasters
In the BASS plugin, BAP sessions created with scanned Broadcasters are
notified in the bap attached callback. This creates BASS data for these
devices as well, to internally keep information about the sessions.
Commit: d68dc1fd03bc86a5427ca8738c04fb692cc95263
https://github.com/bluez/bluez/commit/d68dc1fd03bc86a5427ca8738c04fb692cc95263
Author: Iulia Tanasescu <iulia.tanasescu@nxp.com>
Date: 2025-02-27 (Thu, 27 Feb 2025)
Changed paths:
M profiles/audio/bap.c
M profiles/audio/bass.c
M profiles/audio/bass.h
Log Message:
-----------
bass: Register bis probe/remove callbacks
This removes the BASS add/remove stream APIs and uses shared/bap to
register BIS probe/remove callbacks instead, to avoid making direct
calls between plugins.
Compare: https://github.com/bluez/bluez/compare/f4617c531abe...d68dc1fd03bc
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-02-27 18:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/master/f4617c-d68dc1@github.com \
--to=noreply@github.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