[PATCH BlueZ v4 0/6] bap: Release cached ASEs on ClearConfiguration

[Luiz Augusto von Dentz <luiz.dentz@gmail.com>]

From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

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.

v4: 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.
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          | 178 ++++++++++++++++++++++++++++++++--
 src/shared/bap.c              |  32 ++++++
 src/shared/bap.h              |   8 ++
 test/functional/test_bap.py   |  23 +++++
 7 files changed, 333 insertions(+), 9 deletions(-)

-- 
2.56.0