android_kernel_xiaomi_sm8350/drivers/usb
Oliver Neukum b308e74d9c USB: visor driver adapted to new tty buffering
the new tty buffering code allows usb drivers to stop private buffering.
In fact we must do so to allow flushing to work correctly. This does so
for the visor driver.


Signed-off-by: Oliver Neukum <oneukum@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2007-07-12 16:29:51 -07:00
..
atm USB: cxacru: Cleanup sysfs attribute code 2007-07-12 16:29:45 -07:00
class usblp: Don't let suspend to kill ->used 2007-06-08 16:24:29 -07:00
core USB: rework C++-style comments 2007-07-12 16:29:49 -07:00
gadget USB: export <linux/usb_gadgetfs> as <linux/usb/gadgetfs.h> 2007-07-12 16:29:50 -07:00
host USB: use function attribute __maybe_unused 2007-07-12 16:29:50 -07:00
image header cleaning: don't include smp_lock.h when not used 2007-05-08 11:15:07 -07:00
misc USB: prevent char device open/deregister race 2007-07-12 16:29:48 -07:00
mon usbmon: Add class for binary interface 2007-07-12 16:29:47 -07:00
serial USB: visor driver adapted to new tty buffering 2007-07-12 16:29:51 -07:00
storage USB: add USB-Persist facility 2007-07-12 16:29:47 -07:00
Kconfig USB: Use menuconfig objects 2007-07-12 16:29:46 -07:00
Makefile USB: r8a66597-hcd: host controller driver for R8A66597 2007-07-12 16:29:45 -07:00
README
usb-skeleton.c USB: prevent char device open/deregister race 2007-07-12 16:29:48 -07: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 ("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.