michaelh/zephyr
1
0
Fork 0
Code Releases Activity

Bluetooth: Move HCI driver debug to top-level Kconfig

Browse source 
Since the HCI driver debug option applies to both files in
drivers/bluetooth and subsys/bluetooth, the configuration option itself
now lives in the top-level Kconfig file for consistency.

Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
This commit is contained in:
Carles Cufi 2017-05-05 15:45:34 +02:00 • committed by Johan Hedberg
commit 8a7eeeb7f1
3 changed files with 9 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

7
drivers/bluetooth/hci/Kconfig
View file

@ -58,13 +58,6 @@ endchoice
endif # !BLUETOOTH_CONTROLLER
config BLUETOOTH_DEBUG_HCI_DRIVER
bool "Bluetooth HCI driver debug"
depends on BLUETOOTH_DEBUG
help
This option enables debug support for the chosen
Bluetooth HCI driver
config BLUETOOTH_UART_ON_DEV_NAME
string "Device Name of UART Device for Bluetooth"
default "UART_0"

6
drivers/bluetooth/nble/Kconfig
View file

@ -79,12 +79,6 @@ config BLUETOOTH_DEVICE_NAME
if BLUETOOTH_DEBUG
config BLUETOOTH_DEBUG_HCI_DRIVER
bool "Bluetooth driver debug"
help
This option enables debug support for the chosen
Bluetooth UART driver to Nordic chip.
config BLUETOOTH_DEBUG_GATT
bool "Bluetooth Generic Attribute Profile (GATT) debug"
help

9
subsys/bluetooth/Kconfig
View file

@ -127,6 +127,7 @@ config BLUETOOTH_DEBUG_MONITOR
endchoice
if BLUETOOTH_DEBUG
config BLUETOOTH_DEBUG_COLOR
bool "Use colored logs"
depends on BLUETOOTH_DEBUG_LOG
@ -143,6 +144,14 @@ config BLUETOOTH_MONITOR_ON_DEV_NAME
This option specifies the name of UART device to be used
for the Bluetooth monitor logging.
config BLUETOOTH_DEBUG_HCI_DRIVER
bool "Bluetooth HCI driver debug"
depends on BLUETOOTH_DEBUG
help
This option enables debug support for the active
Bluetooth HCI driver, including the Controller-side HCI layer
when included in the build.
endif #BLUETOOTH_DEBUG
source "subsys/bluetooth/host/Kconfig"
source "subsys/bluetooth/controller/Kconfig"