kernel_optimize_test

History

Matthias Kaehlcke 831c70fc13 USB: use mutex instead of semaphore in the USB gadget serial driver The USB gadget serial driver uses a semaphore as mutex. Use the mutex API instead of the (binary) semaphore. Signed-off-by: Matthias Kaehlcke <matthias.kaehlcke@gmail.com> Acked-by: David Brownell <david-b@pacbell.net> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>		2007-07-19 17:46:03 -07:00
..
atm	Freezer: make kernel threads nonfreezable by default	2007-07-17 10:23:02 -07:00
class	USB: cdc-acm: add new device id to option driver	2007-07-12 16:34:43 -07:00
core	dev_vdbg(), available with -DVERBOSE_DEBUG	2007-07-18 15:49:50 -07:00
gadget	USB: use mutex instead of semaphore in the USB gadget serial driver	2007-07-19 17:46:03 -07:00
host	some kmalloc/memset ->kzalloc (tree wide)	2007-07-19 10:04:50 -07:00
image
misc	drivers/*: mark variables with uninitialized_var()	2007-07-17 16:23:19 -04:00
mon
serial	USB: io_*: remove bogus termios no change checks	2007-07-12 16:34:41 -07:00
storage	Freezer: make kernel threads nonfreezable by default	2007-07-17 10:23:02 -07:00
Kconfig	no USB on M32R	2007-07-17 11:01:07 -07:00
Makefile	USB: remove Makefile reference to obsolete OHCI_AT91	2007-07-12 16:34:41 -07:00
README
usb-skeleton.c	USB: usb-skeleton: use anchors in pre/post reset	2007-07-12 16:34:37 -07:00

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.