From dcc310f468ac6e8704ba49c799cd32681d27b3d0 Mon Sep 17 00:00:00 2001 From: Shen Weilong Date: Fri, 2 Dec 2022 14:22:53 +0800 Subject: [PATCH] Explain how mush memory that will be used by each connection/advertiser. --- components/bt/controller/esp32c2/Kconfig.in | 3 ++- components/bt/controller/esp32h2/Kconfig.in | 3 ++- components/bt/host/nimble/Kconfig.in | 3 +++ 3 files changed, 7 insertions(+), 2 deletions(-) diff --git a/components/bt/controller/esp32c2/Kconfig.in b/components/bt/controller/esp32c2/Kconfig.in index 6cb2bddd4b0d..4c2ac499a9c1 100644 --- a/components/bt/controller/esp32c2/Kconfig.in +++ b/components/bt/controller/esp32c2/Kconfig.in @@ -128,6 +128,7 @@ if BT_LE_EXT_ADV instances. Minimum there is always one instance of advertising. Enter how many more advertising instances you want. + Each extended advertising instance will take about 0.5k DRAM. config BT_LE_EXT_ADV_MAX_SIZE int "Maximum length of the advertising data." @@ -339,7 +340,7 @@ config BT_LE_MAX_CONNECTIONS is expected to configure BTDM_CTRL_BLE_MAX_CONN from controller menu along with this option. Similarly for ESP32-C3 or ESP32-S3, user is expected to configure BT_CTRL_BLE_MAX_ACT from controller menu. - + Each connection will take about 1k DRAM. choice BT_LE_COEX_PHY_CODED_TX_RX_TLIM prompt "Coexistence: limit on MAX Tx/Rx time for coded-PHY connection" diff --git a/components/bt/controller/esp32h2/Kconfig.in b/components/bt/controller/esp32h2/Kconfig.in index 88f42b87f77c..bdd492b7b0fc 100644 --- a/components/bt/controller/esp32h2/Kconfig.in +++ b/components/bt/controller/esp32h2/Kconfig.in @@ -128,6 +128,7 @@ if BT_LE_EXT_ADV instances. Minimum there is always one instance of advertising. Enter how many more advertising instances you want. + Each extended advertising instance will take about 0.5k DRAM. config BT_LE_EXT_ADV_MAX_SIZE int "Maximum length of the advertising data." @@ -339,7 +340,7 @@ config BT_LE_MAX_CONNECTIONS is expected to configure BTDM_CTRL_BLE_MAX_CONN from controller menu along with this option. Similarly for ESP32-C3 or ESP32-S3, user is expected to configure BT_CTRL_BLE_MAX_ACT from controller menu. - + Each connection will take about 1k DRAM. choice BT_LE_COEX_PHY_CODED_TX_RX_TLIM prompt "Coexistence: limit on MAX Tx/Rx time for coded-PHY connection" diff --git a/components/bt/host/nimble/Kconfig.in b/components/bt/host/nimble/Kconfig.in index 8c174af5c3b7..754a0af5e9b2 100644 --- a/components/bt/host/nimble/Kconfig.in +++ b/components/bt/host/nimble/Kconfig.in @@ -75,6 +75,7 @@ config BT_NIMBLE_MAX_CONNECTIONS is expected to configure BTDM_CTRL_BLE_MAX_CONN from controller menu along with this option. Similarly for ESP32-C3 or ESP32-S3, user is expected to configure BT_CTRL_BLE_MAX_ACT from controller menu. + For ESP32C2, ESP32C6 and ESP32H2, each connection will take about 1k DRAM. config BT_NIMBLE_MAX_BONDS int "Maximum number of bonds to save across reboots" @@ -538,6 +539,8 @@ if BT_NIMBLE_EXT_ADV instances. Minimum there is always one instance of advertising. Enter how many more advertising instances you want. + For ESP32C2, ESP32C6 and ESP32H2, each extended advertising instance + will take about 0.5k DRAM. config BT_NIMBLE_EXT_ADV_MAX_SIZE int "Maximum length of the advertising data."