1
linux/drivers/usb
Pete Zaitcev bdc4abdd09 USB: usblp: Use correct DMA address in case of probe error
Looks like the error path had a copy-paste error. The normal exit path
uses correct URB already.

Signed-off-by: Pete Zaitcev <zaitcev@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2007-05-22 23:45:50 -07:00
..
atm usbatm_heavy_init: don't use CLONE_SIGHAND 2007-05-09 12:30:53 -07:00
class USB: usblp: Use correct DMA address in case of probe error 2007-05-22 23:45:50 -07:00
core USB: don't try to kzalloc 0 bytes 2007-05-22 23:45:50 -07:00
gadget USB: fsl_usb2_udc: Fix UMTI_WIDE support and a compile warning 2007-05-22 23:45:49 -07:00
host EHCI: fix problem with BIOS handoff 2007-05-22 23:45:48 -07:00
image header cleaning: don't include smp_lock.h when not used 2007-05-08 11:15:07 -07:00
misc USB: auerswald: fix file release handler 2007-05-22 23:45:49 -07:00
mon header cleaning: don't include smp_lock.h when not used 2007-05-08 11:15:07 -07:00
serial USB: Fix debug output of ark3116 2007-05-22 23:45:50 -07:00
storage USB: Onetouch - switch to using input_dev->dev.parent 2007-05-22 23:45:50 -07:00
Kconfig [S390] Kconfig: menus with depends on HAS_IOMEM. 2007-05-10 15:46:07 +02:00
Makefile Move USB network drivers to drivers/net/usb. 2007-05-09 21:31:55 -04:00
README
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.