diff --git a/docs/en/api-reference/peripherals/i2s.rst b/docs/en/api-reference/peripherals/i2s.rst index 825d524a43..feb582dc25 100644 --- a/docs/en/api-reference/peripherals/i2s.rst +++ b/docs/en/api-reference/peripherals/i2s.rst @@ -1,6 +1,12 @@ I2S === +.. only:: esp32c3 + + .. warning:: + + This document is not updated for ESP32-C3 yet. + Overview -------- diff --git a/docs/en/api-reference/peripherals/sd_pullup_requirements.rst b/docs/en/api-reference/peripherals/sd_pullup_requirements.rst index 38baa4c117..128fb1750a 100644 --- a/docs/en/api-reference/peripherals/sd_pullup_requirements.rst +++ b/docs/en/api-reference/peripherals/sd_pullup_requirements.rst @@ -1,6 +1,12 @@ SD Pull-up Requirements ======================= +.. only:: esp32c3 + + .. warning:: + + This document is not updated for ESP32-C3 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. diff --git a/docs/en/api-reference/peripherals/sdio_slave.rst b/docs/en/api-reference/peripherals/sdio_slave.rst index 836404576c..a02ed1525c 100644 --- a/docs/en/api-reference/peripherals/sdio_slave.rst +++ b/docs/en/api-reference/peripherals/sdio_slave.rst @@ -1,6 +1,12 @@ SDIO Card Slave Driver ====================== +.. only:: esp32c3 + + .. warning:: + + This document is not updated for ESP32-C3 yet. + Overview -------- @@ -94,7 +100,7 @@ The SDIO slave driver uses the following terms: - Sending: slave to host transfers. - Receiving: host to slave transfers. -.. note:: Register names in *{IDF_TARGET_NAME} Technical Reference Manual* > *SDIO Slave Controller* +.. note:: Register names in *{IDF_TARGET_NAME} Technical Reference Manual* > *SDIO Slave Controller* [`PDF <{IDF_TARGET_TRM_EN_URL}#sdioslave>`__] are oriented from the point of view of the host, i.e. 'rx' registers refer to sending, while 'tx' registers refer to receiving. We're not using `tx` or `rx` in the driver to avoid ambiguities. diff --git a/docs/en/api-reference/peripherals/sdmmc_host.rst b/docs/en/api-reference/peripherals/sdmmc_host.rst index e2898a3bd8..3ee6a63897 100644 --- a/docs/en/api-reference/peripherals/sdmmc_host.rst +++ b/docs/en/api-reference/peripherals/sdmmc_host.rst @@ -1,6 +1,12 @@ SDMMC Host Driver ================= +.. only:: esp32c3 + + .. warning:: + + This document is not updated for ESP32-C3 yet. + Overview -------- diff --git a/docs/en/index.rst b/docs/en/index.rst index 75f394645f..29fde1d2f9 100644 --- a/docs/en/index.rst +++ b/docs/en/index.rst @@ -18,12 +18,6 @@ This is the documentation for Espressif IoT Development Framework (`esp-idf