linux/drivers/usb
William Wu 138fd489e3 usb: dwc3: core: add async probe for rockchip dwc3
The default autosuspend delay of PM runtime is 5000ms,
it's too long. For Rockchip DWC3 controller, if it supports
PM runtime management, e.g. RK3568 OTG port, then we expect
to put the DWC3 controller in runtime suspend at the end of
probe as soon as possible. This can fix the issue that race
condition between power down the DWC3 in runtime suspend and
access the DWC3 in dwc3_gadget_pullup() by userspace.

This patch uses pm_runtime_put_sync_suspend() instead of
pm_runtime_put if enable PM runtime. And according to the
commit f2a2b34e45 ("usb: dwc3: rockchip: use async_schedule
for initial dwc3"), we do pm_runtime_put_sync_suspend() in
async schedule to avoid increasing the boot time.

Change-Id: I378e57d272382d444f1ac52ea2961736e472e713
Signed-off-by: William Wu <william.wu@rock-chips.com>
2020-12-24 17:31:35 +08:00
..
atm
c67x00
chipidea Merge tag 'ASB-2020-09-05_4.19-stable' of https://android.googlesource.com/kernel/common 2020-09-24 17:59:50 +08:00
class Merge tag 'ASB-2020-11-05_4.19-stable' of https://android.googlesource.com/kernel/common 2020-11-03 18:36:42 +08:00
common
core Merge tag 'ASB-2020-11-05_4.19-stable' of https://android.googlesource.com/kernel/common 2020-11-03 18:36:42 +08:00
dwc2 Merge tag 'ASB-2020-11-05_4.19-stable' of https://android.googlesource.com/kernel/common 2020-11-03 18:36:42 +08:00
dwc3 usb: dwc3: core: add async probe for rockchip dwc3 2020-12-24 17:31:35 +08:00
early
gadget usb: gadget: add transfer_type in struct usb_ep for rockchip 2020-12-22 18:44:44 +08:00
host ohci-platform: add the max clock number to 4 2020-11-11 21:58:10 +08:00
image
isp1760
misc Merge tag 'ASB-2020-09-05_4.19-stable' of https://android.googlesource.com/kernel/common 2020-09-24 17:59:50 +08:00
mon
mtu3 Merge tag 'ASB-2020-09-05_4.19-stable' of https://android.googlesource.com/kernel/common 2020-09-24 17:59:50 +08:00
musb Merge tag 'ASB-2020-09-05_4.19-stable' of https://android.googlesource.com/kernel/common 2020-09-24 17:59:50 +08:00
phy
renesas_usbhs
roles
serial Merge tag 'ASB-2020-11-05_4.19-stable' of https://android.googlesource.com/kernel/common 2020-11-03 18:36:42 +08:00
storage Merge tag 'ASB-2020-10-05_4.19-stable' of https://android.googlesource.com/kernel/common 2020-10-10 18:38:14 +08:00
typec Merge tag 'ASB-2020-10-05_4.19-stable' of https://android.googlesource.com/kernel/common 2020-10-10 18:38:14 +08:00
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.