michaelh/zephyr
1
0
Fork 0
Code Releases Activity

kconfig: bluetooth: Let BT_HCI_VS be configurable from controller

Browse source 
This moves the vendor-specific HCI command/event configuration
definitions out of bluetooth/common into bluetooth. This allows
the controller itself to indicate its support for vendor-specific
commands/events.

Signed-off-by: Thomas Stenersen <thomas.stenersen@nordicsemi.no>
This commit is contained in:
Thomas Stenersen 2019-02-21 15:20:57 +01:00 • committed by Carles Cufí
commit caa4f7baae
2 changed files with 8 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
subsys/bluetooth/common/Kconfig
View file

@ -6,8 +6,15 @@
# SPDX-License-Identifier: Apache-2.0
#
config BT_HAS_HCI_VS
bool
help
This option is set by the Bluetooth controller to indicate support
for the Zephyr HCI Vendor-Specific Commands and Event.
config BT_HCI_VS
bool "Zephyr HCI Vendor-Specific Commands"
depends on BT_HAS_HCI_VS
default y
help
Enable support for the Zephyr HCI Vendor-Specific Commands in the

1
subsys/bluetooth/controller/Kconfig
View file

@ -23,6 +23,7 @@ choice BT_LL_CHOICE
config BT_LL_SW
bool "Software-based BLE Link Layer"
select BT_RECV_IS_RX_THREAD
select BT_HAS_HCI_VS
select ENTROPY_GENERATOR
select ENTROPY_NRF5_RNG if SOC_COMPATIBLE_NRF
select ENTROPY_NRF5_BIAS_CORRECTION if SOC_COMPATIBLE_NRF