Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bluetooth: CAP: Add support for handling ASE errors #79014

Merged
merged 2 commits into from
Oct 23, 2024
Merged

Bluetooth: CAP: Add support for handling ASE errors #79014

merged 2 commits into from
Oct 23, 2024

Commits on Oct 9, 2024

  1. Bluetooth: BAP: Disallow bt_bap_stream_stop when CIS is not connected 

    When the CIS for a BAP stream is not connected, we cannot truly
be in the disabling state (the only state the stop operation
can be performed by the unicast client).

The reason for this is that if the CIS is disconnected, then
the ASCS server shall transition to the QoS Configured state
regardless of whether it has received a receiver stop ready
command from the unicast client.

Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
    @Thalley
    Thalley committed Oct 9, 2024
    Configuration menu
    Copy the full SHA
    d124aef View commit details
    Browse the repository at this point in the history

  2. Bluetooth: CAP: Add support for handling ASE errors 

    If we get an error/rejection from the CAP acceptor when
performing the Unicast Audio Start or Stop procedure then
we need to abort the procedure and let the application determine
what the next step is.

This change triggered a corner case when connecting to multiple
CAP acceptors as the CAP initiatior. This was also fixed as part
of this.

Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
    @Thalley
    Thalley committed Oct 9, 2024
    Configuration menu
    Copy the full SHA
    0d8b921 View commit details
    Browse the repository at this point in the history