Hi, (break your lines at 80-columns) david preetham <preetham.david@xxxxxxxxx> writes: > In DWC3 USB device controller, on which basis event->status & > DEPEVT_STATUS_SHORT is set who will set? I understand if we receive > less bytes we are going to set short packet. > > Suppose gadget driver requested 1MB req length, DWC3 forms TRB size > with gadget(MTP) request length. If host sends less data event status > is set to DEPEVT_STATUS_SHORT. In function __dwc3_cleanup_done_trbs > there is check if (count && (event->status & DEPEVT_STATUS_SHORT)), > before givingback request to gadget driver. Currently in MTP gadget > driver relies on short packet for EOF for large files(more than 4GB it > don’t have file length size information) f_mtp.c (receive_file_work) > reference. > > How device controller will know short packet or end of transfer apart > from checking req length and received length from host is there > anything host informs this is short packet to device controller? > Suppose there 2gb file is getting transfer from host to device. How > host will make sure EOF or short transfer for complete 2gb file. already replied: https://marc.info/?l=linux-usb&m=154721398321898 -- balbi
