Merge branch 'docs/update_usb_docs_for_p4' into 'master'

docs(usb): update usb docs related to esp32p4

Closes AEG-2760

See merge request ae_group/esp-iot-solution!1363

Author: YanKE01

docs/_static/usb/esp32p4_usb.png

@@ -3,7 +3,7 @@ USB Device UAC
 
 :link_to_translation:`zh_CN:[中文]`
 
-`esp_device_uac` is a USB Audio Class driver library based on TinyUSB. It supports simulating an ESP chip as an audio device, with customizable audio sampling rates, microphone channels, and speaker channels.
+``esp_device_uac`` is a USB Audio Class driver library based on TinyUSB. It supports simulating an ESP chip as an audio device, with customizable audio sampling rates, microphone channels, and speaker channels.
 
 Features:
 
@@ -16,7 +16,7 @@ USB Device UAC User Guide
 
 - Development Board
 
-    1. Any ESP32-S2/ESP32-S3 development board with a USB interface can be used.
+    1. Any ESP32-S2/ESP32-S3/ESP32-P4 development board with a USB interface can be used.
 
 - USB MIC Callback Function
 

docs/en/usb/usb_device/usb_device_uac.rst

@@ -3,14 +3,12 @@ USB Device UVC
 
 :link_to_translation:`zh_CN:[中文]`
 
-``usb_device_uvc`` is a USB ``UVC`` device driver for ESP32-S2/ESP32-S3, which supports streaming JPEG frames to the USB Host. User can wrapper the Camera or any devices as a UVC standard device through the callback functions.
+``usb_device_uvc`` is a USB ``UVC`` device driver for ESP32-S2/ESP32-S3/ESP32-P4, which supports streaming JPEG frames to the USB Host. User can wrapper the Camera or any devices as a UVC standard device through the callback functions.
 
 Features:
 
 1. Support video stream through the UVC Stream interface
-
 2. Support both ``Isochronous`` and ``Bulk`` mode
-
 3. Support multiple resolutions and frame rates
 
 Add component to your project

docs/en/usb/usb_device/usb_device_uvc.rst

@@ -15,7 +15,7 @@ User Guide
 
 Hardware requirements:
 
-    - Any ESP32-S2/ESP32-S3 development board with a USB interface capable of providing external power.
+    - Any ESP32-S2/ESP32-S3/ESP32-P4 development board with a USB interface capable of providing external power.
     - A USB flash drive using the BOT (Bulk-Only Transport) protocol and Transparent SCSI command set.
 
 Partition Table:

docs/en/usb/usb_host/esp_msc_ota.rst

@@ -76,15 +76,8 @@ USB Stream Config Reference
 4. The host will matches the descriptors of the connected devices according to the user parameters. If the device fails to meet the configuration requirements, the driver prompt warning message
 5. If the device meets user configuration requirements, the Host will continue to receive the IN stream (UVC and UAC mic), and will call the user’s callbacks when new frames ready.
 
-   1. The camera callback will be triggered after a new MJPEG image ready.
-      The callback can block during processing, because which works in
-      an independent task context.
-   2. The mic callback will be triggered after :cpp:func:`mic_min_bytes` bytes
-      data received. But the callback here must not block in any way,
-      otherwise it will affect the reception of the next frame. If the
-      block operations for mic is necessary, you can use the polling
-      mode instead of the callback mode through
-      :cpp:func:`uac_mic_streaming_read` api.
+   1. The camera callback will be triggered after a new MJPEG image ready. The callback can block during processing, because which works in an independent task context.
+   2. The mic callback will be triggered after :cpp:func:`mic_min_bytes` bytes data received. But the callback here must not block in any way, otherwise it will affect the reception of the next frame. If the block operations for mic is necessary, you can use the polling mode instead of the callback mode through :cpp:func:`uac_mic_streaming_read` api.
 
 6. User can send speaker OUT stream using :cpp:func:`uac_spk_streaming_write` through a ringbuffer, the Host will fetch the data when USB is free to send.
 7. Use the :cpp:func:`usb_streaming_control` to control the stream suspend/resume, uac volume/mute control can also be support if the USB device has such feature unit;
@@ -96,8 +89,7 @@ Bug report
 ESP32-S2 ECO0 Chip SPI screen jitter when work with usb camera
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-1. In earlier versions of the ESP32-S2 chip, USB transfers can cause SPI
-   data contamination (esp32s2>=ECO1 and esp32s3 do not have this bug)
+1. In earlier versions of the ESP32-S2 chip, USB transfers can cause SPI data contamination (esp32s2>=ECO1 and esp32s3 do not have this bug)
 2. Software workaround
 
 -  ``spi_ll.h`` add below function

docs/en/usb/usb_host/usb_stream.rst

@@ -18,4 +18,4 @@ USB Host & Device
     USB Device Set Const COM <usb_device_const_COM>
     USB Signal Quality Test <usb_signal_quality>
     TinyUSB Guide <tinyusb_guide>
-    Native TinyUSB Development Guide <tinyusb_development_guide>
+    Native TinyUSB Development Guide <tinyusb_development_guide>

docs/en/usb/usb_overview/index.rst

@@ -1,4 +1,3 @@
-
 Developing with Native tinyusb
 --------------------------------
 
@@ -58,6 +57,12 @@ Most of tinyusb's functionalities are controlled through macros, so we need to d
 
         #define CFG_TUSB_RHPORT0_MODE    (OPT_MODE_DEVICE | OPT_MODE_FULL_SPEED)
 
+- **CFG_TUSB_RHPORT1_MODE**: Defines the connection method and speed to the USB Phy. The following method indicates a USB device with USB high speed.
+
+    .. code:: C
+
+        #define CFG_TUSB_RHPORT1_MODE    (OPT_MODE_DEVICE | OPT_MODE_HIGH_SPEED)
+
 - **ESP_PLATFORM**: This macro needs to be enabled when using the esp-idf platform for compilation.
 
 - **CFG_TUSB_OS**: Defines the operating system for tinyusb. If using FreeRTOS, this macro needs to be enabled. It can also be disabled if not using an OS.
@@ -78,6 +83,12 @@ Most of tinyusb's functionalities are controlled through macros, so we need to d
 
         #define CFG_TUSB_DEBUG         0
 
+- **CFG_TUSB_DEBUG_PRINTF**: Defines the log printing function for tinyusb.
+
+    .. code:: C
+
+        #define CFG_TUSB_DEBUG_PRINTF      esp_rom_printf 
+
 - **CFG_TUD_ENABLED**: Set to 1 to enable tinyusb device functionality.
 
 - **CFG_TUSB_MEM_SECTION**: This macro can be enabled to allocate tinyusb memory to a specific memory section.

docs/en/usb/usb_overview/tinyusb_development_guide.rst

@@ -206,4 +206,3 @@ In UVC devices, a single physical camera has a VC (video control) descriptor, an
             |-- Video Streaming
 
 Refer to :doc:`/usb/usb_device/usb_device_uvc` for more information.
-

docs/en/usb/usb_overview/tinyusb_guide.rst

@@ -83,7 +83,6 @@ Solution
 
 Users have the option to download the script :download:`ignore_hwserial_usb_serial_jtag.bat <../../../_static/ignore_hwserial_usb_serial_jtag.bat>` , then run it with administrative privileges by right-clicking and selecting **Run as Administrator**.
 
-
 .. Note::
 
     The above command is for Windows 10/11. For Windows 7 or other versions, the registry path is different. Please download the script :download:`ignore_hwserial_usb_serial_jtag_win7.bat <../../../_static/ignore_hwserial_usb_serial_jtag_win7.bat>` and run it with Administrative privileges.

docs/en/usb/usb_overview/usb_device_const_COM.rst

@@ -8,7 +8,7 @@ According to the USB protocol requirements, self-powered USB devices must detect
 
 There are generally two methods for USB device VBUS detection: detection by USB PHY hardware, or \ **detection by software with the help of ADC/GPIO**\.
 
-The internal USB PHY of ESP32S2/S3 does not support hardware detection logic, this function needs to be implemented by software with the help of ADC/GPIO. Among them, using the GPIO detection method is the simplest. The implementation is as follows:
+The internal USB PHY of ESP32S2/S3/P4 does not support hardware detection logic, this function needs to be implemented by software with the help of ADC/GPIO. Among them, using the GPIO detection method is the simplest. The implementation is as follows:
 
 **For ESP-IDF 4.4 and earlier versions:**
 
@@ -22,7 +22,7 @@ The internal USB PHY of ESP32S2/S3 does not support hardware detection logic, th
     *
     * @brief For USB Self-power device, the VBUS voltage must be monitored to achieve hot-plug,
     *        The simplest solution is detecting GPIO level as voltage signal.
-    *        A divider resistance Must be used due to ESP32S2/S3 has no 5V tolerate pin.
+    *        A divider resistance Must be used due to ESP32S2/S3/P4 has no 5V tolerate pin.
     *
     *   5V VBUS ┌──────┐    ┌──────┐   GND
     *    ───────┤ 100K ├─┬──┤ 100K ├──────