Help

Select type of WiFi TX buffers:

If "Static" is selected, WiFi TX buffers are allocated when WiFi is
initialized and released when WiFi is de-initialized. The size of each
static TX buffer is fixed to about 1.6KB.

If "Dynamic" is selected, each WiFi TX buffer is allocated as needed
when a data frame is delivered to the Wifi driver from the TCP/IP stack.
The buffer is freed after the data frame has been sent by the WiFi driver.
The size of each dynamic TX buffer depends on the length of each data
frame sent by the TCP/IP layer.

If PSRAM is enabled, "Static" should be selected to guarantee enough
WiFi TX buffers. If PSRAM is disabled, "Dynamic" should be selected
to improve the utilization of RAM.

Direct dependencies

WIFI_ESP32 && WIFI

(Includes any dependencies from ifs and menus.)

Default

ESP32_WIFI_DYNAMIC_TX_BUFFER

Choice options

Kconfig definition

At <Zephyr>/drivers/wifi/esp32/Kconfig.esp32:76

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:42 → <Zephyr>/drivers/Kconfig:78 → <Zephyr>/drivers/wifi/Kconfig:36

Menu path: (Top) → Device Drivers → Wi-Fi Drivers → ESP32 SoC WiFi support

choice ESP32_WIFI_TX_BUFFER
    bool "Type of WiFi TX buffers"
    default ESP32_WIFI_DYNAMIC_TX_BUFFER
    depends on WIFI_ESP32 && WIFI
    help
      Select type of WiFi TX buffers:

      If "Static" is selected, WiFi TX buffers are allocated when WiFi is
      initialized and released when WiFi is de-initialized. The size of each
      static TX buffer is fixed to about 1.6KB.

      If "Dynamic" is selected, each WiFi TX buffer is allocated as needed
      when a data frame is delivered to the Wifi driver from the TCP/IP stack.
      The buffer is freed after the data frame has been sent by the WiFi driver.
      The size of each dynamic TX buffer depends on the length of each data
      frame sent by the TCP/IP layer.

      If PSRAM is enabled, "Static" should be selected to guarantee enough
      WiFi TX buffers. If PSRAM is disabled, "Dynamic" should be selected
      to improve the utilization of RAM.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)