bap: Release cached ASEs on ClearConfiguration
Status from this message: This series was applied to bluetooth/bluez.git (master)
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v6 Latest6 patches 1 replyApplied
- v56 patches 1 replySuperseded
- v4 posting 2/26 patches 0 repliesSuperseded
Earlier versions · 4
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v4 posting 1/2 | 6 patches | 2 replies | Superseded | |
| v3 | 6 patches | 1 reply | Applied | |
| v2 | 6 patches | 1 reply | Superseded | |
| v1 | 5 patches | 0 replies | Superseded |
Patches in v6 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | shared/bap: Add bt_bap_foreach_stream and bt_bap_stream_get_rpacsrc/ src/ | +39 | 1 reply | |
| 2/6 | shared/bap: Update the remote PAC when reusing an ASEsrc/ | +1 | 0 replies | |
| 3/6 | bap: Release cached ASEs on ClearConfiguration of an endpointprofiles/ | +212 | 0 replies | |
| 4/6 | client/player: Add endpoint.clear commandclient/ doc/ | +77 | 0 replies | |
| 5/6 | doc/functional-bap: Document clearing a cached configurationdoc/ | +24 | 0 replies | |
| 6/6 | test: functional: Cover clearing a cached configurationtest/ | +23 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v6 yet.
Cover letter [PATCH BlueZ v6 0/6] bap: Release cached ASEs on ClearConfiguration
From: Luiz Augusto von Dentz <[email protected]>
An acceptor may keep an ASE in Codec Configured, caching its codec configuration, once the initiator removes the transport. The initiator then has no way to get rid of it, as it no longer has a transport to release.
Release such cached ASEs on ClearConfiguration of an endpoint, and add endpoint.clear to bluetoothctl to exercise it, with a functional test.
This series is independent of the other two.
v6: Wait for a cached ASE to leave Releasing for a bounded time, and fail
all the ClearConfiguration waiting for it when its release fails or times out. Join a pending release also when the ASE is already Releasing, and don't let a late response access the freed queue.
v5: Complete the release of a cached ASE once it leaves Releasing, to Idle
or back to Codec Configured as some servers do, and don't release it again while a release is pending.
v4: Complete every pending release of a stream once it is idle, including
the ones left behind by a failed release.
v3: Reply to ClearConfiguration once the cached ASEs are idle, and
report a failed release as an error.
v2: Wait for the release of the cached ASEs before replying, validate the
transport path of endpoint.clear and update the remote PAC of an ASE when it is reused (new patch 2/6).
Luiz Augusto von Dentz (6):
shared/bap: Add bt_bap_foreach_stream and bt_bap_stream_get_rpac shared/bap: Update the remote PAC when reusing an ASE
bap: Release cached ASEs on ClearConfiguration of an endpoint client/player: Add endpoint.clear command doc/functional-bap: Document clearing a cached configuration
test: functional: Cover clearing a cached configuration
client/player.c | 57 +++++++++ doc/bluetoothctl-endpoint.rst | 20 +++ doc/functional-bap.rst | 24 ++++ profiles/audio/bap.c | 221 ++++++++++++++++++++++++++++++++-- src/shared/bap.c | 32 +++++ src/shared/bap.h | 8 ++ test/functional/test_bap.py | 23 ++++ 7 files changed, 376 insertions(+), 9 deletions(-)
Signature · 1 line
2.56.0