michaelh/zephyr
1
0
Fork 0
Code Releases Activity

Bluetooth: BAP: Unicast client shall support 0 or > 1 endpoints

Browse source 
As per table 4.2 in BAP v1.0.1, the BAP unicast client shall
support at least 2 (> 1) endpoints in either direction if it
supports that direction.

Since Kconfig does not support such requirements (0 || > 1),
this is done using a BUILD_ASSERT.

Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
This commit is contained in:
Emil Gydesen 2023-06-22 13:43:36 +02:00 • committed by Fabio Baltieri
commit 5a4c9a2112
3 changed files with 11 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

4
samples/bluetooth/tmap_central/prj.conf
View file

@ -39,8 +39,8 @@ CONFIG_BT_TBS_SUPPORTED_FEATURES=3
CONFIG_BT_ISO_TX_BUF_COUNT=2
CONFIG_BT_ISO_MAX_CHAN=2
CONFIG_BT_BAP_UNICAST_CLIENT_GROUP_STREAM_COUNT=1
CONFIG_BT_BAP_UNICAST_CLIENT_ASE_SNK_COUNT=1
CONFIG_BT_BAP_UNICAST_CLIENT_ASE_SRC_COUNT=1
CONFIG_BT_BAP_UNICAST_CLIENT_ASE_SNK_COUNT=2
CONFIG_BT_BAP_UNICAST_CLIENT_ASE_SRC_COUNT=2
CONFIG_BT_GATT_DYNAMIC_DB=y
CONFIG_BT_EXT_ADV=y