alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
878d70d9e6
esp-idf/components/bt/Kconfig

1276 lines
37 KiB
Plaintext
Raw Normal View History

component/bt : fix bug of sw interrupt cause to run btdm to different cpu core. 1. add sw interrupt cause osi to controller. 2. modify the kconfig to improve the option view. 3. add option of the cpu core which bluedroid run. 4. add option of the cpu core which bluetooth controller run.
2017-10-20 05:09:03 -04:00
menu Bluetooth
config BT_ENABLED
config: Move WiFi & BT toggles to Components menu, same as Ethernet
2017-01-10 00:39:43 -05:00
bool "Bluetooth"
help
component/bt: allow to use alternative Bluetooth stack by disabling Bluedroid Merges #408 https://github.com/espressif/esp-idf/pull/440
2017-03-07 12:20:33 -05:00
Select this option to enable Bluetooth and show the submenu with Bluetooth configuration choices.
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
menu "Bluetooth controller"
visible if BT_ENABLED
choice BTDM_CONTROLLER_MODE
prompt "Bluetooth controller mode (BR/EDR/BLE/DUALMODE)"
depends on BT_ENABLED
help
Specify the bluetooth controller mode (BR/EDR, BLE or dual mode).
config BTDM_CONTROLLER_MODE_BLE_ONLY
bool "BLE Only"
config BTDM_CONTROLLER_MODE_BR_EDR_ONLY
bool "BR/EDR Only"
config BTDM_CONTROLLER_MODE_BTDM
bool "Bluetooth Dual Mode"
endchoice
config BTDM_CONTROLLER_BLE_MAX_CONN
tools: fix ci example build report reassign warnning
2018-08-08 07:46:53 -04:00
int "BLE Max Connections"
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
depends on BTDM_CONTROLLER_MODE_BLE_ONLY || BTDM_CONTROLLER_MODE_BTDM
default 3
range 1 9
help
tools: fix ci example build report reassign warnning
2018-08-08 07:46:53 -04:00
BLE maximum connections of bluetooth controller.
Each connection uses 1KB static DRAM whenever the BT controller is enabled.
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
config BTDM_CONTROLLER_BR_EDR_MAX_ACL_CONN
tools: fix ci example build report reassign warnning
2018-08-08 07:46:53 -04:00
int "BR/EDR ACL Max Connections"
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
depends on BTDM_CONTROLLER_MODE_BR_EDR_ONLY || BTDM_CONTROLLER_MODE_BTDM
default 2
range 1 7
help
component/bt: Add Legacy Pairing
2018-09-04 09:11:03 -04:00
BR/EDR ACL maximum connections of bluetooth controller.
tools: fix ci example build report reassign warnning
2018-08-08 07:46:53 -04:00
Each connection uses 1.2KB static DRAM whenever the BT controller is enabled.
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
config BTDM_CONTROLLER_BR_EDR_MAX_SYNC_CONN
tools: fix ci example build report reassign warnning
2018-08-08 07:46:53 -04:00
int "BR/EDR Sync(SCO/eSCO) Max Connections"
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
depends on BTDM_CONTROLLER_MODE_BR_EDR_ONLY || BTDM_CONTROLLER_MODE_BTDM
default 0
range 0 3
help
tools: fix ci example build report reassign warnning
2018-08-08 07:46:53 -04:00
BR/EDR Synchronize maximum connections of bluetooth controller.
Each connection uses 2KB static DRAM whenever the BT controller is enabled.
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
component/bt: Allow configuration of default SCO_DATA_PATH in bluetooth controller
2019-06-04 04:31:21 -04:00
choice BTDM_CONTROLLER_BR_EDR_SCO_DATA_PATH
prompt "BR/EDR Sync(SCO/eSCO) default data path"
depends on BTDM_CONTROLLER_MODE_BR_EDR_ONLY || BTDM_CONTROLLER_MODE_BTDM
default BTDM_CONTROLLER_BR_EDR_SCO_DATA_PATH_PCM
help
SCO data path, i.e. HCI or PCM.
SCO data can be sent/received through HCI synchronous packets, or the data
can be routed to on-chip PCM module on ESP32. PCM input/output signals can
be "matrixed" to GPIOs. The default data path can also be set using API
"esp_bredr_sco_datapath_set"
config BTDM_CONTROLLER_BR_EDR_SCO_DATA_PATH_HCI
bool "HCI"
config BTDM_CONTROLLER_BR_EDR_SCO_DATA_PATH_PCM
bool "PCM"
endchoice
config BTDM_CONTROLLER_BR_EDR_SCO_DATA_PATH_EFF
int
default 0 if BTDM_CONTROLLER_BR_EDR_SCO_DATA_PATH_HCI
default 1 if BTDM_CONTROLLER_BR_EDR_SCO_DATA_PATH_PCM
default 0
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
config BTDM_CONTROLLER_BLE_MAX_CONN_EFF
int
default BTDM_CONTROLLER_BLE_MAX_CONN if BTDM_CONTROLLER_MODE_BLE_ONLY || BTDM_CONTROLLER_MODE_BTDM
default 0
config BTDM_CONTROLLER_BR_EDR_MAX_ACL_CONN_EFF
int
default BTDM_CONTROLLER_BR_EDR_MAX_ACL_CONN if BTDM_CONTROLLER_MODE_BR_EDR_ONLY || BTDM_CONTROLLER_MODE_BTDM
default 0
config BTDM_CONTROLLER_BR_EDR_MAX_SYNC_CONN_EFF
int
default BTDM_CONTROLLER_BR_EDR_MAX_SYNC_CONN if BTDM_CONTROLLER_MODE_BR_EDR_ONLY || BTDM_CONTROLLER_MODE_BTDM
default 0
component/bt : fix bug of sw interrupt cause to run btdm to different cpu core. 1. add sw interrupt cause osi to controller. 2. modify the kconfig to improve the option view. 3. add option of the cpu core which bluedroid run. 4. add option of the cpu core which bluetooth controller run.
2017-10-20 05:09:03 -04:00
choice BTDM_CONTROLLER_PINNED_TO_CORE_CHOICE
prompt "The cpu core which bluetooth controller run"
depends on BT_ENABLED && !FREERTOS_UNICORE
help
Specify the cpu core to run bluetooth controller.
Can not specify no-affinity.
config BTDM_CONTROLLER_PINNED_TO_CORE_0
bool "Core 0 (PRO CPU)"
config BTDM_CONTROLLER_PINNED_TO_CORE_1
bool "Core 1 (APP CPU)"
depends on !FREERTOS_UNICORE
endchoice
config BTDM_CONTROLLER_PINNED_TO_CORE
int
default 0 if BTDM_CONTROLLER_PINNED_TO_CORE_0
default 1 if BTDM_CONTROLLER_PINNED_TO_CORE_1
default 0
choice BTDM_CONTROLLER_HCI_MODE_CHOICE
prompt "HCI mode"
component/bt: allow to use alternative Bluetooth stack by disabling Bluedroid Merges #408 https://github.com/espressif/esp-idf/pull/440
2017-03-07 12:20:33 -05:00
depends on BT_ENABLED
component/bt : fix bug of sw interrupt cause to run btdm to different cpu core. 1. add sw interrupt cause osi to controller. 2. modify the kconfig to improve the option view. 3. add option of the cpu core which bluedroid run. 4. add option of the cpu core which bluetooth controller run.
2017-10-20 05:09:03 -04:00
help
Speicify HCI mode as VHCI or UART(H4)
config BTDM_CONTROLLER_HCI_MODE_VHCI
bool "VHCI"
bt: Add option to ena/dis BLE service change registration Add option to enable/disable automatic registration of BLE Gattc service change notify. Which sends in parralel (with user message flow) commands to BLE server which sometime leads to GATT_BUSY. (BLE server is able to handle only one command at time) Closes https://github.com/espressif/esp-idf/issues/1575 Merges https://github.com/espressif/esp-idf/pull/1673
2018-02-11 14:49:38 -05:00
help
component/bt : fix bug of sw interrupt cause to run btdm to different cpu core. 1. add sw interrupt cause osi to controller. 2. modify the kconfig to improve the option view. 3. add option of the cpu core which bluedroid run. 4. add option of the cpu core which bluetooth controller run.
2017-10-20 05:09:03 -04:00
Normal option. Mostly, choose this VHCI when bluetooth host run on ESP32, too.
config BTDM_CONTROLLER_HCI_MODE_UART_H4
bool "UART(H4)"
help
If use external bluetooth host which run on other hardware and use UART as the HCI interface,
choose this option.
endchoice
menu "HCI UART(H4) Options"
visible if BTDM_CONTROLLER_HCI_MODE_UART_H4
config BT_HCI_UART_NO
int "UART Number for HCI"
depends on BTDM_CONTROLLER_HCI_MODE_UART_H4
range 1 2
default 1
help
Uart number for HCI. The available uart is UART1 and UART2.
config BT_HCI_UART_BAUDRATE
int "UART Baudrate for HCI"
depends on BTDM_CONTROLLER_HCI_MODE_UART_H4
range 115200 921600
default 921600
help
UART Baudrate for HCI. Please use standard baudrate.
endmenu
component/bt: implement bluetooth modem sleep mode, one mode for BLE only and another for dual mode bluetooth 1. provide options for bluetooth low power mode 2. provide two options for bluetooth low power clock: main XTAL and external 32kHz XTAL 3. provide function and callbacks to control bluetooth low power mode, including enable/disable sleep, software wakeup request, low power clock settings, check power state, etc 4. modify vhci API vhci_host_send_packet to use blocking mode 5. note that DFS and bluetooth modem sleep can not be used together currently.
2018-04-08 07:19:47 -04:00
menu "MODEM SLEEP Options"
visible if BT_ENABLED
config BTDM_CONTROLLER_MODEM_SLEEP
bool "Bluetooth modem sleep"
depends on BT_ENABLED
component/bt: enable bluetooth modem sleep as default setting
2018-09-14 05:01:45 -04:00
default y
component/bt: implement bluetooth modem sleep mode, one mode for BLE only and another for dual mode bluetooth 1. provide options for bluetooth low power mode 2. provide two options for bluetooth low power clock: main XTAL and external 32kHz XTAL 3. provide function and callbacks to control bluetooth low power mode, including enable/disable sleep, software wakeup request, low power clock settings, check power state, etc 4. modify vhci API vhci_host_send_packet to use blocking mode 5. note that DFS and bluetooth modem sleep can not be used together currently.
2018-04-08 07:19:47 -04:00
help
Enable/disable bluetooth controller low power mode.
choice BTDM_MODEM_SLEEP_MODE
prompt "Bluetooth Modem sleep mode"
depends on BTDM_CONTROLLER_MODEM_SLEEP
help
To select which strategy to use for modem sleep
config BTDM_MODEM_SLEEP_MODE_ORIG
bool "ORIG Mode(sleep with low power clock)"
help
component/bt: add more information and description for bluetooth modem sleep Add remark that "EVED" mode for bluetooth modem sleep is only used for internal test
2018-12-21 06:29:47 -05:00
ORIG mode is a bluetooth sleep mode that can be used for dual mode controller. In this mode, bluetooth controller
sleeps between BR/EDR frames and BLE events. A low power clock is used to maintain bluetooth reference clock.
component/bt: implement bluetooth modem sleep mode, one mode for BLE only and another for dual mode bluetooth 1. provide options for bluetooth low power mode 2. provide two options for bluetooth low power clock: main XTAL and external 32kHz XTAL 3. provide function and callbacks to control bluetooth low power mode, including enable/disable sleep, software wakeup request, low power clock settings, check power state, etc 4. modify vhci API vhci_host_send_packet to use blocking mode 5. note that DFS and bluetooth modem sleep can not be used together currently.
2018-04-08 07:19:47 -04:00
config BTDM_MODEM_SLEEP_MODE_EVED
component/bt: add more information and description for bluetooth modem sleep Add remark that "EVED" mode for bluetooth modem sleep is only used for internal test
2018-12-21 06:29:47 -05:00
bool "EVED Mode(For internal test only)"
component/bt: implement bluetooth modem sleep mode, one mode for BLE only and another for dual mode bluetooth 1. provide options for bluetooth low power mode 2. provide two options for bluetooth low power clock: main XTAL and external 32kHz XTAL 3. provide function and callbacks to control bluetooth low power mode, including enable/disable sleep, software wakeup request, low power clock settings, check power state, etc 4. modify vhci API vhci_host_send_packet to use blocking mode 5. note that DFS and bluetooth modem sleep can not be used together currently.
2018-04-08 07:19:47 -04:00
help
component/bt: add more information and description for bluetooth modem sleep Add remark that "EVED" mode for bluetooth modem sleep is only used for internal test
2018-12-21 06:29:47 -05:00
EVED mode is for BLE only and is only for internal test. Do not use it for production. this mode is not compatible
with DFS nor light sleep
component/bt: implement bluetooth modem sleep mode, one mode for BLE only and another for dual mode bluetooth 1. provide options for bluetooth low power mode 2. provide two options for bluetooth low power clock: main XTAL and external 32kHz XTAL 3. provide function and callbacks to control bluetooth low power mode, including enable/disable sleep, software wakeup request, low power clock settings, check power state, etc 4. modify vhci API vhci_host_send_packet to use blocking mode 5. note that DFS and bluetooth modem sleep can not be used together currently.
2018-04-08 07:19:47 -04:00
endchoice
choice BTDM_LOW_POWER_CLOCK
prompt "Bluetooth low power clock"
depends on BTDM_MODEM_SLEEP_MODE_ORIG
help
Select the low power clock source for bluetooth controller
config BTDM_LPCLK_SEL_MAIN_XTAL
bool "Main crystal"
component/bt: bugfix of bluetooth modem sleep not being able to work with Dynamic Frequency Scaling 1. start an esp_timer on entering sleep to acquire pm_lock before wake up from modem sleep 2. decrease the clock division of XTAL fed to bluetooth low power clock from 32us to 2us period to allow to work under 240MHz Max CPU frequency 3. decrease the minimum sleep duration threshold to allow shorter bluetooth modem sleep period, especially for BLE with short connection interval 4. reconfigure bluetooth baseband(BT-BB) settings after PHY/RF init upon waking up from modem sleep to avoid packet RX/TX performance degradation
2018-12-14 01:56:29 -05:00
help
Main crystal can be used as low power clock for bluetooth modem sleep. If this option is selected, bluetooth
modem sleep can work under Dynamic Frequency Scaling(DFS) enabled, but cannot work when light sleep is enabled.
component/bt: add more information and description for bluetooth modem sleep Add remark that "EVED" mode for bluetooth modem sleep is only used for internal test
2018-12-21 06:29:47 -05:00
Main crystal has a relatively better performance than other bluetooth low power clock sources.
component/bt: implement bluetooth modem sleep mode, one mode for BLE only and another for dual mode bluetooth 1. provide options for bluetooth low power mode 2. provide two options for bluetooth low power clock: main XTAL and external 32kHz XTAL 3. provide function and callbacks to control bluetooth low power mode, including enable/disable sleep, software wakeup request, low power clock settings, check power state, etc 4. modify vhci API vhci_host_send_packet to use blocking mode 5. note that DFS and bluetooth modem sleep can not be used together currently.
2018-04-08 07:19:47 -04:00
config BTDM_LPCLK_SEL_EXT_32K_XTAL
bool "External 32kHz crystal"
depends on ESP32_RTC_CLOCK_SOURCE_EXTERNAL_CRYSTAL
endchoice
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
endmenu
config BLE_SCAN_DUPLICATE
Merge branch 'master' into feature/cmake
2018-08-30 00:30:09 -04:00
bool "BLE Scan Duplicate Options"
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
depends on (BTDM_CONTROLLER_MODE_BTDM || BTDM_CONTROLLER_MODE_BLE_ONLY)
default y
help
This select enables parameters setting of BLE scan duplicate.
component/bt: add adv packet duplicate in scan duplicate
2018-08-20 03:04:37 -04:00
choice SCAN_DUPLICATE_TYPE
prompt "Scan Duplicate Type"
default SCAN_DUPLICATE_BY_DEVICE_ADDR
depends on BLE_SCAN_DUPLICATE
help
component/bt: Allow configuration of default SCO_DATA_PATH in bluetooth controller
2019-06-04 04:31:21 -04:00
Scan duplicate have three ways. one is "Scan Duplicate By Device Address", This way is to use advertiser address
filtering. The adv packet of the same address is only allowed to be reported once. Another way is "Scan Duplicate
By Device Address And Advertising Data". This way is to use advertising data and device address filtering. All
different adv packets with the same address are allowed to be reported. The last way is "Scan Duplicate By Advertising
component/bt: add adv packet duplicate in scan duplicate
2018-08-20 03:04:37 -04:00
Data". This way is to use advertising data filtering. All same advertising data only allow to be reported once even though
they are from different devices.
config SCAN_DUPLICATE_BY_DEVICE_ADDR
bool "Scan Duplicate By Device Address"
component/bt: Allow configuration of default SCO_DATA_PATH in bluetooth controller
2019-06-04 04:31:21 -04:00
help
component/bt: add adv packet duplicate in scan duplicate
2018-08-20 03:04:37 -04:00
This way is to use advertiser address filtering. The adv packet of the same address is only allowed to be reported once
config SCAN_DUPLICATE_BY_ADV_DATA
bool "Scan Duplicate By Advertising Data"
help
This way is to use advertising data filtering. All same advertising data only allow to be reported once even though
they are from different devices.
config SCAN_DUPLICATE_BY_ADV_DATA_AND_DEVICE_ADDR
bool "Scan Duplicate By Device Address And Advertising Data"
help
component/bt: Allow configuration of default SCO_DATA_PATH in bluetooth controller
2019-06-04 04:31:21 -04:00
This way is to use advertising data and device address filtering. All different adv packets with the same address are
component/bt: add adv packet duplicate in scan duplicate
2018-08-20 03:04:37 -04:00
allowed to be reported.
endchoice
config SCAN_DUPLICATE_TYPE
int
depends on BLE_SCAN_DUPLICATE
default 0 if SCAN_DUPLICATE_BY_DEVICE_ADDR
default 1 if SCAN_DUPLICATE_BY_ADV_DATA
default 2 if SCAN_DUPLICATE_BY_ADV_DATA_AND_DEVICE_ADDR
default 0
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
config DUPLICATE_SCAN_CACHE_SIZE
int "Maximum number of devices in scan duplicate filter"
depends on BLE_SCAN_DUPLICATE
component/bt: add adv packet duplicate in scan duplicate
2018-08-20 03:04:37 -04:00
range 10 1000
default 200
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
help
Maximum number of devices which can be recorded in scan duplicate filter.
When the maximum amount of device in the filter is reached, the cache will be refreshed.
config BLE_MESH_SCAN_DUPLICATE_EN
bool "Special duplicate scan mechanism for BLE Mesh scan"
depends on BLE_SCAN_DUPLICATE
default n
help
This enables the BLE scan duplicate for special BLE Mesh scan.
config MESH_DUPLICATE_SCAN_CACHE_SIZE
int "Maximum number of Mesh adv packets in scan duplicate filter"
depends on BLE_MESH_SCAN_DUPLICATE_EN
component/bt: add adv packet duplicate in scan duplicate
2018-08-20 03:04:37 -04:00
range 10 1000
default 200
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
help
Maximum number of adv packets which can be recorded in duplicate scan cache for BLE Mesh.
When the maximum amount of device in the filter is reached, the cache will be refreshed.
Component/bt: add BLE adv report flow control
2019-03-01 08:59:55 -05:00
config BLE_ADV_REPORT_FLOW_CONTROL_SUPPORTED
bool "BLE adv report flow control supported"
depends on (BTDM_CONTROLLER_MODE_BTDM || BTDM_CONTROLLER_MODE_BLE_ONLY)
default y
help
The function is mainly used to enable flow control for advertising reports. When it is enabled,
advertising reports will be discarded by the controller if the number of unprocessed advertising
reports exceeds the size of BLE adv report flow control.
config BLE_ADV_REPORT_FLOW_CONTROL_NUM
int "BLE adv report flow control number"
depends on BLE_ADV_REPORT_FLOW_CONTROL_SUPPORTED
range 50 1000
default 100
help
The number of unprocessed advertising report that Bluedroid can save.If you set
`BLE_ADV_REPORT_FLOW_CONTROL_NUM` to a small value, this may cause adv packets lost.
If you set `BLE_ADV_REPORT_FLOW_CONTROL_NUM` to a large value, Bluedroid may cache a
lot of adv packets and this may cause system memory run out. For example, if you set
it to 50, the maximum memory consumed by host is 35 * 50 bytes. Please set
`BLE_ADV_REPORT_FLOW_CONTROL_NUM` according to your system free memory and handle adv
packets as fast as possible, otherwise it will cause adv packets lost.
config BLE_ADV_REPORT_DISCARD_THRSHOLD
int "BLE adv lost event threshold value"
depends on BLE_ADV_REPORT_FLOW_CONTROL_SUPPORTED
range 1 1000
default 20
help
When adv report flow control is enabled, The ADV lost event will be generated when the number
of ADV packets lost in the controller reaches this threshold. It is better to set a larger value.
If you set `BLE_ADV_REPORT_DISCARD_THRSHOLD` to a small value or printf every adv lost event, it
may cause adv packets lost more.
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
component/bt: implement bluetooth modem sleep mode, one mode for BLE only and another for dual mode bluetooth 1. provide options for bluetooth low power mode 2. provide two options for bluetooth low power clock: main XTAL and external 32kHz XTAL 3. provide function and callbacks to control bluetooth low power mode, including enable/disable sleep, software wakeup request, low power clock settings, check power state, etc 4. modify vhci API vhci_host_send_packet to use blocking mode 5. note that DFS and bluetooth modem sleep can not be used together currently.
2018-04-08 07:19:47 -04:00
endmenu
component/bt : fix bug of sw interrupt cause to run btdm to different cpu core. 1. add sw interrupt cause osi to controller. 2. modify the kconfig to improve the option view. 3. add option of the cpu core which bluedroid run. 4. add option of the cpu core which bluetooth controller run.
2017-10-20 05:09:03 -04:00
menuconfig BLUEDROID_ENABLED
bool "Bluedroid Enable"
depends on BTDM_CONTROLLER_HCI_MODE_VHCI
default y
help
This enables the default Bluedroid Bluetooth stack
choice BLUEDROID_PINNED_TO_CORE_CHOICE
prompt "The cpu core which Bluedroid run"
depends on BLUEDROID_ENABLED && !FREERTOS_UNICORE
help
Which the cpu core to run Bluedroid. Can choose core0 and core1.
Can not specify no-affinity.
config BLUEDROID_PINNED_TO_CORE_0
bool "Core 0 (PRO CPU)"
config BLUEDROID_PINNED_TO_CORE_1
bool "Core 1 (APP CPU)"
depends on !FREERTOS_UNICORE
endchoice
config BLUEDROID_PINNED_TO_CORE
int
depends on BLUEDROID_ENABLED
default 0 if BLUEDROID_PINNED_TO_CORE_0
default 1 if BLUEDROID_PINNED_TO_CORE_1
default 0
Initial public version
2016-08-17 11:08:22 -04:00
component/bt : change task to decease dram(heap) 1. decrease the task size(HCI cannot < 1024, btu cannot < 4096) 2. btc task can config by menuconfig(default 2048)
2016-11-25 10:37:46 -05:00
config BTC_TASK_STACK_SIZE
component/bt: clean up the A2DP sink example
2017-03-18 04:02:54 -04:00
int "Bluetooth event (callback to application) task stack size"
Merge branch 'master' into feature/btdm_avrc
2017-03-31 00:51:45 -04:00
depends on BLUEDROID_ENABLED
component/bt: clean up the A2DP sink example
2017-03-18 04:02:54 -04:00
default 3072
help
This select btc task stack size
component/bt : change task to decease dram(heap) 1. decrease the task size(HCI cannot < 1024, btu cannot < 4096) 2. btc task can config by menuconfig(default 2048)
2016-11-25 10:37:46 -05:00
component/bt : fix the bug of deinit/disable 1. fix the exception of deinit/disable 2. debug mem leak of deinit, fix some memleak, but still something wrong. 3. debug men leak of disable. 4. add bluedroid memory debug
2016-12-12 15:10:44 -05:00
config BLUEDROID_MEM_DEBUG
component/bt: clean up the A2DP sink example
2017-03-18 04:02:54 -04:00
bool "Bluedroid memory debug"
Merge branch 'master' into feature/btdm_avrc
2017-03-31 00:51:45 -04:00
depends on BLUEDROID_ENABLED
component/bt: clean up the A2DP sink example
2017-03-18 04:02:54 -04:00
default n
help
Bluedroid memory debug
component/bt : fix the bug of deinit/disable 1. fix the exception of deinit/disable 2. debug mem leak of deinit, fix some memleak, but still something wrong. 3. debug men leak of disable. 4. add bluedroid memory debug
2016-12-12 15:10:44 -05:00
component/bt: add Kconfig option "CLASSIC_BT_ENABLED"
2017-03-16 10:32:27 -04:00
config CLASSIC_BT_ENABLED
component/bt: clean up the A2DP sink example
2017-03-18 04:02:54 -04:00
bool "Classic Bluetooth"
Merge branch 'master' into feature/btdm_avrc
2017-03-31 00:51:45 -04:00
depends on BLUEDROID_ENABLED
component/bt: clean up the A2DP sink example
2017-03-18 04:02:54 -04:00
default n
component/bt: add constraint in Kconfig to enable SMP_ENABLE when using classic BT 1. For now, some security related functions used in classic Bluetooth are controlled by "SMP_ENABLE". This commit fixes the dependency. 2. The two options, "CLASSIC_BT_ENABLED" and "SMP_ENABLED" The two options will be decoupled in the future.
2017-06-15 03:48:20 -04:00
help
For now this option needs "SMP_ENABLE" to be set to yes
component/bt: add Kconfig option "CLASSIC_BT_ENABLED"
2017-03-16 10:32:27 -04:00
component/bt: implement A2DP source 1. Modified symbol names of A2DP sink APIs include: - esp_a2d_data_cb_t --> esp_a2d_sink_data_cb_t - esp_a2d_register_data_callback --> esp_a2d_sink_register_data_callback
2017-12-25 06:39:37 -05:00
config A2DP_ENABLE
bool "A2DP"
component/bt: Add SPP profile
2018-01-05 03:48:29 -05:00
depends on CLASSIC_BT_ENABLED
default n
help
component/bt: implement A2DP source 1. Modified symbol names of A2DP sink APIs include: - esp_a2d_data_cb_t --> esp_a2d_sink_data_cb_t - esp_a2d_register_data_callback --> esp_a2d_sink_register_data_callback
2017-12-25 06:39:37 -05:00
Advanced Audio Distrubution Profile
bt: Add option to ena/dis BLE service change registration Add option to enable/disable automatic registration of BLE Gattc service change notify. Which sends in parralel (with user message flow) commands to BLE server which sometime leads to GATT_BUSY. (BLE server is able to handle only one command at time) Closes https://github.com/espressif/esp-idf/issues/1575 Merges https://github.com/espressif/esp-idf/pull/1673
2018-02-11 14:49:38 -05:00
component/bt: make A2DP source and sink task size configurable through menuconfig 1. use different set of parameters for A2DP source/sink tasks 2. make the task stack size configurable through menuconfig
2018-01-30 01:26:53 -05:00
config A2DP_SINK_TASK_STACK_SIZE
int "A2DP sink (audio stream decoding) task stack size"
bt-a2dp: BT A2DP sink and source selection is now runtime Earlier they have to be selected at the compile time through sdkconfig. A2DP sink and source application tested with this change. Signed-off-by: Amey Inamdar <amey@espressif.com>
2018-04-12 01:17:21 -04:00
depends on A2DP_ENABLE
component/bt: make A2DP source and sink task size configurable through menuconfig 1. use different set of parameters for A2DP source/sink tasks 2. make the task stack size configurable through menuconfig
2018-01-30 01:26:53 -05:00
default 2048
config A2DP_SOURCE_TASK_STACK_SIZE
int "A2DP source (audio stream encoding) task stack size"
bt-a2dp: BT A2DP sink and source selection is now runtime Earlier they have to be selected at the compile time through sdkconfig. A2DP sink and source application tested with this change. Signed-off-by: Amey Inamdar <amey@espressif.com>
2018-04-12 01:17:21 -04:00
depends on A2DP_ENABLE
component/bt: make A2DP source and sink task size configurable through menuconfig 1. use different set of parameters for A2DP source/sink tasks 2. make the task stack size configurable through menuconfig
2018-01-30 01:26:53 -05:00
default 2048
component/bt: Add SPP profile
2018-01-05 03:48:29 -05:00
config BT_SPP_ENABLED
component/bt: implement A2DP source 1. Modified symbol names of A2DP sink APIs include: - esp_a2d_data_cb_t --> esp_a2d_sink_data_cb_t - esp_a2d_register_data_callback --> esp_a2d_sink_register_data_callback
2017-12-25 06:39:37 -05:00
bool "SPP"
component/bt: Add SPP profile
2018-01-05 03:48:29 -05:00
depends on CLASSIC_BT_ENABLED
default n
help
component/bt: implement A2DP source 1. Modified symbol names of A2DP sink APIs include: - esp_a2d_data_cb_t --> esp_a2d_sink_data_cb_t - esp_a2d_register_data_callback --> esp_a2d_sink_register_data_callback
2017-12-25 06:39:37 -05:00
This enables the Serial Port Profile
component/bt: Add SPP profile
2018-01-05 03:48:29 -05:00
component/bt: implement HFP Hands Free Unit Role
2018-05-20 23:33:30 -04:00
config HFP_ENABLE
bool "Hands Free/Handset Profile"
depends on CLASSIC_BT_ENABLED
default n
choice HFP_ROLE
prompt "Hands-free Profile Role configuration"
depends on HFP_ENABLE
config HFP_CLIENT_ENABLE
bool "Hands Free Unit"
endchoice
choice HFP_AUDIO_DATA_PATH
prompt "audio(SCO) data path"
depends on HFP_ENABLE
component/bt: Allow configuration of default SCO_DATA_PATH in bluetooth controller
2019-06-04 04:31:21 -04:00
help
SCO data path, i.e. HCI or PCM. This option is set using API
"esp_bredr_sco_datapath_set" in Bluetooth host. Default SCO data
path can also be set in Bluetooth Controller.
component/bt: implement HFP Hands Free Unit Role
2018-05-20 23:33:30 -04:00
config HFP_AUDIO_DATA_PATH_PCM
bool "PCM"
config HFP_AUDIO_DATA_PATH_HCI
bool "HCI"
endchoice
component/bt:Finish all the separate code from BT & BLE
2017-04-20 07:18:05 -04:00
config GATTS_ENABLE
component/bt:change the kconfig. 1.change the rowdata to rodata; 2.change BT_ACL_CONNECTIONS to Maximum BT/BLE connection count. 3. change the comments of bt_target.h:505 from 40 to 5.
2017-04-25 22:47:16 -04:00
bool "Include GATT server module(GATTS)"
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
depends on BLUEDROID_ENABLED && (BTDM_CONTROLLER_MODE_BTDM || BTDM_CONTROLLER_MODE_BLE_ONLY)
bt: Add option to ena/dis BLE service change registration Add option to enable/disable automatic registration of BLE Gattc service change notify. Which sends in parralel (with user message flow) commands to BLE server which sometime leads to GATT_BUSY. (BLE server is able to handle only one command at time) Closes https://github.com/espressif/esp-idf/issues/1575 Merges https://github.com/espressif/esp-idf/pull/1673
2018-02-11 14:49:38 -05:00
default y
component/bt:Finish all the separate code from BT & BLE
2017-04-20 07:18:05 -04:00
help
component/bt:change the kconfig. 1.change the rowdata to rodata; 2.change BT_ACL_CONNECTIONS to Maximum BT/BLE connection count. 3. change the comments of bt_target.h:505 from 40 to 5.
2017-04-25 22:47:16 -04:00
This option can be disabled when the app work only on gatt client mode
component/bt:Finish all the separate code from BT & BLE
2017-04-20 07:18:05 -04:00
Component/bt: add gatts send service change indication API
2018-09-18 04:20:13 -04:00
choice GATTS_SEND_SERVICE_CHANGE_MODE
prompt "GATTS Service Change Mode"
default GATTS_SEND_SERVICE_CHANGE_AUTO
depends on GATTS_ENABLE
help
Service change indication mode for GATT Server.
config GATTS_SEND_SERVICE_CHANGE_MANUAL
bool "GATTS manually send service change indication"
help
Manually send service change indication through API esp_ble_gatts_send_service_change_indication()
config GATTS_SEND_SERVICE_CHANGE_AUTO
bool "GATTS automatically send service change indication"
help
Let Bluedroid handle the service change indication internally
endchoice
config GATTS_SEND_SERVICE_CHANGE_MODE
int
depends on GATTS_ENABLE
default 0 if GATTS_SEND_SERVICE_CHANGE_AUTO
default 1 if GATTS_SEND_SERVICE_CHANGE_MANUAL
default 0
component/bt:Finish all the separate code from BT & BLE
2017-04-20 07:18:05 -04:00
config GATTC_ENABLE
component/bt:change the kconfig. 1.change the rowdata to rodata; 2.change BT_ACL_CONNECTIONS to Maximum BT/BLE connection count. 3. change the comments of bt_target.h:505 from 40 to 5.
2017-04-25 22:47:16 -04:00
bool "Include GATT client module(GATTC)"
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
depends on BLUEDROID_ENABLED && (BTDM_CONTROLLER_MODE_BTDM || BTDM_CONTROLLER_MODE_BLE_ONLY)
component/bt:Finish all the separate code from BT & BLE
2017-04-20 07:18:05 -04:00
default y
help
This option can be close when the app work only on gatt server mode
Component/bt: fix memory leak
2018-05-22 04:27:01 -04:00
config GATTC_CACHE_NVS_FLASH
bool "Save gattc cache data to nvs flash"
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
depends on GATTC_ENABLE && (BTDM_CONTROLLER_MODE_BTDM || BTDM_CONTROLLER_MODE_BLE_ONLY)
Component/bt: fix memory leak
2018-05-22 04:27:01 -04:00
default n
help
This select can save gattc cache data to nvs flash
component/bt: add constraint in Kconfig to enable SMP_ENABLE when using classic BT 1. For now, some security related functions used in classic Bluetooth are controlled by "SMP_ENABLE". This commit fixes the dependency. 2. The two options, "CLASSIC_BT_ENABLED" and "SMP_ENABLED" The two options will be decoupled in the future.
2017-06-15 03:48:20 -04:00
config BLE_SMP_ENABLE
bool "Include BLE security module(SMP)"
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
depends on BLUEDROID_ENABLED && (BTDM_CONTROLLER_MODE_BTDM || BTDM_CONTROLLER_MODE_BLE_ONLY)
component/bt:Finish all the separate code from BT & BLE
2017-04-20 07:18:05 -04:00
default y
help
This option can be close when the app not used the ble security connect.
Component/bt: fix iOS and win10 compatibility error for HID
2019-02-28 07:39:12 -05:00
config SMP_SLAVE_CON_PARAMS_UPD_ENABLE
bool "Slave enable connection parameters update during pairing"
depends on BLE_SMP_ENABLE
default n
help
In order to reduce the pairing time, slave actively initiates connection parameters update during pairing.
component/bt:Fixted the bug of HCI comment timeout error. 1. remove the SMP_INCLUDED == TRUE insite the btm_find_dev_by_handle function. 2. change the Kconfig with BT_ACL_CONNECTIONS
2017-04-26 04:23:45 -04:00
config BT_STACK_NO_LOG
components/bt: Improve the Bluetooth debug messaging scheme As of now, when Bluetooth debugs are enabled, all the messages are mapped to BT_PRINTF which is mapped to ESP_LOGE. Hence, make monitor shows all logs in red color which might lead to missing the actual errors This patch maps the Bluetooth messages to appropriate ESP_LOG* messages and improves readability. Also, make the BT trace level be configurable in menuconfig, so that each layer of bt trace can be enabled/disabled. Finally, add debug log control for BTC, OSI, BLUFI and clear up Bluetooth debug logs. So, with this the method of enabling Bluetooth logs is as follows: 1. make menuconfig -> Component config -> Bluetooth -> Bluedroid Enable -> BT DEBUG LOG LEVEL -> set trace level for every layer of BT Signed-off-by: Hrishikesh Dhayagude <hrishi@espressif.com>
2018-04-24 22:11:06 -04:00
bool "Disable BT debug logs (minimize bin size)"
component/bt:Fixted the bug of HCI comment timeout error. 1. remove the SMP_INCLUDED == TRUE insite the btm_find_dev_by_handle function. 2. change the Kconfig with BT_ACL_CONNECTIONS
2017-04-26 04:23:45 -04:00
depends on BLUEDROID_ENABLED
default n
help
This select can save the rodata code size
components/bt: Improve the Bluetooth debug messaging scheme As of now, when Bluetooth debugs are enabled, all the messages are mapped to BT_PRINTF which is mapped to ESP_LOGE. Hence, make monitor shows all logs in red color which might lead to missing the actual errors This patch maps the Bluetooth messages to appropriate ESP_LOG* messages and improves readability. Also, make the BT trace level be configurable in menuconfig, so that each layer of bt trace can be enabled/disabled. Finally, add debug log control for BTC, OSI, BLUFI and clear up Bluetooth debug logs. So, with this the method of enabling Bluetooth logs is as follows: 1. make menuconfig -> Component config -> Bluetooth -> Bluedroid Enable -> BT DEBUG LOG LEVEL -> set trace level for every layer of BT Signed-off-by: Hrishikesh Dhayagude <hrishi@espressif.com>
2018-04-24 22:11:06 -04:00
menu "BT DEBUG LOG LEVEL"
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
choice HCI_INITIAL_TRACE_LEVEL
prompt "HCI layer"
default HCI_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for HCI layer
config HCI_TRACE_LEVEL_NONE
bool "NONE"
config HCI_TRACE_LEVEL_ERROR
bool "ERROR"
config HCI_TRACE_LEVEL_WARNING
bool "WARNING"
config HCI_TRACE_LEVEL_API
bool "API"
config HCI_TRACE_LEVEL_EVENT
bool "EVENT"
config HCI_TRACE_LEVEL_DEBUG
bool "DEBUG"
config HCI_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config HCI_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if HCI_TRACE_LEVEL_NONE
default 1 if HCI_TRACE_LEVEL_ERROR
default 2 if HCI_TRACE_LEVEL_WARNING
default 3 if HCI_TRACE_LEVEL_API
default 4 if HCI_TRACE_LEVEL_EVENT
default 5 if HCI_TRACE_LEVEL_DEBUG
default 6 if HCI_TRACE_LEVEL_VERBOSE
default 2
choice BTM_INITIAL_TRACE_LEVEL
prompt "BTM layer"
default BTM_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for BTM layer
config BTM_TRACE_LEVEL_NONE
bool "NONE"
config BTM_TRACE_LEVEL_ERROR
bool "ERROR"
config BTM_TRACE_LEVEL_WARNING
bool "WARNING"
config BTM_TRACE_LEVEL_API
bool "API"
config BTM_TRACE_LEVEL_EVENT
bool "EVENT"
config BTM_TRACE_LEVEL_DEBUG
bool "DEBUG"
config BTM_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config BTM_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if BTM_TRACE_LEVEL_NONE
default 1 if BTM_TRACE_LEVEL_ERROR
default 2 if BTM_TRACE_LEVEL_WARNING
default 3 if BTM_TRACE_LEVEL_API
default 4 if BTM_TRACE_LEVEL_EVENT
default 5 if BTM_TRACE_LEVEL_DEBUG
default 6 if BTM_TRACE_LEVEL_VERBOSE
default 2
choice L2CAP_INITIAL_TRACE_LEVEL
prompt "L2CAP layer"
default L2CAP_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for L2CAP layer
config L2CAP_TRACE_LEVEL_NONE
bool "NONE"
config L2CAP_TRACE_LEVEL_ERROR
bool "ERROR"
config L2CAP_TRACE_LEVEL_WARNING
bool "WARNING"
config L2CAP_TRACE_LEVEL_API
bool "API"
config L2CAP_TRACE_LEVEL_EVENT
bool "EVENT"
config L2CAP_TRACE_LEVEL_DEBUG
bool "DEBUG"
config L2CAP_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config L2CAP_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if L2CAP_TRACE_LEVEL_NONE
default 1 if L2CAP_TRACE_LEVEL_ERROR
default 2 if L2CAP_TRACE_LEVEL_WARNING
default 3 if L2CAP_TRACE_LEVEL_API
default 4 if L2CAP_TRACE_LEVEL_EVENT
default 5 if L2CAP_TRACE_LEVEL_DEBUG
default 6 if L2CAP_TRACE_LEVEL_VERBOSE
default 2
choice RFCOMM_INITIAL_TRACE_LEVEL
prompt "RFCOMM layer"
default RFCOMM_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for RFCOMM layer
config RFCOMM_TRACE_LEVEL_NONE
bool "NONE"
config RFCOMM_TRACE_LEVEL_ERROR
bool "ERROR"
config RFCOMM_TRACE_LEVEL_WARNING
bool "WARNING"
config RFCOMM_TRACE_LEVEL_API
bool "API"
config RFCOMM_TRACE_LEVEL_EVENT
bool "EVENT"
config RFCOMM_TRACE_LEVEL_DEBUG
bool "DEBUG"
config RFCOMM_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config RFCOMM_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if RFCOMM_TRACE_LEVEL_NONE
default 1 if RFCOMM_TRACE_LEVEL_ERROR
default 2 if RFCOMM_TRACE_LEVEL_WARNING
default 3 if RFCOMM_TRACE_LEVEL_API
default 4 if RFCOMM_TRACE_LEVEL_EVENT
default 5 if RFCOMM_TRACE_LEVEL_DEBUG
default 6 if RFCOMM_TRACE_LEVEL_VERBOSE
default 2
choice SDP_INITIAL_TRACE_LEVEL
prompt "SDP layer"
default SDP_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for SDP layer
config SDP_TRACE_LEVEL_NONE
bool "NONE"
config SDP_TRACE_LEVEL_ERROR
bool "ERROR"
config SDP_TRACE_LEVEL_WARNING
bool "WARNING"
config SDP_TRACE_LEVEL_API
bool "API"
config SDP_TRACE_LEVEL_EVENT
bool "EVENT"
config SDP_TRACE_LEVEL_DEBUG
bool "DEBUG"
config SDP_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config SDP_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if SDP_TRACE_LEVEL_NONE
default 1 if SDP_TRACE_LEVEL_ERROR
default 2 if SDP_TRACE_LEVEL_WARNING
default 3 if SDP_TRACE_LEVEL_API
default 4 if SDP_TRACE_LEVEL_EVENT
default 5 if SDP_TRACE_LEVEL_DEBUG
default 6 if SDP_TRACE_LEVEL_VERBOSE
default 2
choice GAP_INITIAL_TRACE_LEVEL
prompt "GAP layer"
default GAP_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for GAP layer
config GAP_TRACE_LEVEL_NONE
bool "NONE"
config GAP_TRACE_LEVEL_ERROR
bool "ERROR"
config GAP_TRACE_LEVEL_WARNING
bool "WARNING"
config GAP_TRACE_LEVEL_API
bool "API"
config GAP_TRACE_LEVEL_EVENT
bool "EVENT"
config GAP_TRACE_LEVEL_DEBUG
bool "DEBUG"
config GAP_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config GAP_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if GAP_TRACE_LEVEL_NONE
default 1 if GAP_TRACE_LEVEL_ERROR
default 2 if GAP_TRACE_LEVEL_WARNING
default 3 if GAP_TRACE_LEVEL_API
default 4 if GAP_TRACE_LEVEL_EVENT
default 5 if GAP_TRACE_LEVEL_DEBUG
default 6 if GAP_TRACE_LEVEL_VERBOSE
default 2
choice BNEP_INITIAL_TRACE_LEVEL
prompt "BNEP layer"
default BNEP_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for BNEP layer
config BNEP_TRACE_LEVEL_NONE
bool "NONE"
config BNEP_TRACE_LEVEL_ERROR
bool "ERROR"
config BNEP_TRACE_LEVEL_WARNING
bool "WARNING"
config BNEP_TRACE_LEVEL_API
bool "API"
config BNEP_TRACE_LEVEL_EVENT
bool "EVENT"
config BNEP_TRACE_LEVEL_DEBUG
bool "DEBUG"
config BNEP_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config BNEP_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if BNEP_TRACE_LEVEL_NONE
default 1 if BNEP_TRACE_LEVEL_ERROR
default 2 if BNEP_TRACE_LEVEL_WARNING
default 3 if BNEP_TRACE_LEVEL_API
default 4 if BNEP_TRACE_LEVEL_EVENT
default 5 if BNEP_TRACE_LEVEL_DEBUG
default 6 if BNEP_TRACE_LEVEL_VERBOSE
default 2
choice PAN_INITIAL_TRACE_LEVEL
prompt "PAN layer"
default PAN_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for PAN layer
config PAN_TRACE_LEVEL_NONE
bool "NONE"
config PAN_TRACE_LEVEL_ERROR
bool "ERROR"
config PAN_TRACE_LEVEL_WARNING
bool "WARNING"
config PAN_TRACE_LEVEL_API
bool "API"
config PAN_TRACE_LEVEL_EVENT
bool "EVENT"
config PAN_TRACE_LEVEL_DEBUG
bool "DEBUG"
config PAN_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config PAN_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if PAN_TRACE_LEVEL_NONE
default 1 if PAN_TRACE_LEVEL_ERROR
default 2 if PAN_TRACE_LEVEL_WARNING
default 3 if PAN_TRACE_LEVEL_API
default 4 if PAN_TRACE_LEVEL_EVENT
default 5 if PAN_TRACE_LEVEL_DEBUG
default 6 if PAN_TRACE_LEVEL_VERBOSE
default 2
choice A2D_INITIAL_TRACE_LEVEL
prompt "A2D layer"
default A2D_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for A2D layer
config A2D_TRACE_LEVEL_NONE
bool "NONE"
config A2D_TRACE_LEVEL_ERROR
bool "ERROR"
config A2D_TRACE_LEVEL_WARNING
bool "WARNING"
config A2D_TRACE_LEVEL_API
bool "API"
config A2D_TRACE_LEVEL_EVENT
bool "EVENT"
config A2D_TRACE_LEVEL_DEBUG
bool "DEBUG"
config A2D_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config A2D_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if A2D_TRACE_LEVEL_NONE
default 1 if A2D_TRACE_LEVEL_ERROR
default 2 if A2D_TRACE_LEVEL_WARNING
default 3 if A2D_TRACE_LEVEL_API
default 4 if A2D_TRACE_LEVEL_EVENT
default 5 if A2D_TRACE_LEVEL_DEBUG
default 6 if A2D_TRACE_LEVEL_VERBOSE
default 2
choice AVDT_INITIAL_TRACE_LEVEL
prompt "AVDT layer"
default AVDT_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for AVDT layer
config AVDT_TRACE_LEVEL_NONE
bool "NONE"
config AVDT_TRACE_LEVEL_ERROR
bool "ERROR"
config AVDT_TRACE_LEVEL_WARNING
bool "WARNING"
config AVDT_TRACE_LEVEL_API
bool "API"
config AVDT_TRACE_LEVEL_EVENT
bool "EVENT"
config AVDT_TRACE_LEVEL_DEBUG
bool "DEBUG"
config AVDT_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config AVDT_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if AVDT_TRACE_LEVEL_NONE
default 1 if AVDT_TRACE_LEVEL_ERROR
default 2 if AVDT_TRACE_LEVEL_WARNING
default 3 if AVDT_TRACE_LEVEL_API
default 4 if AVDT_TRACE_LEVEL_EVENT
default 5 if AVDT_TRACE_LEVEL_DEBUG
default 6 if AVDT_TRACE_LEVEL_VERBOSE
default 2
choice AVCT_INITIAL_TRACE_LEVEL
prompt "AVCT layer"
default AVCT_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for AVCT layer
config AVCT_TRACE_LEVEL_NONE
bool "NONE"
config AVCT_TRACE_LEVEL_ERROR
bool "ERROR"
config AVCT_TRACE_LEVEL_WARNING
bool "WARNING"
config AVCT_TRACE_LEVEL_API
bool "API"
config AVCT_TRACE_LEVEL_EVENT
bool "EVENT"
config AVCT_TRACE_LEVEL_DEBUG
bool "DEBUG"
config AVCT_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config AVCT_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if AVCT_TRACE_LEVEL_NONE
default 1 if AVCT_TRACE_LEVEL_ERROR
default 2 if AVCT_TRACE_LEVEL_WARNING
default 3 if AVCT_TRACE_LEVEL_API
default 4 if AVCT_TRACE_LEVEL_EVENT
default 5 if AVCT_TRACE_LEVEL_DEBUG
default 6 if AVCT_TRACE_LEVEL_VERBOSE
default 2
choice AVRC_INITIAL_TRACE_LEVEL
prompt "AVRC layer"
default AVRC_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for AVRC layer
config AVRC_TRACE_LEVEL_NONE
bool "NONE"
config AVRC_TRACE_LEVEL_ERROR
bool "ERROR"
config AVRC_TRACE_LEVEL_WARNING
bool "WARNING"
config AVRC_TRACE_LEVEL_API
bool "API"
config AVRC_TRACE_LEVEL_EVENT
bool "EVENT"
config AVRC_TRACE_LEVEL_DEBUG
bool "DEBUG"
config AVRC_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config AVRC_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if AVRC_TRACE_LEVEL_NONE
default 1 if AVRC_TRACE_LEVEL_ERROR
default 2 if AVRC_TRACE_LEVEL_WARNING
default 3 if AVRC_TRACE_LEVEL_API
default 4 if AVRC_TRACE_LEVEL_EVENT
default 5 if AVRC_TRACE_LEVEL_DEBUG
default 6 if AVRC_TRACE_LEVEL_VERBOSE
default 2
choice MCA_INITIAL_TRACE_LEVEL
prompt "MCA layer"
default MCA_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for MCA layer
config MCA_TRACE_LEVEL_NONE
bool "NONE"
config MCA_TRACE_LEVEL_ERROR
bool "ERROR"
config MCA_TRACE_LEVEL_WARNING
bool "WARNING"
config MCA_TRACE_LEVEL_API
bool "API"
config MCA_TRACE_LEVEL_EVENT
bool "EVENT"
config MCA_TRACE_LEVEL_DEBUG
bool "DEBUG"
config MCA_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config MCA_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if MCA_TRACE_LEVEL_NONE
default 1 if MCA_TRACE_LEVEL_ERROR
default 2 if MCA_TRACE_LEVEL_WARNING
default 3 if MCA_TRACE_LEVEL_API
default 4 if MCA_TRACE_LEVEL_EVENT
default 5 if MCA_TRACE_LEVEL_DEBUG
default 6 if MCA_TRACE_LEVEL_VERBOSE
default 2
choice HID_INITIAL_TRACE_LEVEL
prompt "HID layer"
default HID_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for HID layer
config HID_TRACE_LEVEL_NONE
bool "NONE"
config HID_TRACE_LEVEL_ERROR
bool "ERROR"
config HID_TRACE_LEVEL_WARNING
bool "WARNING"
config HID_TRACE_LEVEL_API
bool "API"
config HID_TRACE_LEVEL_EVENT
bool "EVENT"
config HID_TRACE_LEVEL_DEBUG
bool "DEBUG"
config HID_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config HID_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if HID_TRACE_LEVEL_NONE
default 1 if HID_TRACE_LEVEL_ERROR
default 2 if HID_TRACE_LEVEL_WARNING
default 3 if HID_TRACE_LEVEL_API
default 4 if HID_TRACE_LEVEL_EVENT
default 5 if HID_TRACE_LEVEL_DEBUG
default 6 if HID_TRACE_LEVEL_VERBOSE
default 2
choice APPL_INITIAL_TRACE_LEVEL
prompt "APPL layer"
default APPL_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for APPL layer
config APPL_TRACE_LEVEL_NONE
bool "NONE"
config APPL_TRACE_LEVEL_ERROR
bool "ERROR"
config APPL_TRACE_LEVEL_WARNING
bool "WARNING"
config APPL_TRACE_LEVEL_API
bool "API"
config APPL_TRACE_LEVEL_EVENT
bool "EVENT"
config APPL_TRACE_LEVEL_DEBUG
bool "DEBUG"
config APPL_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config APPL_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if APPL_TRACE_LEVEL_NONE
default 1 if APPL_TRACE_LEVEL_ERROR
default 2 if APPL_TRACE_LEVEL_WARNING
default 3 if APPL_TRACE_LEVEL_API
default 4 if APPL_TRACE_LEVEL_EVENT
default 5 if APPL_TRACE_LEVEL_DEBUG
default 6 if APPL_TRACE_LEVEL_VERBOSE
default 2
choice GATT_INITIAL_TRACE_LEVEL
prompt "GATT layer"
default GATT_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for GATT layer
config GATT_TRACE_LEVEL_NONE
bool "NONE"
config GATT_TRACE_LEVEL_ERROR
bool "ERROR"
config GATT_TRACE_LEVEL_WARNING
bool "WARNING"
config GATT_TRACE_LEVEL_API
bool "API"
config GATT_TRACE_LEVEL_EVENT
bool "EVENT"
config GATT_TRACE_LEVEL_DEBUG
bool "DEBUG"
config GATT_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config GATT_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if GATT_TRACE_LEVEL_NONE
default 1 if GATT_TRACE_LEVEL_ERROR
default 2 if GATT_TRACE_LEVEL_WARNING
default 3 if GATT_TRACE_LEVEL_API
default 4 if GATT_TRACE_LEVEL_EVENT
default 5 if GATT_TRACE_LEVEL_DEBUG
default 6 if GATT_TRACE_LEVEL_VERBOSE
default 2
choice SMP_INITIAL_TRACE_LEVEL
prompt "SMP layer"
default SMP_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for SMP layer
config SMP_TRACE_LEVEL_NONE
bool "NONE"
config SMP_TRACE_LEVEL_ERROR
bool "ERROR"
config SMP_TRACE_LEVEL_WARNING
bool "WARNING"
config SMP_TRACE_LEVEL_API
bool "API"
config SMP_TRACE_LEVEL_EVENT
bool "EVENT"
config SMP_TRACE_LEVEL_DEBUG
bool "DEBUG"
config SMP_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config SMP_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if SMP_TRACE_LEVEL_NONE
default 1 if SMP_TRACE_LEVEL_ERROR
default 2 if SMP_TRACE_LEVEL_WARNING
default 3 if SMP_TRACE_LEVEL_API
default 4 if SMP_TRACE_LEVEL_EVENT
default 5 if SMP_TRACE_LEVEL_DEBUG
default 6 if SMP_TRACE_LEVEL_VERBOSE
default 2
choice BTIF_INITIAL_TRACE_LEVEL
prompt "BTIF layer"
default BTIF_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for BTIF layer
config BTIF_TRACE_LEVEL_NONE
bool "NONE"
config BTIF_TRACE_LEVEL_ERROR
bool "ERROR"
config BTIF_TRACE_LEVEL_WARNING
bool "WARNING"
config BTIF_TRACE_LEVEL_API
bool "API"
config BTIF_TRACE_LEVEL_EVENT
bool "EVENT"
config BTIF_TRACE_LEVEL_DEBUG
bool "DEBUG"
config BTIF_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config BTIF_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if BTIF_TRACE_LEVEL_NONE
default 1 if BTIF_TRACE_LEVEL_ERROR
default 2 if BTIF_TRACE_LEVEL_WARNING
default 3 if BTIF_TRACE_LEVEL_API
default 4 if BTIF_TRACE_LEVEL_EVENT
default 5 if BTIF_TRACE_LEVEL_DEBUG
default 6 if BTIF_TRACE_LEVEL_VERBOSE
default 2
choice BTC_INITIAL_TRACE_LEVEL
prompt "BTC layer"
default BTC_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for BTC layer
config BTC_TRACE_LEVEL_NONE
bool "NONE"
config BTC_TRACE_LEVEL_ERROR
bool "ERROR"
config BTC_TRACE_LEVEL_WARNING
bool "WARNING"
config BTC_TRACE_LEVEL_API
bool "API"
config BTC_TRACE_LEVEL_EVENT
bool "EVENT"
config BTC_TRACE_LEVEL_DEBUG
bool "DEBUG"
config BTC_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config BTC_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if BTC_TRACE_LEVEL_NONE
default 1 if BTC_TRACE_LEVEL_ERROR
default 2 if BTC_TRACE_LEVEL_WARNING
default 3 if BTC_TRACE_LEVEL_API
default 4 if BTC_TRACE_LEVEL_EVENT
default 5 if BTC_TRACE_LEVEL_DEBUG
default 6 if BTC_TRACE_LEVEL_VERBOSE
default 2
choice OSI_INITIAL_TRACE_LEVEL
prompt "OSI layer"
default OSI_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for OSI layer
config OSI_TRACE_LEVEL_NONE
bool "NONE"
config OSI_TRACE_LEVEL_ERROR
bool "ERROR"
config OSI_TRACE_LEVEL_WARNING
bool "WARNING"
config OSI_TRACE_LEVEL_API
bool "API"
config OSI_TRACE_LEVEL_EVENT
bool "EVENT"
config OSI_TRACE_LEVEL_DEBUG
bool "DEBUG"
config OSI_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config OSI_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if OSI_TRACE_LEVEL_NONE
default 1 if OSI_TRACE_LEVEL_ERROR
default 2 if OSI_TRACE_LEVEL_WARNING
default 3 if OSI_TRACE_LEVEL_API
default 4 if OSI_TRACE_LEVEL_EVENT
default 5 if OSI_TRACE_LEVEL_DEBUG
default 6 if OSI_TRACE_LEVEL_VERBOSE
default 2
choice BLUFI_INITIAL_TRACE_LEVEL
prompt "BLUFI layer"
default BLUFI_TRACE_LEVEL_WARNING
depends on BLUEDROID_ENABLED && !BT_STACK_NO_LOG
help
Define BT trace level for BLUFI layer
config BLUFI_TRACE_LEVEL_NONE
bool "NONE"
config BLUFI_TRACE_LEVEL_ERROR
bool "ERROR"
config BLUFI_TRACE_LEVEL_WARNING
bool "WARNING"
config BLUFI_TRACE_LEVEL_API
bool "API"
config BLUFI_TRACE_LEVEL_EVENT
bool "EVENT"
config BLUFI_TRACE_LEVEL_DEBUG
bool "DEBUG"
config BLUFI_TRACE_LEVEL_VERBOSE
bool "VERBOSE"
endchoice
config BLUFI_INITIAL_TRACE_LEVEL
int
depends on BLUEDROID_ENABLED
default 0 if BLUFI_TRACE_LEVEL_NONE
default 1 if BLUFI_TRACE_LEVEL_ERROR
default 2 if BLUFI_TRACE_LEVEL_WARNING
default 3 if BLUFI_TRACE_LEVEL_API
default 4 if BLUFI_TRACE_LEVEL_EVENT
default 5 if BLUFI_TRACE_LEVEL_DEBUG
default 6 if BLUFI_TRACE_LEVEL_VERBOSE
default 2
endmenu #BT DEBUG LOG LEVEL
component/bt:Change the bt Kconfig BT_ACL_CONNECTIONS type from choice to int(range).
2017-04-26 05:27:21 -04:00
config BT_ACL_CONNECTIONS
int "BT/BLE MAX ACL CONNECTIONS(1~7)"
component/bt:Finish all the separate code from BT & BLE
2017-04-20 07:18:05 -04:00
depends on BLUEDROID_ENABLED
component/bt:Change the bt Kconfig BT_ACL_CONNECTIONS type from choice to int(range).
2017-04-26 05:27:21 -04:00
range 1 7
default 4
bt: Add option to ena/dis BLE service change registration Add option to enable/disable automatic registration of BLE Gattc service change notify. Which sends in parralel (with user message flow) commands to BLE server which sometime leads to GATT_BUSY. (BLE server is able to handle only one command at time) Closes https://github.com/espressif/esp-idf/issues/1575 Merges https://github.com/espressif/esp-idf/pull/1673
2018-02-11 14:49:38 -05:00
help
component/bt:change the kconfig. 1.change the rowdata to rodata; 2.change BT_ACL_CONNECTIONS to Maximum BT/BLE connection count. 3. change the comments of bt_target.h:505 from 40 to 5.
2017-04-25 22:47:16 -04:00
Maximum BT/BLE connection count
component/bt:Finish all the separate code from BT & BLE
2017-04-20 07:18:05 -04:00
component/bt: Added the bluedroid environment variable dynomic malloc support & support to malloc the memory to the psram. component/bt: Added the Macro for the classic BT support. component/bt: added the bluedroid deinit method. component/bt: allow more classic BT global variables to use dynamic allocation scheme 1. allocate memory for AVDT, AVCT control blocks when dynamic memory is used 2. allow SBC decoder buffer to use dynamic allocation scheme component/bt: Remove the wrong changes in bt/Kconfig & Added the GATTS_INCLUDED in the gatt_free function when gatt service close. component/bt: Shorten the abbreviation BT_ALLOCATION_FROM_SPIRAM_FIRST and BT_BLE_DYNAMIC_ENV_MEMORY two macros.
2017-10-18 03:34:43 -04:00
config BT_ALLOCATION_FROM_SPIRAM_FIRST
bool "BT/BLE will first malloc the memory from the PSRAM"
depends on BLUEDROID_ENABLED
default n
help
This select can save the internal RAM if there have the PSRAM
config BT_BLE_DYNAMIC_ENV_MEMORY
bool "Use dynamic memory allocation in BT/BLE stack"
depends on BLUEDROID_ENABLED
default n
help
This select can make the allocation of memory will become more flexible
Component/bt: fix hci_hal_env.rx_q and xHciH4Queue blocking when scanning
2018-07-01 22:59:51 -04:00
config BLE_HOST_QUEUE_CONGESTION_CHECK
bool "BLE queue congestion check"
depends on BLUEDROID_ENABLED
default n
help
component/bt: Add Legacy Pairing
2018-09-04 09:11:03 -04:00
When scanning and scan duplicate is not enabled, if there are a lot of adv packets around or application layer
handling adv packets is slow, it will cause the controller memory to run out. if enabled, adv packets will be
Component/bt: fix hci_hal_env.rx_q and xHciH4Queue blocking when scanning
2018-07-01 22:59:51 -04:00
lost when host queue is congested.
component/bt: add constraint in Kconfig to enable SMP_ENABLE when using classic BT 1. For now, some security related functions used in classic Bluetooth are controlled by "SMP_ENABLE". This commit fixes the dependency. 2. The two options, "CLASSIC_BT_ENABLED" and "SMP_ENABLED" The two options will be decoupled in the future.
2017-06-15 03:48:20 -04:00
config SMP_ENABLE
bool
depends on BLUEDROID_ENABLED
default CLASSIC_BT_ENABLED || BLE_SMP_ENABLE
bt: Add option to ena/dis BLE service change registration Add option to enable/disable automatic registration of BLE Gattc service change notify. Which sends in parralel (with user message flow) commands to BLE server which sometime leads to GATT_BUSY. (BLE server is able to handle only one command at time) Closes https://github.com/espressif/esp-idf/issues/1575 Merges https://github.com/espressif/esp-idf/pull/1673
2018-02-11 14:49:38 -05:00
component/bt: add a option to make report adv data and scan response individually Originally, when doing BLE active scan, Bluedroid will not report adv to application layer until receive scan response. This option is used to disable the behavior. When enable this option, Bluedroid will report adv data or scan response to application layer immediately.
2019-01-23 01:11:56 -05:00
config BLE_ACTIVE_SCAN_REPORT_ADV_SCAN_RSP_INDIVIDUALLY
bool "Report adv data and scan response individually when BLE active scan"
depends on BLUEDROID_ENABLED && (BTDM_CONTROLLER_MODE_BTDM || BTDM_CONTROLLER_MODE_BLE_ONLY)
default n
help
Originally, when doing BLE active scan, Bluedroid will not report adv to application layer
until receive scan response. This option is used to disable the behavior. When enable this option,
Bluedroid will report adv data or scan response to application layer immediately.
esp32: Pass memory layout linker script through C preprocessor C preprocessor is a bit icky, but with ULP we will have 3 possible variables influencing the memory layout and 9 linker scripts is too many!
2016-09-20 21:04:16 -04:00
# Memory reserved at start of DRAM for Bluetooth stack
Component/bt: add ble link timeout config in menuconfig - add ble link timeout config in menuconfig - disable background connection when call gatts_open
2019-04-15 23:11:08 -04:00
config BLE_ESTABLISH_LINK_CONNECTION_TIMEOUT
int "Timeout of BLE connection establishment"
depends on BLUEDROID_ENABLED
range 1 60
default 30
help
Bluetooth Connection establishment maximum time, if connection time exceeds this value, the connection
establishment fails, ESP_GATTC_OPEN_EVT or ESP_GATTS_OPEN_EVT is triggered.
esp32: Pass memory layout linker script through C preprocessor C preprocessor is a bit icky, but with ULP we will have 3 possible variables influencing the memory layout and 9 linker scripts is too many!
2016-09-20 21:04:16 -04:00
config BT_RESERVE_DRAM
hex
component/bt : decrease memory consumption by conn number 1. BLE only with 9(max) connection will decrease 3K DRAM 2. BR/EDR only with 7(max) connection will decrease 16K DRAM 3. Any of BLE or BR/EDR connection number decrease will also decrease DRAM consumption 4. Decrease one BLE connection will save about 1KB DRAM 5. Decrease one BR/EDR ACL connection will save about 1.2KB DRAM 6. Decrease one BR/EDR SCO/eSCO will save 2KB DRAM. 7. fix some definition and kconfig 8. remove 1.2k of vhci tx cache and make .bss & .data to heap about 1.4K 9. modify BT Reserved Memory size and modify example to support new bt kconfig
2018-06-15 09:40:51 -04:00
default 0xdb5c if BT_ENABLED
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 01:24:58 -04:00
default 0
component/bt : fix bug of sw interrupt cause to run btdm to different cpu core. 1. add sw interrupt cause osi to controller. 2. modify the kconfig to improve the option view. 3. add option of the cpu core which bluedroid run. 4. add option of the cpu core which bluetooth controller run.
2017-10-20 05:09:03 -04:00
endmenu
Reference in New Issue Copy Permalink