drivers: wifi: esp_at: fix AT+CIPSEND premature timeout

For TCP socket, this fixes AT+CIPSEND command with too short timeout.
ESP modem replies SEND OK/SEND FAIL dependent on network traffic
condition, so this timeout config changes as Kconfig option for being
configurable by user.

Signed-off-by: Chun-Chieh Li <[email protected]>

Author: ccli8

drivers/wifi/esp_at/Kconfig.esp_at

@@ -99,6 +99,14 @@ config WIFI_ESP_AT_RX_NET_PKT_ALLOC_TIMEOUT
 	help
 	  Network interface RX net_pkt allocation timeout in milliseconds.
 
+config WIFI_ESP_AT_TCP_SEND_TIMEOUT
+	int "TCP socket send timeout"
+	default 30000
+	help
+	  For TCP socket, how long to wait in milliseconds for device
+	  to reply SEND OK/SEND FAIL after AT+CIPSEND has been sent.
+	  This can vary with network traffic condition.
+
 choice
 	prompt "ESP IP Address configuration"
 	default WIFI_ESP_AT_IP_DHCP

drivers/wifi/esp_at/esp_offload.c

@@ -20,6 +20,9 @@ LOG_MODULE_REGISTER(wifi_esp_at_offload, CONFIG_WIFI_LOG_LEVEL);
 
 #include "esp.h"
 
+#define TCP_SEND_TIMEOUT                                        \
+	K_MSEC(CONFIG_WIFI_ESP_AT_TCP_SEND_TIMEOUT)
+
 static int esp_listen(struct net_context *context, int backlog)
 {
 	return -ENOTSUP;
@@ -330,7 +333,11 @@ static int _sock_send(struct esp_socket *sock, struct net_pkt *pkt)
 	}
 
 	/* Wait for 'SEND OK' or 'SEND FAIL' */
-	ret = k_sem_take(&dev->sem_response, ESP_CMD_TIMEOUT);
+	if (esp_socket_ip_proto(sock) == IPPROTO_TCP) {
+		ret = k_sem_take(&dev->sem_response, TCP_SEND_TIMEOUT);
+	} else {
+		ret = k_sem_take(&dev->sem_response, ESP_CMD_TIMEOUT);
+	}
 	if (ret < 0) {
 		LOG_DBG("No send response");
 		goto out;