Branch: refs/heads/master Home: https://github.com/bluez/bluez Commit: 4130fe22fb8af7ebc02e737f2841da766e726b16 https://github.com/bluez/bluez/commit/4130fe22fb8af7ebc02e737f2841da766e726b16 Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: 2025-02-28 (Fri, 28 Feb 2025) Changed paths: M src/shared/bap.c Log Message: ----------- 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.' Commit: 9efc138e98080e1e3f27e56c30cf289e014d5302 https://github.com/bluez/bluez/commit/9efc138e98080e1e3f27e56c30cf289e014d5302 Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: 2025-02-28 (Fri, 28 Feb 2025) Changed paths: M src/shared/bap.c Log Message: ----------- shared/bap: Fix state transition of sink for disable operation This fixes a regression introduced by 173045553c15 ("bap: Fix not generating releasing state") where the Disable operation no long caused the transition to QoS configured for Sink, as per ASCS spec Table 3.2: ASE state machine transitions that state transition is required. Commit: 711424319562ef2efcb7ad0d5f264400f72af8fd https://github.com/bluez/bluez/commit/711424319562ef2efcb7ad0d5f264400f72af8fd Author: Pauli Virtanen <pav@xxxxxx> Date: 2025-02-28 (Fri, 28 Feb 2025) Changed paths: M tools/sco-tester.c Log Message: ----------- sco-tester: add test for disconnecting SCO Add test that checks that shutdown(sk) results to HCI_Disconnection_Complete for the SCO handle: SCO Disconnect - Success Compare: https://github.com/bluez/bluez/compare/7f1fa3d7ce39...711424319562 To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
