diff options
| author | claude[bot] <209825114+claude[bot]@users.noreply.github.com> | 2026-06-02 16:59:14 +0000 |
|---|---|---|
| committer | GitHub <[email protected]> | 2026-06-02 16:59:14 +0000 |
| commit | f19c01216fc5fc0f07789932df1db6fde82f525b (patch) | |
| tree | 146458c0794f71ab4631505befc0b25bce36c2fb /docs | |
| parent | ff3fef931dd2be604fd525814654d1cfcd7c725c (diff) | |
docs: revert USBFS non-ISO transfer qualification in device_issues
Restore original "Other types of transfers are not affected" statement,
removing the conditional USBHS_INT_BUSY_EN / USBFS-unconfirmed wording.
Co-authored-by: Zixun LI <[email protected]>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/reference/device_issues.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/reference/device_issues.rst b/docs/reference/device_issues.rst index 6dafe4de2..ae9cd55f1 100644 --- a/docs/reference/device_issues.rst +++ b/docs/reference/device_issues.rst @@ -32,4 +32,4 @@ Reference: `CH32V30X Reference Manual`_ USBFS/USBHS controller chapter Data corruption may occur on isochronous endpoints. Due to the lacking of FIFO for interrupt status registers, later completed transfer will overwrite `INT_ST` and `RX_LEN` register if previous transfer processing is not completed. -For USBHS devices (CH32F20x, CH32V305/CH32V307), other transfer types are protected by the ``USBHS_INT_BUSY_EN`` mechanism which holds off new transfers while an interrupt is being processed. USBFS device behavior is not fully confirmed. +Other types of transfers are not affected. |