android_kernel_xiaomi_sm8350/drivers/usb
Kevin Lloyd 7384a922b5 USB Serial: Sierra: debug message fix
This patch moves dbg calls to dev_dbg where possible. It also fixes some
issues with a previous submission aiming to do the same thing.

Signed-off-by: Kevin Lloyd <klloyd@sierrawireless.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-10-17 14:40:56 -07:00
..
atm usbatm: Use skb_queue_walk_safe() instead of by-hand implementation. 2008-09-23 00:27:47 -07:00
c67x00
class drivers/usb/class/usblp.c: adjust error handling code 2008-10-17 14:40:51 -07:00
core USB: RESET_RESUME needs to block autosuspend when remote wakeup is needed 2008-10-17 14:40:55 -07:00
gadget usb: add Freescale QE/CPM USB peripheral controller driver 2008-10-17 14:40:54 -07:00
host OHCI: Allow broken controllers to auto-stop 2008-10-17 14:40:54 -07:00
image
misc USB: drivers/usb/misc: Use an IS_ERR test rather than a NULL test 2008-10-17 14:40:53 -07:00
mon device create: usb: convert device_create_drvdata to device_create 2008-10-16 09:24:45 -07:00
musb USB: drivers/usb/musb/: disable it on SuperH 2008-09-23 13:58:09 -07:00
serial USB Serial: Sierra: debug message fix 2008-10-17 14:40:56 -07:00
storage usb-storage: report underflow with no sense data 2008-10-17 14:40:54 -07:00
Kconfig USB: Add MUSB and TUSB support 2008-08-13 17:33:00 -07:00
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 ("khubd").

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.