Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-05-28 11:56:10 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

STM32 USB OTGFSDEV: Update comments

Browse Source
This commit is contained in:
Petteri Aimonen
2021-03-24 14:57:42 +02:00
committed by David Sidrane
parent 18bfef1b38
commit 3dfc4e0afd
1 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
arch/arm/src/stm32/stm32_otgfsdev.c
+9 -3
View File
@@ -481,15 +481,21 @@ struct stm32_usbdev_s
* ep0data * ep0data
* For OUT SETUP requests, the SETUP data phase must also complete before * For OUT SETUP requests, the SETUP data phase must also complete before
* the SETUP command can be processed. The pack receipt logic will save * the SETUP command can be processed. The pack receipt logic will save
* the accompanying EP0 IN data in ep0data[] before the SETUP command is * the accompanying EP0 OUT data in ep0data[] before the SETUP command is
* processed. * processed. The data length is specified in the SETUP packet payload,
* and can consist of multiple DATA packets.
* *
* For IN SETUP requests, the DATA phase will occur AFTER the SETUP * For IN SETUP requests, the DATA phase will occur AFTER the SETUP
* control request is processed. In that case, ep0data[] may be used as * control request is processed. In that case, ep0data[] may be used as
* the response buffer. * the response buffer.
* *
* ep0datlen * ep0datlen
* Length of OUT DATA received in ep0data[] (Not used with OUT data) * Length of data received part of OUT SETUP request. During transfer
* it is the total number of bytes received, which can be more than
* CONFIG_USBDEV_SETUP_MAXDATASIZE. The value is clamped to valid length
* of data in ep0data[] before SETUP OUT handler is called. Bytes that
* exceed the maximum length are discarded, but must be read out of the
* USB peripheral FIFO.
*/ */
struct usb_ctrlreq_s ctrlreq; struct usb_ctrlreq_s ctrlreq;