michaelh/zephyr
1
0
Fork 0
Code Releases Activity

Bluetooth: CAP: Do not require CAS unless necessary

Browse source 
Removes the requirement that CAS is found on the remove
device for ad-hoc sets. This makes the CAP API more
versatile as it allows applications to use it with
remote non-CAP devices.

Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
This commit is contained in:
Emil Gydesen 2024-05-29 17:14:52 +02:00 • committed by Carles Cufí
commit 1af717430a
7 changed files with 74 additions and 144 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/releases/release-notes-3.7.rst
View file

@ -113,6 +113,10 @@ Bluetooth
The public_broadcast_sink sample has been renamed to pbp_public_broadcast_sink.
The public_broadcast_source sample has been renamed to pbp_public_broadcast_source.
* The CAP Commander and CAP Initiator now no longer require CAS to be discovered for
:code:`BT_CAP_SET_TYPE_AD_HOC` sets. This allows applications to use these APIs on e.g.
BAP Unicast Servers that do not implement the CAP Acceptor role.
* Host
* Added Nordic UART Service (NUS), enabled by the :kconfig:option:`CONFIG_BT_ZEPHYR_NUS`.