linux/drivers/usb
Felipe Balbi fbabe66636 UPSTREAM: usb: dwc3: gadget: clear DWC3_EP_TRANSFER_STARTED on cmd complete
We must wait until End Transfer completes in order to clear
DWC3_EP_TRANSFER_STARTED, otherwise we may confuse the driver.

This patch is in preparation to fix a rare race condition that happens
upon Disconnect Interrupt.

Change-Id: I2f36f240dc0917715d0eeacde14b22043e19eee7
Tested-by: Thinh Nguyen <thinhn@synopsys.com>
Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
Signed-off-by: William Wu <william.wu@rock-chips.com>
(cherry picked from commit acbfa6c26f)
2019-05-16 19:19:54 +08:00
..
atm BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
c67x00 USB: add SPDX identifiers to all remaining Makefiles 2017-11-07 15:53:48 +01:00
chipidea BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
class BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
common rk: revert to v4.4 2019-02-10 00:33:21 +08:00
core BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
dwc_otg_310 usb: dwc_otg_310: pcd: don't set pullup twice 2018-11-29 20:49:49 +08:00
dwc2 BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
dwc3 UPSTREAM: usb: dwc3: gadget: clear DWC3_EP_TRANSFER_STARTED on cmd complete 2019-05-16 19:19:54 +08:00
early usb: early: Correct the endpoint type value for bulk in endpoint 2017-12-07 16:03:15 +01:00
gadget BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
host BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
image BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
isp1760 BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
misc BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
mon BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
mtu3 BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
musb BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
phy BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
renesas_usbhs rk: revert to v4.4 2019-02-10 00:33:21 +08:00
roles BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
serial BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
storage BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
typec BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
usbip BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
wusbcore BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
Kconfig BACKPORT: USB: add missing SPDX lines to Kconfig and Makefiles 2019-05-16 19:19:54 +08:00
Makefile rk: revert to v4.4 2019-02-10 00:33:21 +08:00
README
usb-skeleton.c usb: usb-skeleton: use irqsave() in USB's complete callback 2018-06-28 19:36:06 +09:00

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.