Loading...
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 | # Kconfig - Bluetooth common configuration options # # Copyright (c) 2017 Nordic Semiconductor ASA # Copyright (c) 2016 Intel Corporation # # SPDX-License-Identifier: Apache-2.0 # if BT_HCI config BT_HCI_VS_EXT bool "Zephyr HCI Vendor-Specific Extensions" default y help Enable support for the Zephyr HCI Vendor-Specific Extensions in the Host and/or Controller. config BT_HCI_VS_EXT_DETECT bool "Use heuristics to guess HCI vendor extensions support in advance" depends on BT_HCI_VS_EXT && !BT_CTLR default y if BOARD_QEMU_X86 || BOARD_QEMU_CORTEX_M3 help Use some heuristics to try to guess in advance whether the controller supports the HCI vendor extensions in advance, in order to prevent sending vendor commands to controller which may interpret them in completely different ways. config BT_RPA # Virtual/hidden option bool select TINYCRYPT select TINYCRYPT_AES default n config BT_DEBUG # Virtual/hidden option to make the conditions more intuitive bool choice prompt "Bluetooth debug type" depends on BT default BT_DEBUG_NONE config BT_DEBUG_NONE bool "No debug log" help Select this to disable all Bluetooth debug logs. config BT_DEBUG_LOG bool "Normal printf-style to console" select BT_DEBUG select PRINTK select SYS_LOG help This option enables Bluetooth debug going to standard serial console. config BT_DEBUG_MONITOR bool "Monitor protocol over UART" select BT_DEBUG select PRINTK select CONSOLE_HAS_DRIVER help Use a custom logging protocol over the console UART instead of plain-text output. Requires a special application on the host side that can decode this protocol. Currently the 'btmon' tool from BlueZ is capable of doing this. If the target board has two or more external UARTs it is possible to keep using UART_CONSOLE together with this option, however if there is only a single external UART then UART_CONSOLE needs to be disabled (in which case printk/printf will get encoded into the monitor protocol). endchoice if BT_DEBUG if !HAS_DTS config BT_MONITOR_ON_DEV_NAME string "Device Name of Bluetooth monitor logging UART" depends on BT_DEBUG_MONITOR default "UART_0" help This option specifies the name of UART device to be used for the Bluetooth monitor logging. endif config BT_DEBUG_HCI_DRIVER bool "Bluetooth HCI driver debug" depends on BT_DEBUG help This option enables debug support for the active Bluetooth HCI driver, including the Controller-side HCI layer when included in the build. config BT_DEBUG_RPA bool "Bluetooth Resolvable Private Address (RPA) debug" depends on BT_RPA help This option enables debug support for the Bluetooth Resolvable Private Address (RPA) generation and resolution. endif #BT_DEBUG endif # BT_HCI |