#
# [31mCONFIG_USB[0m Miscellaneous driver configuration
#
comment "USB Miscellaneous drivers"
config [31mCONFIG_USB_EMI62[0m
tristate "EMI 6|2m USB Audio interface support"
---help---
This driver loads firmware to Emagic EMI 6|2m low latency [31mCONFIG_USB[0m
Audio and Midi interface.
After firmware load the device is handled with standard linux
[31mCONFIG_USB[0m Audio driver.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called audio. If you want to compile it as a
module, say [31mCONFIG_M[0m here and read <file:Documentation/kbuild/modules.txt>.
config [31mCONFIG_USB_EMI26[0m
tristate "EMI 2|6 USB Audio interface support"
---help---
This driver loads firmware to Emagic EMI 2|6 low latency [31mCONFIG_USB[0m
Audio interface.
After firmware load the device is handled with standard linux
[31mCONFIG_USB[0m Audio driver.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called emi26.
config [31mCONFIG_USB_ADUTUX[0m
tristate "ADU devices from Ontrak Control Systems"
help
Say Y if you want to use an ADU device from Ontrak Control
Systems.
To compile this driver as a module, choose [31mCONFIG_M[0m here. The module
will be called adutux.
config [31mCONFIG_USB_SEVSEG[0m
tristate "USB 7-Segment LED Display"
help
Say Y here if you have a [31mCONFIG_USB[0m 7-Segment Display by Delcom
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called usbsevseg.
config [31mCONFIG_USB_RIO500[0m
tristate "USB Diamond Rio500 support"
help
Say Y here if you want to connect a [31mCONFIG_USB[0m Rio500 mp3 player to your
computer's [31mCONFIG_USB[0m port. Please read <file:Documentation/usb/rio.txt>
for more information.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called rio500.
config [31mCONFIG_USB_LEGOTOWER[0m
tristate "USB Lego Infrared Tower support"
help
Say Y here if you want to connect a [31mCONFIG_USB[0m Lego Infrared Tower to your
computer's [31mCONFIG_USB[0m port.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called legousbtower. If you want to compile it as
a module, say [31mCONFIG_M[0m here and read
<file:Documentation/kbuild/modules.txt>.
config [31mCONFIG_USB_LCD[0m
tristate "USB LCD driver support"
help
Say Y here if you want to connect an USBLCD to your computer's
[31mCONFIG_USB[0m port. The USBLCD is a small [31mCONFIG_USB[0m interface board for
alphanumeric LCD modules. See <http://www.usblcd.de/> for more
information.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called usblcd.
config [31mCONFIG_USB_CYPRESS_CY7C63[0m
tristate "Cypress CY7C63xxx USB driver support"
help
Say Y here if you want to connect a Cypress CY7C63xxx
micro controller to your computer's [31mCONFIG_USB[0m port. Currently this
driver supports the pre-programmed devices (incl. firmware)
by AK Modul-Bus Computer GmbH.
Please see: http://www.ak-modul-bus.de/stat/mikrocontroller.html
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called cypress_cy7c63.
config [31mCONFIG_USB_CYTHERM[0m
tristate "Cypress USB thermometer driver support"
help
Say Y here if you want to connect a Cypress [31mCONFIG_USB[0m thermometer
device to your computer's [31mCONFIG_USB[0m port. This device is also known
as the Cypress [31mCONFIG_USB[0m Starter kit or demo board. The Elektor
magazine published a modified version of this device in issue
#291.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called cytherm.
config [31mCONFIG_USB_IDMOUSE[0m
tristate "Siemens ID USB Mouse Fingerprint sensor support"
help
Say Y here if you want to use the fingerprint sensor on
the Siemens ID Mouse. There is also a Siemens ID Mouse
_Professional_, which has not been tested with this driver,
but uses the same sensor and may therefore work.
This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX",
which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm".
See also <http://www.fs.tum.de/~echtler/idmouse/>.
config [31mCONFIG_USB_FTDI_ELAN[0m
tristate "Elan PCMCIA CardBus Adapter USB Client"
help
ELAN's Uxxx series of adapters are [31mCONFIG_USB[0m to [31mCONFIG_PCMCIA[0m CardBus adapters.
Currently only the U132 adapter is available.
The U132 is specifically designed for CardBus PC cards that contain
an OHCI host controller. Typical PC cards are the Orange Mobile 3G
Option GlobeTrotter Fusion card. The U132 adapter will *NOT* work
with PC cards that do not contain an OHCI controller. To use a U132
adapter you will need this "ftdi-elan" module as well as the "u132-hcd"
module which is a [31mCONFIG_USB[0m host controller driver that talks to the OHCI
controller within CardBus card that are inserted in the U132 adapter.
This driver has been tested with a CardBus OHCI [31mCONFIG_USB[0m adapter, and
worked with a [31mCONFIG_USB[0m PEN Drive inserted into the first [31mCONFIG_USB[0m port of
the [31mCONFIG_PCCARD[0m. [31mCONFIG_A[0m rather pointless thing to do, but useful for testing.
See also the [31mCONFIG_USB_U132_HCD[0m entry "Elan U132 Adapter Host Controller"
It is safe to say [31mCONFIG_M[0m here.
config [31mCONFIG_USB_APPLEDISPLAY[0m
tristate "Apple Cinema Display support"
select [31mCONFIG_BACKLIGHT_LCD_SUPPORT[0m
select [31mCONFIG_BACKLIGHT_CLASS_DEVICE[0m
help
Say Y here if you want to control the backlight of Apple Cinema
Displays over [31mCONFIG_USB[0m. This driver provides a sysfs interface.
source "drivers/usb/misc/sisusbvga/Kconfig"
config [31mCONFIG_USB_LD[0m
tristate "USB LD driver"
help
This driver is for generic [31mCONFIG_USB[0m devices that use interrupt transfers,
like LD Didactic's [31mCONFIG_USB[0m devices.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ldusb.
config [31mCONFIG_USB_TRANCEVIBRATOR[0m
tristate "PlayStation 2 Trance Vibrator driver support"
help
Say Y here if you want to connect a PlayStation 2 Trance Vibrator
device to your computer's [31mCONFIG_USB[0m port.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called trancevibrator.
config [31mCONFIG_USB_IOWARRIOR[0m
tristate "IO Warrior driver support"
help
Say Y here if you want to support the IO Warrior devices from Code
Mercenaries. This includes support for the following devices:
IO Warrior 40
IO Warrior 24
IO Warrior 56
IO Warrior 24 Power Vampire
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called iowarrior.
config [31mCONFIG_USB_TEST[0m
tristate "USB testing driver"
help
This driver is for testing host controller software. It is used
with specialized device firmware for regression and stress testing,
to help prevent problems from cropping up with "real" drivers.
See <http://www.linux-usb.org/usbtest/> for more information,
including sample test device firmware and "how to use it".
config [31mCONFIG_USB_EHSET_TEST_FIXTURE[0m
tristate "USB EHSET Test Fixture driver"
help
Say Y here if you want to support the special test fixture device
used for the [31mCONFIG_USB[0m-IF Embedded Host High-Speed Electrical Test procedure.
When the test fixture is connected, it can enumerate as one of several
VID/PID pairs. This driver then initiates a corresponding test mode on
the downstream port to which the test fixture is attached.
See <http://www.usb.org/developers/onthego/EHSET_v1.01.pdf> for more
information.
config [31mCONFIG_USB_ISIGHTFW[0m
tristate "iSight firmware loading support"
select [31mCONFIG_FW_LOADER[0m
help
This driver loads firmware for [31mCONFIG_USB[0m Apple iSight cameras, allowing
them to be driven by the [31mCONFIG_USB[0m video class driver available at
http://linux-uvc.berlios.de
The firmware for this driver must be extracted from the MacOS
driver beforehand. Tools for doing so are available at
http://bersace03.free.fr
config [31mCONFIG_USB_YUREX[0m
tristate "USB YUREX driver support"
help
Say Y here if you want to connect a YUREX to your computer's
[31mCONFIG_USB[0m port. The YUREX is a leg-shakes sensor. See
<http://bbu.kayac.com/en/> for further information.
This driver supports read/write of leg-shakes counter and
fasync for the counter update via a device file /dev/yurex*.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called yurex.
config [31mCONFIG_USB_EZUSB_FX2[0m
tristate "Functions for loading firmware on EZUSB chips"
help
Say Y here if you need EZUSB device support.
(Cypress FX/FX2/FX2LP microcontrollers)
config [31mCONFIG_USB_HSIC_USB3503[0m
tristate "USB3503 HSIC to USB20 Driver"
depends on [31mCONFIG_I2C[0m
select [31mCONFIG_REGMAP_I2C[0m
help
This option enables support for SMSC USB3503 HSIC to [31mCONFIG_USB[0m 2.0 Driver.
config [31mCONFIG_USB_HSIC_USB4604[0m
tristate "USB4604 HSIC to USB20 Driver"
depends on [31mCONFIG_I2C[0m
help
This option enables support for SMSC USB4604 HSIC to [31mCONFIG_USB[0m 2.0 Driver.
config [31mCONFIG_USB_LINK_LAYER_TEST[0m
tristate "USB Link Layer Test driver"
help
This driver is for generating specific traffic for Super Speed Link
Layer Test Device. Say Y only when you want to conduct [31mCONFIG_USB[0m Super Speed
Link Layer Test for host controllers.
config [31mCONFIG_USB_CHAOSKEY[0m
tristate "ChaosKey random number generator driver support"
depends on [31mCONFIG_HW_RANDOM[0m
help
Say Y here if you want to connect an AltusMetrum ChaosKey or
Araneus Alea I to your computer's [31mCONFIG_USB[0m port. These devices
are hardware random number generators which hook into the
kernel entropy pool to ensure a large supply of entropy for
/dev/random and /dev/urandom and also provides direct access
via /dev/chaoskeyX
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called chaoskey.
config [31mCONFIG_UCSI[0m
tristate "USB Type-C Connector System Software Interface driver"
depends on [31mCONFIG_ACPI[0m
help
[31mCONFIG_UCSI[0m driver is meant to be used as a convenience tool for desktop and
server systems that are not equipped to handle [31mCONFIG_USB[0m in device mode. It
will always select [31mCONFIG_USB[0m host role for the [31mCONFIG_USB[0m Type-[31mCONFIG_C[0m ports on systems
that provide [31mCONFIG_UCSI[0m interface.
[31mCONFIG_USB[0m Type-[31mCONFIG_C[0m Connector System Software Interface ([31mCONFIG_UCSI[0m) is a
specification for an interface that allows the Operating System to
control the [31mCONFIG_USB[0m Type-[31mCONFIG_C[0m ports on a system. Things the need controlling
include the [31mCONFIG_USB[0m Data Role (host or device), and when [31mCONFIG_USB[0m Power
Delivery is supported, the Power Role (source or sink). With [31mCONFIG_USB[0m
Type-[31mCONFIG_C[0m connectors, when two dual role capable devices are attached
together, the data role is selected randomly. Therefore it is
important to give the OS a way to select the role. Otherwise the user
would have to unplug and replug in order in order to attempt to swap
the data and power roles.
The [31mCONFIG_UCSI[0m specification can be downloaded from:
http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb-type-c-ucsi-spec.html
To compile the driver as a module, choose [31mCONFIG_M[0m here: the module will be
called ucsi.