Stephen Warren 2456b97f0c ush: ehci: initialize altnext pointers in QH ... Section 4.10.2 "Advance Queue" of ehci-specification-for-usb.pdf specifies how an EHCI controller loads a new QTD for processing if the QH is not already marked as active. It states: ===== If the field Bytes to Transfer is not zero and the T-bit in the Alternate Next qTD Pointer is set to zero, then the host controller uses the Alternate Next qTD Pointer. Otherwise, the host controller uses the Next qTD Pointer. If Next qTD Pointer’s T-bit is set to a one, then the host controller exits this state and uses the horizontal pointer to the next schedule data structure. ===== Hence, we must ensure that the alternate next QTD pointer's T-bit (TERMINATE) is set, so the EHCI controller knows to use the next QTD pointer. Signed-off-by: Stephen Warren <swarren@nvidia.com>		2014-03-10 18:53:36 +01:00
..
eth	net: asix: don't pad odd-length TX packets	2014-03-07 10:59:06 -05:00
gadget	sizes.h - consolidate for all architectures	2014-03-04 12:15:01 -05:00
host	ush: ehci: initialize altnext pointers in QH	2014-03-10 18:53:36 +01:00
musb	blackfin: Add <asm/clock.h> to numerous drivers	2014-02-20 12:00:27 -05:00
musb-new	kbuild: use Linux Kernel build scripts	2014-02-19 11:07:50 -05:00
phy	drivers: usb: convert makefiles to Kbuild style	2013-10-31 13:25:38 -04:00
ulpi	drivers: usb: convert makefiles to Kbuild style	2013-10-31 13:25:38 -04:00