1
linux/drivers/usb
Mike Isely 78aef519ed cypress_m8: implement graceful failure handling
When receiving a fatal error from the USB core, e.g. EILSEQ (which can
happen if the polling interval is too short), fail gracefully.
Previously the driver would fill the log with useless error messages
or (more alarmingly) silently spin forever trying to write updated
control information to the device.  This change implements a new flag
which if cleared indicates that the driver has failed.  The flag will
be set on initialization, cleared on fatal errors, and anything else
that touches the USB port in the driver will abort if the flag is
clear.  When the flag is cleared, a message will be logged indicating
that the driver has failed.

Signed-off-by: Mike Isely <isely@pobox.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-09-27 11:58:59 -07:00
..
atm USB: fix __must_check warnings in drivers/usb/atm/ 2006-09-27 11:58:58 -07:00
class USB: fix __must_check warnings in drivers/usb/class/ 2006-09-27 11:58:58 -07:00
core USB: fix __must_check warnings in drivers/usb/core/ 2006-09-27 11:58:57 -07:00
gadget USB: net2280: update dma buffer allocation 2006-09-27 11:58:57 -07:00
host USB: fix __must_check warnings in drivers/usb/host/ 2006-09-27 11:58:58 -07:00
image USB: Make file operations structs in drivers/usb const. 2006-09-27 11:58:52 -07:00
input USB: fix __must_check warnings in drivers/usb/input/ 2006-09-27 11:58:58 -07:00
misc USB: fix __must_check warnings in drivers/usb/misc/ 2006-09-27 11:58:58 -07:00
mon usbmon: don't call mon_dmapeek if DMA isn't being used 2006-09-27 11:58:56 -07:00
net USB: net1080 inherent pad length 2006-09-27 11:58:54 -07:00
serial cypress_m8: implement graceful failure handling 2006-09-27 11:58:59 -07:00
storage USB: replace kernel_thread() with kthread_run() in libusual.c 2006-09-27 11:58:56 -07:00
Kconfig USB OHCI controller support for PNX4008 2006-09-27 11:58:48 -07:00
Makefile [PATCH] USB: rename Cypress CY7C63xxx driver to proper name and fix up some tiny things 2006-07-12 16:03:21 -07:00
README Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00
usb-skeleton.c usbcore: non-hub-specific uses of autosuspend 2006-09-27 11:58:57 -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.