Emil Gydesen 5a4c9a2112 Bluetooth: BAP: Unicast client shall support 0 or > 1 endpoints ... 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>		2023-06-26 12:40:39 +00:00
..
audio	Bluetooth: BAP: Unicast client shall support 0 or > 1 endpoints	2023-06-26 12:40:39 +00:00
common	Bluetooth: Mesh: Updated ACL configuration settings	2023-06-17 08:06:16 -04:00
controller	Bluetooth: Fix endianness handling for ext scan reports evt_type	2023-06-21 16:06:36 +02:00
crypto	Bluetooth: Logging: Move all logging symbols together	2023-03-28 10:33:24 +02:00
host	Bluetooth: att: Reset ATT timer when retrying on security error	2023-06-24 18:55:17 +02:00
lib	Bluetooth: Logging: Move all logging symbols together	2023-03-28 10:33:24 +02:00
mesh	Bluetooth: Mesh: Fix dead code issue when getting node id state	2023-06-22 12:34:23 +02:00
services	Bluetooth: IAS: Fix alert level loop	2023-06-21 09:34:49 +02:00
shell	Bluetooth: Shell: Move scan filter to function	2023-06-22 12:28:12 +02:00
CMakeLists.txt	Bluetooth: Host: Add Encrypted Advertising Data	2023-03-21 13:39:09 +02:00
Kconfig	Bluetooth: Add missing dependency for PAST feature	2023-04-04 14:31:17 +02:00
Kconfig.adv	Bluetooth: Host: Add support for PAwR Sync	2023-04-26 20:08:16 +02:00
Kconfig.iso	Bluetooth: ISO: Fix BT_ISO_TX_MTU range	2023-03-03 09:19:19 +01:00
Kconfig.logging	Bluetooth: Logging: Make BT_LOG and BT_LOG_LEGACY hidden symbols	2023-04-12 10:23:04 +02:00