Bluetooth: BAP: Unicast server depend on PACS
When in the BAP unicast server role, at least PAC sink or PAC source shall be set. In order to fulfill this new requirement, a few other Kconfig options had to be changed to a `depends on` from `select` to avoid recursive Kconfig requirements. This change may require some applications to update their configurations according to the migration guide. The change from `select` to `depends on` is ideal anyhow as that is the recommended way to add dependencies. This can checked via the combined BT_PACS Kconfig value. Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
This commit is contained in:
parent
4fe5ac9248
commit
353a05b116
11 changed files with 28 additions and 3 deletions
|
@ -213,6 +213,11 @@ Bluetooth Mesh
|
|||
Bluetooth Audio
|
||||
===============
|
||||
|
||||
* :kconfig:option:`CONFIG_BT_ASCS`, :kconfig:option:`CONFIG_BT_PERIPHERAL` and
|
||||
:kconfig:option:`CONFIG_BT_ISO_PERIPHERAL` are not longer `select`ed automatically when
|
||||
enabling :kconfig:option:`CONFIG_BT_BAP_UNICAST_SERVER`, and these must now be set explicitly
|
||||
in the project configuration file. (:github:`71993`)
|
||||
|
||||
Bluetooth Classic
|
||||
=================
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue