Marcin Niestroj 0b59257d93 drivers: wifi: esp32: create event handling thread in runtime ... Commit 95b916d104 ("drivers: wifi: esp32: fix reconnect issue") switched from thread created at runtime to statically defined thread. The difference is mainly visible for simple applications that use CONFIG_NET_CONFIG_AUTO_INIT=y, where networking setup code is executed before main() and any statically defined threads. All ESP32 events are just queued and never handled, so conditions enforced by CONFIG_NET_CONFIG_NEED_IPV4=y are never met (e.g. Zephyr networking layer is never informed about being connected). Switch back to thread created at runtime, which starts at the moment when k_thread_create() is invoked. This allows ESP32 event processing to happen just after ESP32 WiFi driver gets initialized and before Zephyr network auto initialization code (CONFIG_NET_CONFIG_AUTO_INIT=y). Signed-off-by: Marcin Niestroj <m.niestroj@emb.dev>		2021-06-08 11:15:38 -05:00
..
esp32	drivers: wifi: esp32: create event handling thread in runtime	2021-06-08 11:15:38 -05:00
esp_at	drivers: wifi: esp: stop using pkt->work in TX path	2021-05-07 13:10:01 +02:00
eswifi	drivers: wifi: eswifi: fix swapped protocols in eswifi_off_getaddrinfo	2021-05-25 16:59:17 -05:00
simplelink	drivers: wifi: remove usage of device_pm_control_nop	2021-04-28 12:25:39 -04:00
winc1500	drivers: wifi: remove usage of device_pm_control_nop	2021-04-28 12:25:39 -04:00
CMakeLists.txt	drivers: wifi: esp_at: rename driver from esp	2021-05-06 13:21:39 -04:00
Kconfig	drivers: wifi: esp_at: rename driver from esp	2021-05-06 13:21:39 -04:00