From: Andrei Istodorescu <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 98818d: shared/bap: Update stream management to avoid PACs
Date: Thu, 16 May 2024 10:36:57 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/d9de30-745f32@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 98818da25b2329dd0ff82009c167724df19db880
https://github.com/bluez/bluez/commit/98818da25b2329dd0ff82009c167724df19db880
Author: Andrei Istodorescu <andrei.istodorescu@nxp.com>
Date: 2024-05-16 (Thu, 16 May 2024)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Update stream management to avoid PACs
Remove PAC logic for BAP Broadcast Sink stream creation.
Commit: db8c96059c02fefd232d49dcbeb16d6b22481100
https://github.com/bluez/bluez/commit/db8c96059c02fefd232d49dcbeb16d6b22481100
Author: Andrei Istodorescu <andrei.istodorescu@nxp.com>
Date: 2024-05-16 (Thu, 16 May 2024)
Changed paths:
M src/shared/bap.c
M src/shared/bap.h
Log Message:
-----------
shared/bap: Add function to check the validity of a BIS
Add utilitary function to check if the information from a BIS is matching
the capabilities in bt_bap. This utilitary is used when parsing the BASE
data so that we can decide if we create a new setup/stream/transport for
it, or advance to the next BIS.
Commit: 32d147959b8e7de3fd3d4dc7d208b25f0f2d652e
https://github.com/bluez/bluez/commit/32d147959b8e7de3fd3d4dc7d208b25f0f2d652e
Author: Andrei Istodorescu <andrei.istodorescu@nxp.com>
Date: 2024-05-16 (Thu, 16 May 2024)
Changed paths:
M profiles/audio/bap.c
Log Message:
-----------
bap: Update BIS management
Use the BIS index received in the BASE to synchronize to the BIG.
Allow bt_bap_endpoint to be NULL.
Remove the Broadcast Sink code from set_configuration.
Update BASE parsing so that it creates streams and transports, without a
remote PAC and endpoint.
Update bap_find_setup_by_stream to find the setup in case the stream does
not contain an endpoint.
Commit: 7aecf3bbcdb2257661116758154d827e5d15eb24
https://github.com/bluez/bluez/commit/7aecf3bbcdb2257661116758154d827e5d15eb24
Author: Andrei Istodorescu <andrei.istodorescu@nxp.com>
Date: 2024-05-16 (Thu, 16 May 2024)
Changed paths:
M src/shared/bap.c
M src/shared/bap.h
Log Message:
-----------
shared/bap: Remove not needed function
Commit: 7b1e0e503cb8a4e555496a542c06c318e112bd48
https://github.com/bluez/bluez/commit/7b1e0e503cb8a4e555496a542c06c318e112bd48
Author: Andrei Istodorescu <andrei.istodorescu@nxp.com>
Date: 2024-05-16 (Thu, 16 May 2024)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Return the local PAC when matching a BIS
Commit: 745f324de5898bb63878356bd6639ae6b7e2c3fe
https://github.com/bluez/bluez/commit/745f324de5898bb63878356bd6639ae6b7e2c3fe
Author: Andrei Istodorescu <andrei.istodorescu@nxp.com>
Date: 2024-05-16 (Thu, 16 May 2024)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Add stream ops for get_location, get_dir and get_state
Compare: https://github.com/bluez/bluez/compare/d9de306a28fe...745f324de589
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2024-05-16 17:36 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/d9de30-745f32@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).