kernel-fxtec-pro1x/drivers/usb
Thomas Sailer 0f36163d3a [PATCH] usb: fix uss720 schedule with interrupts off
This patch fixes the long standing schedule with interrupts off problem
of the uss720 driver. The problem is caused by the parport layer calling
the save and restore methods within a write_lock_irqsave guarded region.
The fix is to issue the control transaction requests required by save
and restore asynchronously.

Signed-off-by: Thomas Sailer, <sailer@ife.ee.ethz.ch>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2005-09-12 12:23:53 -07:00
..
atm
class [PATCH] drivers/usb: fix-up schedule_timeout() usage 2005-09-12 12:23:44 -07:00
core [PATCH] USB: relax usbcore reset timings 2005-09-12 12:23:49 -07:00
gadget [PATCH] USB gadgetfs: fixes an error on writing to endpoint file 2005-09-12 12:23:45 -07:00
host [PATCH] USB: OHCI, pxa27x OHCI port power tweaks 2005-09-12 12:23:46 -07:00
image
input [PATCH] USB: add apple usb touchpad driver 2005-09-12 12:23:39 -07:00
media [PATCH] vfree and kfree cleanup in drivers/ 2005-09-10 10:06:30 -07:00
misc [PATCH] usb: fix uss720 schedule with interrupts off 2005-09-12 12:23:53 -07:00
mon
net
serial [PATCH] USB: PL2303: CA-42 Phone cable 2005-09-12 12:23:47 -07:00
storage [PATCH] USB: usb-storage: Add unusual_devs entry for Neuros Audio MP3 player 2005-09-12 12:23:51 -07:00
Kconfig
Makefile
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.