1
linux/drivers/usb
David Brownell 93f1a47c4a USB: add ehci_hcd.ignore_oc parameter
Certain boards seem to like to issue false overcurrent notifications, for
example on ports that don't have anything connected to them.  This looks
like a hardware error, at the level of noise to those ports' overcurrent
input signals (or non-debounced VBUS comparators).  This surfaces to users
as truly massive amounts of syslog spam from khubd (which is appropriate
for real hardware problems, except for the volume from multiple ports).

Using this new "ignore_oc" flag helps such systems work more sanely, by
preventing such indications from getting to khubd (and spam syslog).  The
downside is of course that true overcurrent errors will be masked; they'll
appear as spontaneous disconnects, without the diagnostics that will let
users troubleshoot issues like short circuited cables.

Note that the bulk of these reports seem to be with VIA southbridges, but
I think some were with Intel ones.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-12-01 14:23:37 -08:00
..
atm USB: speedtch: Use usb_endpoint_* functions 2006-12-01 14:23:29 -08:00
class USB: cdc-acm: Use usb_endpoint_* functions 2006-12-01 14:23:28 -08:00
core USB core: fix compiler warning about usb_autosuspend_work 2006-12-01 14:23:35 -08:00
gadget USB: net2280: don't send unwanted zero-length packets 2006-12-01 14:23:36 -08:00
host USB: add ehci_hcd.ignore_oc parameter 2006-12-01 14:23:37 -08:00
image usb: microtek possible memleak fix 2006-12-01 14:23:36 -08:00
input usb: usbkbd free urb cleanup 2006-12-01 14:23:33 -08:00
misc usb: phidgetmotorcontrol free urb cleanup 2006-12-01 14:23:34 -08:00
mon usbmon: don't call mon_dmapeek if DMA isn't being used 2006-09-27 11:58:56 -07:00
net usb: catc free urb cleanup 2006-12-01 14:23:34 -08:00
serial USB: fix aircable.c: inconsequent NULL checking 2006-12-01 14:23:35 -08:00
storage USB: add Digitech USB-Storage to unusual_devs.h 2006-12-01 14:23:35 -08:00
Kconfig USB OHCI controller support for PNX4008 2006-09-27 11:58:48 -07:00
Makefile USB: move trancevibrator.c to the proper usb directory 2006-10-17 14:46:32 -07:00
README
usb-skeleton.c IRQ: Maintain regs pointer globally rather than passing to IRQ handlers 2006-10-05 15:10:12 +01: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.