Commit: 4130fe22fb8af7ebc02e737f2841da766e726b16
Parent: 7f1fa3d7ce39e2e3325c948ef2580b1d60c48c78
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Committer: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-02-28 19:14:09
Tree: 68eadaae3c01fca8f0c2a68b6cb9f4581cd41675

shared/bap: Fix not starting released operation The release operation is intended to release CIS resources: 'Releases resources associated with an ASE, immediately decouples the ASE from any previously coupled CIS, and tears down any CIS previously established for the ASE for one or more ASEs. Valid only if ASE_State field value = 0x01 (Codec Configured), 0x02 (QoS Configured), 0x03 (Enabling), 0x04 (Streaming), or 0x05 (Disabling).' But as the stated in ASCS specification release can also be used with the likes of Codec/QoS Configured which may not require the CIS to be established and in that case released operation shall start autonomously: 'The Released operation shall be initiated autonomously by the server if: The Release operation for an ASE has been completed and the server controller has indicated that the underlying CIS for the ASE has been torn down.'

Diffstat

M src/shared/bap.c | 19 ++++++++++++++++++-

1 files changed, 18 insertions(+), 1 deletions(-)

View Full Diff | Patch