diff options
author | Tony Olech <tony.olech@elandigitalsystems.com> | 2006-09-13 12:27:35 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@suse.de> | 2006-09-27 20:58:59 +0200 |
commit | d774efeabccf5f5207aa70d5c126fc928e8b30bd (patch) | |
tree | ed06d0e280feb9f0aa89fbf4ef793dd5d48cebce /drivers/block/cciss_scsi.c | |
parent | USB: ftdi-elan: client driver for ELAN Uxxx adapters (diff) | |
download | linux-d774efeabccf5f5207aa70d5c126fc928e8b30bd.tar.xz linux-d774efeabccf5f5207aa70d5c126fc928e8b30bd.zip |
USB: u132-hcd: host controller driver for ELAN U132 adapter
This "u132-hcd" module is one half of the "driver" for
ELAN's U132 which is a USB to CardBus OHCI controller
adapter. This module needs the "ftdi-elan" module in
order to communicate to CardBus OHCI controller inserted
into the U132 adapter.
When the "ftdi-elan" module detects a supported CardBus
OHCI controller in the U132 adapter it loads this "u132-hcd"
module.
Upon a successful device probe() the single workqueue
is started up which does all the processing of commands
from the USB core that implement the host controller.
The workqueue maintains the urb queues and issues commands
via the functions exported by the "ftdi-elan" module. Each
such command will result in a callback.
Note that the "ftdi-elan" module is a USB client driver.
Note that this "u132-hcd" module is a (cut-down OHCI)
host controller.
Thus we have a topology with the parent of a host controller
being a USB client! This really stresses the USB subsystem
semaphore/mutex handling in the module removal.
Signed-off-by: Tony Olech <tony.olech@elandigitalsystems.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/block/cciss_scsi.c')
0 files changed, 0 insertions, 0 deletions