docs(esp_tinyusb): Updated CHANGELOG.md and README.md

Author: roma-jam

device/esp_tinyusb/CHANGELOG.md

@@ -1,6 +1,7 @@
 ## [Unreleased]
 
 - Fixed forward compatibility with TinyUSB 0.19
+- Added VBUS monitoring feature for ESP32P4 USB OTG 2.0 (HS)
 
 ## 2.0.1
 

device/esp_tinyusb/README.md

@@ -226,6 +226,38 @@ For self-powered devices, monitoring the VBUS voltage is required. To do this:
     tinyusb_driver_install(&tusb_cfg);
   }
 ```
+
+> **💡 Note:** **ESP32-P4**, USB OTG 2.0, High-speed doesn't have hardware detection of VBUS BVALID signal
+
+For **ESP32-S2**/**ESP32-S3**, VBUS monitoring (driving the BVALID signal) is handled in hardware.
+
+For **ESP32-P4** (USB OTG 2.0), it is implemented in the driver.
+
+To achieve this, an additional software timer is used in the driver.
+
+To avoid and filter glitches on the VBUS-monitor GPIO, a configurable vbus_debounce_ms parameter is available in the driver configuration.
+
+Default value: 250 ms
+
+If the default value isn’t enough, or if the device does not detach from the USB host port, you can increase the debounce interval:
+
+```c
+  #include "tinyusb_default_config.h"
+  #include "sdkconfig.h"
+
+  void app_main(void)
+  {
+    tinyusb_config_t tusb_cfg = TINYUSB_DEFAULT_CONFIG();
+
+    tusb_cfg.phy.self_powered     = true;
+    tusb_cfg.phy.vbus_monitor_io  = GPIO_NUM_0;
+#if (CONFIG_IDF_TARGET_ESP32P4)
+    tusb_cfg.phy.vbus_monitor_debounce_ms = 350; // new debounce value
+#endif
+    tinyusb_driver_install(&tusb_cfg);
+  }
+```
+
 If external PHY is used:
 
 ```c