-
Notifications
You must be signed in to change notification settings - Fork 8.4k
Open
Open
Enhancement
Copy link
Labels
EnhancementChanges/Updates/Additions to existing featuresChanges/Updates/Additions to existing featuresarea: Bluetootharea: Bluetooth Audio
Description
Summary
The cap_commander_broadcast_assistant_recv_state_cb in cap_commander.c always assumes that the updated receive state is the one that was updated due to a change from our side.
Describe the solution you'd like
In the of a CAP Acceptor having multiple receive states, any one of them can change at any time, with or without a request from us. The help ensure correctness we need to compare the src_id of the receive state we have received an update for, with the src_id that is in our parameters.
In the case of adding a source via bt_cap_commander_broadcast_reception_start we do not have the src_id and we should compare the other fields (i.e. the tuple of {broadcast_id, addr_type and sid} which constitutes a unique receive state as per BAP.
Alternatives
No response
Additional Context
No response
Metadata
Metadata
Assignees
Labels
EnhancementChanges/Updates/Additions to existing featuresChanges/Updates/Additions to existing featuresarea: Bluetootharea: Bluetooth Audio
Type
Projects
Status
To do