Lines Matching full:transfer

119 .Sh USB TRANSFER MANAGEMENT FUNCTIONS
125 All the transfer types are managed using the following five functions:
141 is a pointer to an array of USB transfer pointers that are initialized
152 is the private mutex protecting the transfer structure and the
164 is a pointer to an array of USB transfer pointers, that may be NULL,
172 This function is NULL safe with regard to the USB transfer structure
175 It is not allowed to call this function from the USB transfer
181 This function will start the USB transfer pointed to by
188 This function is NULL safe with regard to the USB transfer structure
194 This function will stop the USB transfer pointed to by
203 This function is NULL safe with regard to the USB transfer structure
206 If the transfer was in progress, the callback will called with
212 This function will stop an USB transfer, if not already stopped and
221 This function is NULL safe with regard to the USB transfer structure
224 .Sh USB TRANSFER CALLBACK
234 The USB callback should not restart the USB transfer in case the error
239 That means one can start and stop whatever transfer from the callback
240 of another transfer one desires.
242 Also the transfer that is currently called back.
254 An USB transfer can have multiple frames consisting of one or more USB
255 packets making up an I/O vector for all USB transfer types.
297 An USB control transfer has three parts.
307 If an USB control transfer has no DATA stage,
352 .Sh USB TRANSFER CONFIG
405 Note that "UE_DIR_IN" refers to the data transfer direction of the
406 "IN" tokens and "UE_DIR_OUT" refers to the data transfer direction of
428 "0" no transfer pre-delay.
433 NOTE: The transfer timeout, if any, is started after that the
439 field, if non-zero, will set the transfer timeout in milliseconds.
440 If the "timeout" field is zero and the transfer type is ISOCHRONOUS a
468 be used when setting up the given USB transfer.
473 flags an USB transfer.
482 This flag allows the received transfer length, "xfer->actlen" to be
483 less than "xfer->sumlen" upon completion of a transfer.
492 This flag causes a failing USB transfer to remain first in the PIPE
499 The failing USB transfer is stopped using "usbd_transfer_stop()".
501 The failing USB transfer performs a successful transfer.
505 transfer fails leading to the need for clearing of stall for
522 rounded up to the nearest atomic hardware transfer size.
524 The maximum data length of any USB transfer is always stored in the
547 end of the USB control transfer.
567 belonging to this transfer before the transfer is started.
569 The transfer is started at the moment the host issues a clear-stall
575 executed on the endpoint before the USB transfer is started.
585 During transfer setup the frames field is pre scaled with the corresponding value for the endpoint …
593 the "frames" field if the transfer type is ISOCHRONOUS.