kernel_optimize_test

History

Tony Lindgren f1c9e151b1 USB: omap_udc: sync with OMAP tree Sync up USB parts of the omap_udc support in mainline with the OMAP tree. This patch addresses some OMAP2 differences ... there's another, with respect to the double-buffering issue with PIO-IN in omap_ep_setup() (which is now out of sync with the comments), but it's not clear right now how to address that. From: Tony Lindgren <tony@atomide.com> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>		2008-10-17 14:41:00 -07:00
..
atm
c67x00
class	drivers/usb/class/usblp.c: adjust error handling code	2008-10-17 14:40:51 -07:00
core	USB: change hub initialization sleeps to delayed_work	2008-10-17 14:40:57 -07:00
gadget	USB: omap_udc: sync with OMAP tree	2008-10-17 14:41:00 -07:00
host	USB: ohci-omap: handle other omap15xx chips	2008-10-17 14:40:59 -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	usbmon: fix tiny race exposed by the fastboot patches	2008-10-17 14:40:57 -07:00
musb	usb: musb: remove dead code from procfs	2008-10-17 14:40:59 -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
Makefile
README
usb-skeleton.c

README

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.