docs: update docs with S3 specific information.

docs/en/api-reference/peripherals/sd_pullup_requirements.rst

@@ -7,6 +7,12 @@ SD Pull-up Requirements
 
         This document is not updated for ESP32-C3 yet.
 
+.. only:: esp32s3
+
+    .. warning::
+
+        This document is not updated for ESP32-S3 yet.
+
 Espressif hardware products are designed for multiple use cases which may require different pull states on pins. For this reason, the pull state of particular pins on certain products will need to be adjusted to provide the pull-ups required in the SD bus.
 
 SD pull-up requirements apply to cases where {IDF_TARGET_NAME} uses the SPI controller to communicate with SD cards. When an SD card is operating in SPI mode or 1-bit SD mode, the CMD and DATA (DAT0 - DAT3) lines of the SD bus must be pulled up by 10 kOhm resistors. Slaves should also have pull-ups on all above-mentioned lines (regardless of whether these lines are connected to the host) in order to prevent SD cards from entering a wrong state.

docs/en/api-reference/peripherals/sdio_slave.rst

@@ -7,6 +7,12 @@ SDIO Card Slave Driver
 
         This document is not updated for ESP32-C3 yet.
 
+.. only:: esp32s3
+
+    .. warning::
+
+        This document is not updated for ESP32-S3 yet.
+
 Overview
 --------
 
@@ -189,9 +195,9 @@ To allow the host sending data to the slave, the application has to load buffers
 1. Register the buffer by calling ``sdio_slave_recv_register_buf``, and get the handle of the registered buffer. The driver
    will allocate memory for the linked-list descriptor needed to link the buffer onto the hardware. The size of these buffers should equal to the Receiving buffer size.
 2. Load buffers onto the driver by passing the buffer handle to ``sdio_slave_recv_load_buf``.
-3. Get the received data by calling ``sdio_slave_recv`` or ``sdio_slave_recv_packet``. If non-blocking call is needed, set ``wait=0``. 
+3. Get the received data by calling ``sdio_slave_recv`` or ``sdio_slave_recv_packet``. If non-blocking call is needed, set ``wait=0``.
 
-   The difference between two APIs is that, ``sdio_slave_recv_packet`` gives more information about packet, which can consist of several buffers. When ``ESP_ERR_NOT_FINISHED`` is returned by this API, you should call this API iteratively until the return value is ``ESP_OK``. All the continuous buffers returned with ``ESP_ERR_NOT_FINISHED``, together with the last buffer returned with ``ESP_OK``, belong to one packet from the host. Call ``sdio_slave_recv_get_buf`` to get the address of the received data, and the actual length received in each buffer. The packet length is the sum of received length of all the buffers in the packet. 
+   The difference between two APIs is that, ``sdio_slave_recv_packet`` gives more information about packet, which can consist of several buffers. When ``ESP_ERR_NOT_FINISHED`` is returned by this API, you should call this API iteratively until the return value is ``ESP_OK``. All the continuous buffers returned with ``ESP_ERR_NOT_FINISHED``, together with the last buffer returned with ``ESP_OK``, belong to one packet from the host. Call ``sdio_slave_recv_get_buf`` to get the address of the received data, and the actual length received in each buffer. The packet length is the sum of received length of all the buffers in the packet.
 
    If the host never send data longer than the Receiving buffer size, or you don't care about the packet boundary (e.g. the data is only a byte stream), you can call the simpler version ``sdio_slave_recv`` instead.
 

docs/en/api-reference/peripherals/sdmmc_host.rst

@@ -7,6 +7,13 @@ SDMMC Host Driver
 
         This document is not updated for ESP32-C3 yet.
 
+
+.. only:: esp32s3
+
+    .. warning::
+
+        This document is not updated for ESP32-S3 yet.
+
 Overview
 --------
 

docs/en/api-reference/peripherals/temp_sensor.rst

@@ -1,6 +1,12 @@
 Temperature Sensor
 ===================
 
+.. only:: esp32s3
+
+    .. warning::
+
+        This feature is not supported in v4.4
+
 Overview
 --------