mirror of
https://github.com/torvalds/linux.git
synced 2026-06-10 07:32:29 +02:00
6b406ee4c7
The handle_xfercomp_isoc_split_in() use two conditions to check if the isoc in csplit transcation is done: - the actual xfer length of the current frame is zero - the total xfer length of the frames equals to the request length of the frames But in some case, we find that the two conditions are not enough, e.g. on rockchip platforms, connect the usb audio card with the FE1.1 HUB, the audio is setted to 44100 2ch 16 bits, the csplit transcation sequence is: - CSPLIT IN transcation - MDATA packet [176 bytes] - CSPLIT IN transcation - DATA0 packet [No data] In this case, the total actual xfer length of frames is less than the request length of frames, so the current code will not update the status of frame and the qtd isoc_frame_index, this cause usb audio data corrupted. According to the USB 2.0 spec "Figure 11-85. Isochronous IN Complete-split Transaction Sequence", we can use DATA0 to check if the transaction is last data. So use DATA0 instead of zero length transaction to check if the csplit transcation is done. Change-Id: I55cfa3f7b93ed6bfba3ecec5820d7b534c05ba34 Signed-off-by: William Wu <william.wu@rock-chips.com> |
||
|---|---|---|
| .. | ||
| atm | ||
| c67x00 | ||
| chipidea | ||
| class | ||
| common | ||
| core | ||
| dwc_otg_310 | ||
| dwc2 | ||
| dwc3 | ||
| early | ||
| gadget | ||
| host | ||
| image | ||
| isp1760 | ||
| misc | ||
| mon | ||
| musb | ||
| phy | ||
| renesas_usbhs | ||
| serial | ||
| storage | ||
| usbip | ||
| wusbcore | ||
| Kconfig | ||
| Makefile | ||
| README | ||
| usb-skeleton.c | ||
To understand all the Linux-USB framework, you'll use these resources:
* This source code. This is necessarily an evolving work, and
includes kerneldoc that should help you get a current overview.
("make pdfdocs", and then look at "usb.pdf" for host side and
"gadget.pdf" for peripheral side.) Also, Documentation/usb has
more information.
* The USB 2.0 specification (from www.usb.org), with supplements
such as those for USB OTG and the various device classes.
The USB specification has a good overview chapter, and USB
peripherals conform to the widely known "Chapter 9".
* Chip specifications for USB controllers. Examples include
host controllers (on PCs, servers, and more); peripheral
controllers (in devices with Linux firmware, like printers or
cell phones); and hard-wired peripherals like Ethernet adapters.
* Specifications for other protocols implemented by USB peripheral
functions. Some are vendor-specific; others are vendor-neutral
but just standardized outside of the www.usb.org team.
Here is a list of what each subdirectory here is, and what is contained in
them.
core/ - This is for the core USB host code, including the
usbfs files and the hub class driver ("hub_wq").
host/ - This is for USB host controller drivers. This
includes UHCI, OHCI, EHCI, and others that might
be used with more specialized "embedded" systems.
gadget/ - This is for USB peripheral controller drivers and
the various gadget drivers which talk to them.
Individual USB driver directories. A new driver should be added to the
first subdirectory in the list below that it fits into.
image/ - This is for still image drivers, like scanners or
digital cameras.
../input/ - This is for any driver that uses the input subsystem,
like keyboard, mice, touchscreens, tablets, etc.
../media/ - This is for multimedia drivers, like video cameras,
radios, and any other drivers that talk to the v4l
subsystem.
../net/ - This is for network drivers.
serial/ - This is for USB to serial drivers.
storage/ - This is for USB mass-storage drivers.
class/ - This is for all USB device drivers that do not fit
into any of the above categories, and work for a range
of USB Class specified devices.
misc/ - This is for all USB device drivers that do not fit
into any of the above categories.