docs: update document to remove dependency of esp32 on secure element usage

components/tcp_transport/include/esp_transport_ssl.h

@@ -166,7 +166,7 @@ void esp_transport_ssl_set_common_name(esp_transport_handle_t t, const char *com
 /**
  * @brief      Set the ssl context to use secure element (atecc608a) for client(device) private key and certificate
  *
- * @note       Recommended to be used with ESP32 interfaced to ATECC608A based secure element
+ * @note       Recommended to be used with ESP32 series interfaced to ATECC608A based secure element
  *
  * @param      t     ssl transport
  */

docs/en/api-reference/protocols/esp_http_client.rst

@@ -32,19 +32,17 @@ Persistent connection means that the HTTP client can reuse the same connection f
 
 To allow ESP HTTP client to take full advantage of persistent connections, one should make as many requests as possible using the same handle instance. Check out the example functions ``http_rest_with_url`` and ``http_rest_with_hostname_path`` in the application example. Here, once the connection is created, multiple requests (``GET``, ``POST``, ``PUT``, etc.) are made before the connection is closed.
 
-.. only:: esp32
+Use Secure Element (ATECC608) for TLS
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-    Use Secure Element (ATECC608) for TLS
+A secure element (ATECC608) can be also used for the underlying TLS connection in the HTTP client connection. Please refer to the **ATECC608A (Secure Element) with ESP-TLS** section in the :doc:`ESP-TLS documentation </api-reference/protocols/esp_tls>` for more details. The secure element support has to be first enabled in menuconfig through :ref:`CONFIG_ESP_TLS_USE_SECURE_ELEMENT`. Then the HTTP client can be configured to use secure element as follows:
-    _____________________________________
 
-    A secure element (ATECC608) can be also used for the underlying TLS connection in the HTTP client connection. Please refer to the **ATECC608A (Secure Element) with ESP-TLS** section in the :doc:`ESP-TLS documentation </api-reference/protocols/esp_tls>` for more details. The secure element support has to be first enabled in menuconfig through :ref:`CONFIG_ESP_TLS_USE_SECURE_ELEMENT`. Then the HTTP client can be configured to use secure element as follows:
+.. code-block:: c
 
-    .. code-block:: c
+    esp_http_client_config_t cfg = {
-
+        /* other configurations options */
-        esp_http_client_config_t cfg = {
+        .use_secure_element = true,
-            /* other configurations options */
+    };
-            .use_secure_element = true,
-        };
 
 
 HTTPS Request

docs/en/api-reference/protocols/esp_tls.rst

@@ -138,39 +138,37 @@ The following table shows a typical comparison between WolfSSL and MbedTLS when
 
     These values can vary based on configuration options and version of respective libraries.
 
-.. only:: esp32
+ATECC608A (Secure Element) with ESP-TLS
+--------------------------------------------------
 
-    ATECC608A (Secure Element) with ESP-TLS
+ESP-TLS provides support for using ATECC608A cryptoauth chip with ESP32 series of SoCs. The use of ATECC608A is supported only when ESP-TLS is used with MbedTLS as its underlying SSL/TLS stack. ESP-TLS uses MbedTLS as its underlying TLS/SSL stack by default unless changed manually.
-    --------------------------------------------------
 
-    ESP-TLS provides support for using ATECC608A cryptoauth chip with ESP32 series of SoCs. The use of ATECC608A is supported only when ESP-TLS is used with MbedTLS as its underlying SSL/TLS stack. ESP-TLS uses MbedTLS as its underlying TLS/SSL stack by default unless changed manually.
+.. note::
 
-    .. note::
+    ATECC608A chip interfaced to ESP32 series must be already configured. For details, please refer to `esp_cryptoauth_utility <https://github.com/espressif/esp-cryptoauthlib/blob/master/esp_cryptoauth_utility/README.md#esp_cryptoauth_utility>`_.
 
-        ATECC608A chip interfaced to ESP32 must be already configured. For details, please refer to `esp_cryptoauth_utility <https://github.com/espressif/esp-cryptoauthlib/blob/master/esp_cryptoauth_utility/README.md#esp_cryptoauth_utility>`_.
+To enable the secure element support, and use it in your project for TLS connection, you have to follow the below steps:
 
-    To enable the secure element support, and use it in your project for TLS connection, you have to follow the below steps:
+1) Add `esp-cryptoauthlib <https://github.com/espressif/esp-cryptoauthlib>`_ in your project, for details please refer `how to use esp-cryptoauthlib with ESP-IDF <https://github.com/espressif/esp-cryptoauthlib#how-to-use-esp-cryptoauthlib-with-esp-idf>`_.
 
-    1) Add `esp-cryptoauthlib <https://github.com/espressif/esp-cryptoauthlib>`_ in your project, for details please refer `how to use esp-cryptoauthlib with ESP-IDF <https://github.com/espressif/esp-cryptoauthlib#how-to-use-esp-cryptoauthlib-with-esp-idf>`_.
+2) Enable the following menuconfig option::
 
-    2) Enable the following menuconfig option::
+    menuconfig > Component config > ESP-TLS > Use Secure Element (ATECC608A) with ESP-TLS
 
-        menuconfig > Component config > ESP-TLS > Use Secure Element (ATECC608A) with ESP-TLS
+3) Select type of ATECC608A chip with following option::
 
-    3) Select type of ATECC608A chip with following option::
+    menuconfig > Component config > esp-cryptoauthlib > Choose Type of ATECC608A chip
 
-        menuconfig > Component config > esp-cryptoauthlib > Choose Type of ATECC608A chip
+To know more about different types of ATECC608A chips and how to obtain the type of ATECC608A connected to your ESP module, please visit `ATECC608A chip type <https://github.com/espressif/esp-cryptoauthlib/blob/master/esp_cryptoauth_utility/README.md#find-type-of-atecc608a-chip-connected-to-esp32-wroom32-se>`_.
 
-    To know more about different types of ATECC608A chips and how to obtain the type of ATECC608A connected to your ESP module, please visit `ATECC608A chip type <https://github.com/espressif/esp-cryptoauthlib/blob/master/esp_cryptoauth_utility/README.md#find-type-of-atecc608a-chip-connected-to-esp32-wroom32-se>`_.
+4) Enable the use of ATECC608A in ESP-TLS by providing the following config option in :cpp:type:`esp_tls_cfg_t`.
 
-    4) Enable the use of ATECC608A in ESP-TLS by providing the following config option in :cpp:type:`esp_tls_cfg_t`.
+.. code-block:: c
 
-    .. code-block:: c
+        esp_tls_cfg_t cfg = {
-
+            /* other configurations options */
-            esp_tls_cfg_t cfg = {
+            .use_secure_element = true,
-                /* other configurations options */
+        };
-                .use_secure_element = true,
-            };
 
 .. only:: SOC_DIG_SIGN_SUPPORTED
 

docs/en/api-reference/protocols/mqtt.rst

@@ -154,7 +154,7 @@ It is possible to set authentication parameters through the :cpp:class:`authenti
 
  * :cpp:member:`password <esp_mqtt_client_config_t::credentials_t::authentication_t::password>`: use a password by setting
  * :cpp:member:`certificate <esp_mqtt_client_config_t::credentials_t::authentication_t::certificate>` and :cpp:member:`key <esp_mqtt_client_config_t::credentials_t::authentication_t::key>`: mutual authentication with TLS, and both can be provided in PEM or DER format
- * :cpp:member:`use_secure_element <esp_mqtt_client_config_t::credentials_t::authentication_t::use_secure_element>`: use secure element (ATECC608A) interfaced to ESP32
+ * :cpp:member:`use_secure_element <esp_mqtt_client_config_t::credentials_t::authentication_t::use_secure_element>`: use secure element (ATECC608A) interfaced to ESP32 series
  * :cpp:member:`ds_data <esp_mqtt_client_config_t::credentials_t::authentication_t::ds_data>`: use Digital Signature Peripheral available in some Espressif devices
 
 Session