kernel_optimize_test/drivers/usb
Greg Kroah-Hartman 9908a32e94 USB: remove err() macro from usb class drivers
USB should not be having it's own printk macros, so remove err() and
use the system-wide standard of dev_err() wherever possible.  In the
few places that will not work out, use a basic printk().

Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-10-17 14:41:10 -07:00
..
atm USB: remove warn() macro from usb drivers 2008-10-17 14:41:09 -07:00
c67x00 usb/c67x00 endianness annotations 2008-06-04 08:06:01 -07:00
class USB: remove err() macro from usb class drivers 2008-10-17 14:41:10 -07:00
core USB: remove warn() macro from usb drivers 2008-10-17 14:41:09 -07:00
gadget usb/fsl_qe_udc: clear data toggle on clear halt request 2008-10-17 14:41:08 -07:00
host USB: remove info() macro from remaining usb drivers 2008-10-17 14:41:09 -07:00
image USB: remove info() macro from remaining usb drivers 2008-10-17 14:41:09 -07:00
misc USB: remove info() macro from usb/misc drivers 2008-10-17 14:41:09 -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: remove use of err() in drivers/usb/serial 2008-10-17 14:41:10 -07:00
storage usb-storage: report underflow with no sense data 2008-10-17 14:40:54 -07:00
Kconfig USB: Add MUSB and TUSB support 2008-08-13 17:33:00 -07:00
Makefile USB: add Cypress c67x00 OTG controller HCD driver 2008-05-02 10:25:57 -07:00
README
usb-skeleton.c

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.