diff options
Diffstat (limited to 'drivers/input')
| -rw-r--r-- | drivers/input/Kconfig | 159 | ||||
| -rw-r--r-- | drivers/input/gameport/Kconfig | 84 | ||||
| -rw-r--r-- | drivers/input/joystick/Kconfig | 298 | ||||
| -rw-r--r-- | drivers/input/joystick/iforce/Kconfig | 33 | ||||
| -rw-r--r-- | drivers/input/keyboard/Kconfig | 90 | ||||
| -rw-r--r-- | drivers/input/misc/Kconfig | 58 | ||||
| -rw-r--r-- | drivers/input/mouse/Kconfig | 121 | ||||
| -rw-r--r-- | drivers/input/serio/Kconfig | 105 | ||||
| -rw-r--r-- | drivers/input/touchscreen/Kconfig | 39 |
9 files changed, 987 insertions, 0 deletions
diff --git a/drivers/input/Kconfig b/drivers/input/Kconfig new file mode 100644 index 000000000000..93701990b4f0 --- /dev/null +++ b/drivers/input/Kconfig @@ -0,0 +1,159 @@ +# +# Input device configuration +# + +menu "Input device support" + +config INPUT + tristate + default y + ---help--- + Say Y here if you have any input device (mouse, keyboard, tablet, + joystick, steering wheel ...) connected to your system and want + it to be available to applications. This includes standard PS/2 + keyboard and mouse. + + Say N here if you have a headless (no monitor, no keyboard) system. + + More information is available: <file:Documentation/input/input.txt> + + If unsure, say Y. + + This driver 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 input.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +comment "Userland interfaces" + +config INPUT_MOUSEDEV + tristate "Mouse interface" + depends on INPUT + ---help--- + Say Y here if you want your mouse to be accessible as char devices + 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an + emulated IntelliMouse Explorer PS/2 mouse. That way, all user space + programs (includung SVGAlib, GPM and X) will be able to use your + mouse. + + If unsure, say Y. + + This driver 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 mousedev.o. If you want to compile it as + a module, say M here and read <file:Documentation/modules.txt>. + +config INPUT_MOUSEDEV_PSAUX + bool "Provide legacy /dev/psaux device" + depends on INPUT_MOUSEDEV + +config INPUT_MOUSEDEV_SCREEN_X + int "Horizontal screen resolution" + depends on INPUT_MOUSEDEV + default "1024" + help + If you're using a digitizer, or a graphic tablet, and want to use + it as a mouse then the mousedev driver needs to know the X window + screen resolution you are using to correctly scale the data. If + you're not using a digitizer, this value is ignored. + +config INPUT_MOUSEDEV_SCREEN_Y + int "Vertical screen resolution" + depends on INPUT_MOUSEDEV + default "768" + help + If you're using a digitizer, or a graphic tablet, and want to use + it as a mouse then the mousedev driver needs to know the X window + screen resolution you are using to correctly scale the data. If + you're not using a digitizer, this value is ignored. + +config INPUT_JOYDEV + tristate "Joystick interface" + depends on INPUT + ---help--- + Say Y here if you want your joystick or gamepad to be + accessible as char device 13:0+ - /dev/input/jsX device. + + If unsure, say Y. + + More information is available: <file:Documentation/input/joystick.txt> + + This driver 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 joydev.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config INPUT_TSDEV + tristate "Touchscreen interface" + depends on INPUT + ---help--- + Say Y here if you have an application that only can understand the + Compaq touchscreen protocol for absolute pointer data. This is + useful namely for embedded configurations. + + If unsure, say N. + + This driver 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 tsdev.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config INPUT_TSDEV_SCREEN_X + int "Horizontal screen resolution" + depends on INPUT_TSDEV + default "240" + +config INPUT_TSDEV_SCREEN_Y + int "Vertical screen resolution" + depends on INPUT_TSDEV + default "320" + +config INPUT_EVDEV + tristate "Event interface" + depends on INPUT + help + Say Y here if you want your input device events be accessible + under char device 13:64+ - /dev/input/eventX in a generic way. + + This driver 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 evdev.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config INPUT_EVBUG + tristate "Event debugging" + depends on INPUT + ---help--- + Say Y here if you have a problem with the input subsystem and + want all events (keypresses, mouse movements), to be output to + the system log. While this is useful for debugging, it's also + a security threat - your keypresses include your passwords, of + course. + + If unsure, say N. + + This driver 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 joydev.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +comment "Input I/O drivers" + +source "drivers/input/gameport/Kconfig" + +source "drivers/input/serio/Kconfig" + +comment "Input Device Drivers" + +source "drivers/input/keyboard/Kconfig" + +source "drivers/input/mouse/Kconfig" + +source "drivers/input/joystick/Kconfig" + +source "drivers/input/touchscreen/Kconfig" + +source "drivers/input/misc/Kconfig" + +endmenu + diff --git a/drivers/input/gameport/Kconfig b/drivers/input/gameport/Kconfig new file mode 100644 index 000000000000..15398e3d219a --- /dev/null +++ b/drivers/input/gameport/Kconfig @@ -0,0 +1,84 @@ +# +# Gameport configuration +# +config GAMEPORT + tristate "Gameport support" + ---help--- + Gameport support is for the standard 15-pin PC gameport. If you + have a joystick, gamepad, gameport card, a soundcard with a gameport + or anything else that uses the gameport, say Y or M here and also to + at least one of the hardware specific drivers. + + For Ensoniq AudioPCI (ES1370), AudioPCI 97 (ES1371), ESS Solo1, + S3 SonicVibes, Trident 4DWave, SiS7018, and ALi 5451 gameport + support is provided by the sound drivers, so you won't need any + from the below listed modules. You still need to say Y here. + + If unsure, say Y. + + This driver 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 gameport.o. If you want to compile it as + a module, say M here and read <file:Documentation/modules.txt>. + +config SOUND_GAMEPORT + tristate + default y if GAMEPORT!=m + default m if GAMEPORT=m + +config GAMEPORT_NS558 + tristate "Classic ISA and PnP gameport support" + depends on GAMEPORT + help + Say Y here if you have an ISA or PnP gameport. + + If unsure, say Y. + + This driver 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 ns558.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config GAMEPORT_L4 + tristate "PDPI Lightning 4 gamecard support" + depends on GAMEPORT + help + Say Y here if you have a PDPI Lightning 4 gamecard. + + This driver 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 lightning.o. If you want to compile it as + a module, say M here and read <file:Documentation/modules.txt>. + +config GAMEPORT_EMU10K1 + tristate "SB Live and Audigy gameport support" + depends on GAMEPORT + help + Say Y here if you have a SoundBlaster Live! or SoundBlaster + Audigy card and want to use its gameport. + + This driver 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 emu10k1-gp.o. If you want to compile it as + a module, say M here and read <file:Documentation/modules.txt>. + +config GAMEPORT_VORTEX + tristate "Aureal Vortex, Vortex 2 gameport support" + depends on GAMEPORT + help + Say Y here if you have an Aureal Vortex 1 or 2 card and want + to use its gameport. + + This driver 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 vortex.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config GAMEPORT_FM801 + tristate "ForteMedia FM801 gameport support" + depends on GAMEPORT + +config GAMEPORT_CS461x + tristate "Crystal SoundFusion gameport support" + depends on GAMEPORT + diff --git a/drivers/input/joystick/Kconfig b/drivers/input/joystick/Kconfig new file mode 100644 index 000000000000..29beebccdd18 --- /dev/null +++ b/drivers/input/joystick/Kconfig @@ -0,0 +1,298 @@ +# +# Joystick driver configuration +# +config INPUT_JOYSTICK + bool "Joysticks" + depends on INPUT + help + If you have a joystick, 6dof controller, gamepad, steering wheel, + weapon control system or something like that you can say Y here + and the list of supported devices will be displayed. This option + doesn't affect the kernel. + + Please read the file <file:Documentation/input/joystick.txt> which + contains more information. + +config JOYSTICK_ANALOG + tristate "Classic PC analog joysticks and gamepads" + depends on INPUT && INPUT_JOYSTICK && GAMEPORT + ---help--- + Say Y here if you have a joystick that connects to the PC + gameport. In addition to the usual PC analog joystick, this driver + supports many extensions, including joysticks with throttle control, + with rudders, additional hats and buttons compatible with CH + Flightstick Pro, ThrustMaster FCS, 6 and 8 button gamepads, or + Saitek Cyborg joysticks. + + Please read the file <file:Documentation/input/joystick.txt> which + contains more information. + + This driver 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 analog.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_A3D + tristate "Assasin 3D and MadCatz Panther devices" + depends on INPUT && INPUT_JOYSTICK && GAMEPORT + help + Say Y here if you have an FPGaming or MadCatz controller using the + A3D protocol over the PC gameport. + + This driver 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 a3d.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_ADI + tristate "Logitech ADI digital joysticks and gamepads" + depends on INPUT && INPUT_JOYSTICK && GAMEPORT + help + Say Y here if you have a Logitech controller using the ADI + protocol over the PC gameport. + + This driver 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 adi.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_COBRA + tristate "Creative Labs Blaster Cobra gamepad" + depends on INPUT && INPUT_JOYSTICK && GAMEPORT + help + Say Y here if you have a Creative Labs Blaster Cobra gamepad. + + This driver 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 cobra.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_GF2K + tristate "Genius Flight2000 Digital joysticks and gamepads" + depends on INPUT && INPUT_JOYSTICK && GAMEPORT + help + Say Y here if you have a Genius Flight2000 or MaxFighter digitally + communicating joystick or gamepad. + + This driver 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 gf2k.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_GRIP + tristate "Gravis GrIP joysticks and gamepads" + depends on INPUT && INPUT_JOYSTICK && GAMEPORT + help + Say Y here if you have a Gravis controller using the GrIP protocol + over the PC gameport. + + This driver 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 grip.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_GRIP_MP + tristate "Gravis GrIP MultiPort" + depends on INPUT && INPUT_JOYSTICK && GAMEPORT + help + Say Y here if you have the original Gravis GrIP MultiPort, a hub + that connects to the gameport and you connect gamepads to it. + + This driver 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 grip_mp.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_GUILLEMOT + tristate "Guillemot joysticks and gamepads" + depends on INPUT && INPUT_JOYSTICK && GAMEPORT + help + Say Y here if you have a Guillemot joystick using a digital + protocol over the PC gameport. + + This driver 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 guillemot.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_INTERACT + tristate "InterAct digital joysticks and gamepads" + depends on INPUT && INPUT_JOYSTICK && GAMEPORT + help + Say Y here if you have an InterAct gameport or joystick + communicating digitally over the gameport. + + This driver 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 interact.o. If you want to compile it as + a module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_SIDEWINDER + tristate "Microsoft SideWinder digital joysticks and gamepads" + depends on INPUT && INPUT_JOYSTICK && GAMEPORT + help + Say Y here if you have a Microsoft controller using the Digital + Overdrive protocol over PC gameport. + + This driver 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 sidewinder.o. If you want to compile it + as a module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_TMDC + tristate "ThrustMaster DirectConnect joysticks and gamepads" + depends on INPUT && INPUT_JOYSTICK && GAMEPORT + help + Say Y here if you have a ThrustMaster controller using the + DirectConnect (BSP) protocol over the PC gameport. + + This driver 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 tmdc.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +source "drivers/input/joystick/iforce/Kconfig" + +config JOYSTICK_WARRIOR + tristate "Logitech WingMan Warrior joystick" + depends on INPUT && INPUT_JOYSTICK && SERIO + help + Say Y here if you have a Logitech WingMan Warrior joystick connected + to your computer's serial port. + + This driver 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 warrior.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_MAGELLAN + tristate "LogiCad3d Magellan/SpaceMouse 6dof controllers" + depends on INPUT && INPUT_JOYSTICK && SERIO + help + Say Y here if you have a Magellan or Space Mouse 6DOF controller + connected to your computer's serial port. + + This driver 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 magellan.o. If you want to compile it as + a module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_SPACEORB + tristate "SpaceTec SpaceOrb/Avenger 6dof controllers" + depends on INPUT && INPUT_JOYSTICK && SERIO + help + Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF + controller connected to your computer's serial port. + + This driver 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 spaceorb.o. If you want to compile it as + a module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_SPACEBALL + tristate "SpaceTec SpaceBall 6dof controllers" + depends on INPUT && INPUT_JOYSTICK && SERIO + help + Say Y here if you have a SpaceTec SpaceBall 2003/3003/4000 FLX + controller connected to your computer's serial port. For the + SpaceBall 4000 USB model, use the USB HID driver. + + This driver 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 spaceball.o. If you want to compile it as + a module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_STINGER + tristate "Gravis Stinger gamepad" + depends on INPUT && INPUT_JOYSTICK && SERIO + help + Say Y here if you have a Gravis Stinger connected to one of your + serial ports. + + This driver 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 stinger.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_TWIDDLER + tristate "Twiddler as a joystick" + depends on INPUT && INPUT_JOYSTICK && SERIO + help + Say Y here if you have a Handykey Twiddler connected to your + computer's serial port and want to use it as a joystick. + + This driver 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 twidjoy.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_DB9 + tristate "Multisystem, Sega Genesis, Saturn joysticks and gamepads" + depends on INPUT && INPUT_JOYSTICK && PARPORT + ---help--- + Say Y here if you have a Sega Master System gamepad, Sega Genesis + gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga, + Commodore, Amstrad CPC joystick connected to your parallel port. + For more information on how to use the driver please read + <file:Documentation/input/joystick-parport.txt>. + + This driver 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 db9.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_GAMECON + tristate "Multisystem, NES, SNES, N64, PSX joysticks and gamepads" + depends on INPUT && INPUT_JOYSTICK && PARPORT + ---help--- + Say Y here if you have a Nintendo Entertainment System gamepad, + Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad, + Sony PlayStation gamepad or a Multisystem -- Atari, Amiga, + Commodore, Amstrad CPC joystick connected to your parallel port. + For more information on how to use the driver please read + <file:Documentation/input/joystick-parport.txt>. + + This driver 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 gamecon.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_TURBOGRAFX + tristate "Multisystem joysticks via TurboGraFX device" + depends on INPUT && INPUT_JOYSTICK && PARPORT + help + Say Y here if you have the TurboGraFX interface by Steffen Schwenke, + and want to use it with Multisystem -- Atari, Amiga, Commodore, + Amstrad CPC joystick. For more information on how to use the driver + please read <file:Documentation/input/joystick-parport.txt>. + + This driver 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 turbografx.o. If you want to compile it + as a module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_AMIGA + tristate "Amiga joysticks" + depends on AMIGA && INPUT && INPUT_JOYSTICK + help + Say Y here if you have an Amiga with a digital joystick connected + to it. + + This driver 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 amijoy.o. If you want to compile it as + a module, say M here and read <file:Documentation/modules.txt>. + +config INPUT_JOYDUMP + tristate "Gameport data dumper" + depends on INPUT && INPUT_JOYSTICK + help + Say Y here if you want to dump data from your joystick into the system + log for debugging purposes. Say N if you are making a production + configuration or aren't sure. + + This driver 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 joydump.o. If you want to compile it as + a module, say M here and read <file:Documentation/modules.txt>. + diff --git a/drivers/input/joystick/iforce/Kconfig b/drivers/input/joystick/iforce/Kconfig new file mode 100644 index 000000000000..7e7457ceb137 --- /dev/null +++ b/drivers/input/joystick/iforce/Kconfig @@ -0,0 +1,33 @@ +# +# I-Force driver configuration +# +config JOYSTICK_IFORCE + tristate "I-Force devices" + depends on INPUT && INPUT_JOYSTICK + help + Say Y here if you have an I-Force joystick or steering wheel + + You also must choose at least one of the two options below. + + This driver 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 iforce.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config JOYSTICK_IFORCE_USB + bool "I-Force USB joysticks and wheels" + depends on JOYSTICK_IFORCE && (JOYSTICK_IFORCE=m || USB=y) && USB + help + Say Y here if you have an I-Force joystick or steering wheel + connected to your USB port. + +config JOYSTICK_IFORCE_232 + bool "I-Force Serial joysticks and wheels" + depends on JOYSTICK_IFORCE && (JOYSTICK_IFORCE=m || SERIO=y) && SERIO + help + Say Y here if you have an I-Force joystick or steering wheel + connected to your serial (COM) port. + + You will need an additional utility called inputattach, see + Documentation/input/joystick.txt and ff.txt. + diff --git a/drivers/input/keyboard/Kconfig b/drivers/input/keyboard/Kconfig new file mode 100644 index 000000000000..b2da525b22bc --- /dev/null +++ b/drivers/input/keyboard/Kconfig @@ -0,0 +1,90 @@ +# +# Input core configuration +# +config INPUT_KEYBOARD + bool "Keyboards" + depends on INPUT + help + Say Y here, and a list of supported keyboards will be displayed. + This option doesn't affect the kernel. + + If unsure, say Y. + +config KEYBOARD_ATKBD + tristate "AT keyboard support" + depends on INPUT && INPUT_KEYBOARD && SERIO + ---help--- + Say Y here if you want to use the standard AT keyboard. Usually + you'll need this, unless you have a different type keyboard (USB, + ADB or other). This also works for AT keyboards connected over + a PS/2 to serial converter. + + If unsure, say Y. + + This driver 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 atkbd.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config KEYBOARD_SUNKBD + tristate "Sun Type 4 and Type 5 keyboard support" + depends on INPUT && INPUT_KEYBOARD && SERIO + help + Say Y here if you want to use a Sun Type 4 or Type 5 keyboard, + connected either to the Sun keyboard connector or to an serial + (RS-232) port via a simple adapter. + + This driver 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 sunkbd.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config KEYBOARD_XTKBD + tristate "XT Keyboard support" + depends on INPUT && INPUT_KEYBOARD && SERIO + help + Say Y here if you want to use the old IBM PC/XT keyboard (or + compatible) on your system. This is only possible with a + parallel port keyboard adapter, you cannot connect it to the + keyboard port on a PC that runs Linux. + + This driver 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 xtkbd.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config KEYBOARD_NEWTON + tristate "Newton keyboard" + depends on INPUT && INPUT_KEYBOARD && SERIO + help + Say Y here if you have a Newton keyboard on a serial port. + + This driver 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 maple_keyb.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config KEYBOARD_MAPLE + tristate "Maple bus keyboard support" + depends on SH_DREAMCAST && INPUT && INPUT_KEYBOARD && MAPLE + help + Say Y here if you have a DreamCast console running Linux and have + a keyboard attached to its Maple bus. + + This driver 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 maple_keyb.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config KEYBOARD_AMIGA + tristate "Amiga keyboard" + depends on AMIGA && INPUT && INPUT_KEYBOARD + help + Say Y here if you are running Linux on any AMIGA and have a keyboard + attached. + + This driver 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 amikbd.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + diff --git a/drivers/input/misc/Kconfig b/drivers/input/misc/Kconfig new file mode 100644 index 000000000000..c3d5fc08708f --- /dev/null +++ b/drivers/input/misc/Kconfig @@ -0,0 +1,58 @@ +# +# Input misc drivers configuration +# +config INPUT_MISC + bool "Misc" + depends on INPUT + help + + Say Y here, and a list of miscellaneous input drivers will be displayed. + Everything that didn't fit into the other categories is here. This option + doesn't affect the kernel. + + If unsure, say Y. + +config INPUT_PCSPKR + tristate "PC Speaker support" + depends on INPUT && INPUT_MISC + help + Say Y here if you want the standard PC Speaker to be used for + bells and whistles. + + If unsure, say Y. + + This driver 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 pcspkr.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config INPUT_SPARCSPKR + tristate "SPARC Speaker support" + depends on (SPARC32 || SPARC64) && INPUT && INPUT_MISC + help + Say Y here if you want the standard Speaker on Sparc PCI systems + to be used for bells and whistles. + + If unsure, say Y. + + This driver 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 pcspkr.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config INPUT_M68K_BEEP + tristate "M68k Beeper support" + depends on M68K && INPUT && INPUT_MISC + +config INPUT_UINPUT + tristate "User level driver support" + depends on INPUT && INPUT_MISC + help + Say Y here if you want to support user level drivers for input + subsystem accessible under char device 10:223 - /dev/input/uinput. + + This driver 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 uinput.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + diff --git a/drivers/input/mouse/Kconfig b/drivers/input/mouse/Kconfig new file mode 100644 index 000000000000..5c7eee5151c8 --- /dev/null +++ b/drivers/input/mouse/Kconfig @@ -0,0 +1,121 @@ +# +# Mouse driver configuration +# +config INPUT_MOUSE + bool "Mice" + depends on INPUT + help + Say Y here, and a list of supported mice will be displayed. + This option doesn't affect the kernel. + + If unsure, say Y. + +config MOUSE_PS2 + tristate "PS/2 mouse" + depends on INPUT && INPUT_MOUSE && SERIO + ---help--- + Say Y here if you have a PS/2 mouse connected to your system. This + includes the standard 2 or 3-button PS/2 mouse, as well as PS/2 + mice with wheels and extra buttons, Microsoft, Logitech or Genius + compatible. + + If unsure, say Y. + + This driver 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 psmouse.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config MOUSE_SERIAL + tristate "Serial mouse" + depends on INPUT && INPUT_MOUSE && SERIO + ---help--- + Say Y here if you have a serial (RS-232, COM port) mouse connected + to your system. This includes Sun, MouseSystems, Microsoft, + Logitech and all other compatible serial mice. + + If unsure, say N. + + This driver 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 sermouse.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config MOUSE_INPORT + tristate "InPort/MS/ATIXL busmouse" + depends on INPUT && INPUT_MOUSE && ISA + help + Say Y here if you have an InPort, Microsoft or ATI XL busmouse. + They are rather rare these days. + + This driver 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 inport.o. If you want to compile it as a + module, say M here and read <file.:Documentation/modules.txt>. + +config MOUSE_ATIXL + bool "ATI XL variant" + depends on MOUSE_INPORT + help + Say Y here if your mouse is of the ATI XL variety. + +config MOUSE_LOGIBM + tristate "Logitech busmouse" + depends on INPUT && INPUT_MOUSE && ISA + help + Say Y here if you have a Logitech busmouse. + They are rather rare these days. + + This driver 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 logibm.o. If you want to compile it as a + module, say M here and read <file.:Documentation/modules.txt>. + +config MOUSE_PC110PAD + tristate "IBM PC110 touchpad" + depends on INPUT && INPUT_MOUSE && ISA + help + Say Y if you have the IBM PC-110 micro-notebook and want its + touchpad supported. + + This driver 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 pc110pad.o. If you want to compile it as a + module, say M here and read <file.:Documentation/modules.txt>. + +config MOUSE_MAPLE + tristate "Maple bus mouse" + depends on SH_DREAMCAST && INPUT && INPUT_MOUSE && MAPLE + help + Say Y if you have a DreamCast console and a mouse attached to + its Maple bus. + + This driver 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 maplemouse.o. If you want to compile it as a + module, say M here and read <file.:Documentation/modules.txt>. + +config MOUSE_AMIGA + tristate "Amiga mouse" + depends on AMIGA && INPUT && INPUT_MOUSE + help + Say Y here if you have an Amiga and want its native mouse + supported by the kernel. + + This driver 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 amimouse.o. If you want to compile it as a + module, say M here and read <file.:Documentation/modules.txt>. + +config MOUSE_ACORN + tristate "Acorn RiscPC mouse" + depends on ARCH_ACORN && INPUT && INPUT_MOUSE + help + Say Y here if you have the Acorn RiscPC computer and want its + native mouse supported. + + This driver 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 rpcmouse.o. If you want to compile it as a + module, say M here and read <file.:Documentation/modules.txt>. + diff --git a/drivers/input/serio/Kconfig b/drivers/input/serio/Kconfig new file mode 100644 index 000000000000..bb0a2656b8af --- /dev/null +++ b/drivers/input/serio/Kconfig @@ -0,0 +1,105 @@ +# +# Input core configuration +# +config SERIO + tristate "Serial i/o support" + ---help--- + Say Yes here if you have any input device that uses serial I/O to + communicate with the system. This includes the + * standard AT keyboard and PS/2 mouse * + as well as serial mice, Sun keyboards, some joysticks and 6dof + devices and more. + + If unsure, say Y. + + This driver 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 serio.o. If you want to compile it + as a module, say M here and read <file:Documentation/modules.txt>. + +config SERIO_I8042 + tristate "i8042 PC Keyboard controller" + depends on SERIO + ---help--- + i8042 is the chip over which the standard AT keyboard and PS/2 + mouse are connected to the computer. If you use these devices, + you'll need to say Y here. + + If unsure, say Y. + + This driver 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 i8042.o. If you want to compile it + as a module, say M here and read <file:Documentation/modules.txt>. + +config SERIO_SERPORT + tristate "Serial port line discipline" + depends on SERIO + ---help--- + Say Y here if you plan to use an input device (mouse, joystick, + tablet, 6dof) that communicates over the RS232 serial (COM) port. + + More information is available: <file:Documentation/input/input.txt> + + If unsure, say Y. + + This driver 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 serport.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config SERIO_CT82C710 + tristate "ct82c710 Aux port controller" + depends on SERIO + ---help--- + Say Y here if you have a Texas Instruments TravelMate notebook + equipped with the ct82c710 chip and want to use a mouse connected + to the "QuickPort". + + If unsure, say N. + + This driver 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 ct82c710.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config SERIO_Q40KBD + tristate "Q40 keyboard controller" + depends on Q40 && SERIO + +config SERIO_PARKBD + tristate "Parallel port keyboard adapter" + depends on SERIO && PARPORT + ---help--- + Say Y here if you built a simple parallel port adapter to attach + an additional AT keyboard, XT keyboard or PS/2 mouse. + + More information is available: <file:Documentation/input/input.txt> + + If unsure, say N. + + This driver 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 parkbd.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config SERIO_ACORN + tristate "Acorn RiscPC keyboard controller" + depends on ARCH_ACORN && SERIO + help + Say Y here if you have the Acorn RiscPC and want to use an AT + keyboard connected to its keyboard controller. + + This driver 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 rpckbd.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config SERIO_AMBAKMI + tristate "AMBA KMI keyboard controller" + depends on ARCH_INTEGRATOR && SERIO + +config SERIO_SA1111 + tristate "Intel SA1111 keyboard controller" + depends on SA1111 && SERIO + diff --git a/drivers/input/touchscreen/Kconfig b/drivers/input/touchscreen/Kconfig new file mode 100644 index 000000000000..6823af8eae36 --- /dev/null +++ b/drivers/input/touchscreen/Kconfig @@ -0,0 +1,39 @@ +# +# Mouse driver configuration +# +config INPUT_TOUCHSCREEN + bool "Touchscreens" + depends on INPUT + help + Say Y here, and a list of supported touchscreens will be displayed. + This option doesn't affect the kernel. + + If unsure, say Y. + +config TOUCHSCREEN_BITSY + tristate "Compaq iPAQ H3600 (Bitsy) touchscreen input driver" + depends on SA1100_BITSY && INPUT && INPUT_TOUCHSCREEN && SERIO + help + Say Y here if you have the h3600 (Bitsy) touchscreen. + + If unsure, say N. + + This driver 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 gunze.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + +config TOUCHSCREEN_GUNZE + tristate "Gunze AHL-51S touchscreen" + depends on INPUT && INPUT_TOUCHSCREEN && SERIO + help + Say Y here if you have the Gunze AHL-51 touchscreen connected to + your system. + + If unsure, say N. + + This driver 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 gunze.o. If you want to compile it as a + module, say M here and read <file:Documentation/modules.txt>. + |