android_kernel_motorola_sm6225/drivers/usb
Oliver Neukum 4edf2c8363 USB: fix ark3116 memory leak
this driver has a memory leak in an error case.

Signed-off-by: Oliver Neukum <oneukum@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2007-04-27 13:28:38 -07:00
..
atm USB: cxacru: export detailed device info through sysfs 2007-04-27 13:28:34 -07:00
class USB: cdc-acm: export parsed capabilities through sysfs 2007-04-27 13:28:33 -07:00
core USB: make usbdevices export their device nodes instead of using a separate class 2007-04-27 13:28:37 -07:00
gadget USB: gadget-storage needs BLOCK 2007-04-27 13:28:37 -07:00
host UHCI: Add some WARN_ON()s 2007-04-27 13:28:36 -07:00
image [PATCH] remove many unneeded #includes of sched.h 2007-02-14 08:09:54 -08:00
input USB: ati_remote2: Add channel support 2007-04-27 13:28:37 -07:00
misc USB: iowarrior.c: fix NULL dereference 2007-04-27 13:28:36 -07:00
mon usbmon: Extended text API 2007-04-27 13:28:33 -07:00
net USB: dm9601: fix sparse NULL warnings 2007-04-27 13:28:36 -07:00
serial USB: fix ark3116 memory leak 2007-04-27 13:28:38 -07:00
storage libusual: change block scope variable to function scope 2007-04-27 13:28:34 -07:00
Kconfig [ARM] 3963/1: AT91: Update configuration files 2006-12-01 16:56:43 +00:00
Makefile USB: Driver to charge USB blackberry devices 2007-02-16 15:32:17 -08:00
README Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00
usb-skeleton.c USB: kill BKL in skeleton driver 2007-04-27 13:28:33 -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.