kernel_optimize_test

History

Russell King a8d3584a2d [ARM] Remove clk_use()/clk_unuse() It seems that clk_use() and clk_unuse() are additional complexity which isn't required anymore. Remove them from the clock framework to avoid the additional confusion which they cause, and update all ARM machine types except for OMAP. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>		2006-01-03 18:41:37 +00:00
..
atm	[PATCH] Additional device ID for Conexant AccessRunner USB driver	2005-11-29 21:39:22 -08:00
class
core	[PATCH] usbcore: allow suspend/resume even if drivers don't support it	2005-12-21 14:46:35 -08:00
gadget	[PATCH] USB: fix build breakage in dummy_hcd.c	2005-11-17 11:29:52 -08:00
host	[ARM] Remove clk_use()/clk_unuse()	2006-01-03 18:41:37 +00:00
image	[PATCH] USB: Adapt microtek driver to new scsi features	2005-11-17 11:29:54 -08:00
input	[PATCH] Input: wacom - fix X axis setup	2005-12-30 08:20:26 -08:00
media	[PATCH] USB: SN9C10x driver - bad page state fix	2005-11-23 23:04:27 -08:00
misc	[PATCH] auerswald.c: %zd for size_t	2005-12-15 10:04:29 -08:00
mon
net	[PATCH] USB: move CONFIG_USB_DEBUG checks into the Makefile	2005-11-17 11:29:55 -08:00
serial	[PATCH] usb serial: remove redundant include	2005-11-23 23:04:28 -08:00
storage	[PATCH] USB Storage: Force starget->scsi_level in usb-storage scsiglue.c	2005-12-21 14:46:34 -08: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.