mirror of
https://github.com/adulau/aha.git
synced 2024-12-29 12:16:20 +00:00
52fe0cdb09
This driver supports the application buttons on some Fujitsu Lifebook laptops. It is based on the earlier apanel driver done by Jochen Eisenger, but with many changes. The original driver used ioctl's and a separate user space program (see http://apanel.sourceforge.net). This driver hooks into the input subsystem so that the normal keys act as expected without a daemon. In addition to buttons, the Mail Led is handled via LEDs class device. The driver now supports redefinable keymaps and no longer has to have a DMI table for all Fujitsu laptops. I thought about mixing this driver should be integrated into the Fujitsu laptop extras driver that handles backlight, but rejected the idea because it wasn't clear if all the Fujitsu laptops supported both. Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
200 lines
6.2 KiB
Text
200 lines
6.2 KiB
Text
#
|
|
# Input misc drivers configuration
|
|
#
|
|
menuconfig INPUT_MISC
|
|
bool "Miscellaneous devices"
|
|
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.
|
|
|
|
if INPUT_MISC
|
|
|
|
config INPUT_PCSPKR
|
|
tristate "PC Speaker support"
|
|
depends on ALPHA || X86 || MIPS || PPC_PREP || PPC_CHRP || PPC_PSERIES
|
|
help
|
|
Say Y here if you want the standard PC Speaker to be used for
|
|
bells and whistles.
|
|
|
|
If unsure, say Y.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called pcspkr.
|
|
|
|
config INPUT_SPARCSPKR
|
|
tristate "SPARC Speaker support"
|
|
depends on PCI && SPARC64
|
|
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.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called sparcspkr.
|
|
|
|
config INPUT_M68K_BEEP
|
|
tristate "M68k Beeper support"
|
|
depends on M68K
|
|
|
|
config INPUT_APANEL
|
|
tristate "Fujitsu Lifebook Application Panel buttons"
|
|
depends on X86
|
|
select I2C_I801
|
|
select INPUT_POLLDEV
|
|
select CHECK_SIGNATURE
|
|
help
|
|
Say Y here for support of the Application Panel buttons, used on
|
|
Fujitsu Lifebook. These are attached to the mainboard through
|
|
an SMBus interface managed by the I2C Intel ICH (i801) driver.
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
be called apanel.
|
|
|
|
config INPUT_IXP4XX_BEEPER
|
|
tristate "IXP4XX Beeper support"
|
|
depends on ARCH_IXP4XX
|
|
help
|
|
If you say yes here, you can connect a beeper to the
|
|
ixp4xx gpio pins. This is used by the LinkSys NSLU2.
|
|
|
|
If unsure, say Y.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called ixp4xx-beeper.
|
|
|
|
config INPUT_COBALT_BTNS
|
|
tristate "Cobalt button interface"
|
|
depends on MIPS_COBALT
|
|
select INPUT_POLLDEV
|
|
help
|
|
Say Y here if you want to support MIPS Cobalt button interface.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called cobalt_btns.
|
|
|
|
config INPUT_WISTRON_BTNS
|
|
tristate "x86 Wistron laptop button interface"
|
|
depends on X86 && !X86_64
|
|
select INPUT_POLLDEV
|
|
select NEW_LEDS
|
|
select LEDS_CLASS
|
|
select CHECK_SIGNATURE
|
|
help
|
|
Say Y here for support of Wistron laptop button interfaces, used on
|
|
laptops of various brands, including Acer and Fujitsu-Siemens. If
|
|
available, mail and wifi LEDs will be controllable via /sys/class/leds.
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
be called wistron_btns.
|
|
|
|
config INPUT_ATLAS_BTNS
|
|
tristate "x86 Atlas button interface"
|
|
depends on X86 && ACPI
|
|
help
|
|
Say Y here for support of Atlas wallmount touchscreen buttons.
|
|
The events will show up as scancodes F1 through F9 via evdev.
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
be called atlas_btns.
|
|
|
|
config INPUT_ATI_REMOTE
|
|
tristate "ATI / X10 USB RF remote control"
|
|
depends on USB_ARCH_HAS_HCD
|
|
select USB
|
|
help
|
|
Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
|
|
These are RF remotes with USB receivers.
|
|
The ATI remote comes with many of ATI's All-In-Wonder video cards.
|
|
The X10 "Lola" remote is available at:
|
|
<http://www.x10.com/products/lola_sg1.htm>
|
|
This driver provides mouse pointer, left and right mouse buttons,
|
|
and maps all the other remote buttons to keypress events.
|
|
|
|
To compile this driver as a module, choose M here: the module will be
|
|
called ati_remote.
|
|
|
|
config INPUT_ATI_REMOTE2
|
|
tristate "ATI / Philips USB RF remote control"
|
|
depends on USB_ARCH_HAS_HCD
|
|
select USB
|
|
help
|
|
Say Y here if you want to use an ATI or Philips USB RF remote control.
|
|
These are RF remotes with USB receivers.
|
|
ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
|
|
and is also available as a separate product.
|
|
This driver provides mouse pointer, left and right mouse buttons,
|
|
and maps all the other remote buttons to keypress events.
|
|
|
|
To compile this driver as a module, choose M here: the module will be
|
|
called ati_remote2.
|
|
|
|
config INPUT_KEYSPAN_REMOTE
|
|
tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
|
|
depends on EXPERIMENTAL
|
|
depends on USB_ARCH_HAS_HCD
|
|
select USB
|
|
help
|
|
Say Y here if you want to use a Keyspan DMR USB remote control.
|
|
Currently only the UIA-11 type of receiver has been tested. The tag
|
|
on the receiver that connects to the USB port should have a P/N that
|
|
will tell you what type of DMR you have. The UIA-10 type is not
|
|
supported at this time. This driver maps all buttons to keypress
|
|
events.
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
be called keyspan_remote.
|
|
|
|
config INPUT_POWERMATE
|
|
tristate "Griffin PowerMate and Contour Jog support"
|
|
depends on USB_ARCH_HAS_HCD
|
|
select USB
|
|
help
|
|
Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
|
|
These are aluminum dials which can measure clockwise and anticlockwise
|
|
rotation. The dial also acts as a pushbutton. The base contains an LED
|
|
which can be instructed to pulse or to switch to a particular intensity.
|
|
|
|
You can download userspace tools from
|
|
<http://sowerbutts.com/powermate/>.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called powermate.
|
|
|
|
config INPUT_YEALINK
|
|
tristate "Yealink usb-p1k voip phone"
|
|
depends on EXPERIMENTAL
|
|
depends on USB_ARCH_HAS_HCD
|
|
select USB
|
|
help
|
|
Say Y here if you want to enable keyboard and LCD functions of the
|
|
Yealink usb-p1k usb phones. The audio part is enabled by the generic
|
|
usb sound driver, so you might want to enable that as well.
|
|
|
|
For information about how to use these additional functions, see
|
|
<file:Documentation/input/yealink.txt>.
|
|
|
|
To compile this driver as a module, choose M here: the module will be
|
|
called yealink.
|
|
|
|
config INPUT_UINPUT
|
|
tristate "User level driver support"
|
|
help
|
|
Say Y here if you want to support user level drivers for input
|
|
subsystem accessible under char device 10:223 - /dev/input/uinput.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called uinput.
|
|
|
|
config HP_SDC_RTC
|
|
tristate "HP SDC Real Time Clock"
|
|
depends on GSC || HP300
|
|
select HP_SDC
|
|
help
|
|
Say Y here if you want to support the built-in real time clock
|
|
of the HP SDC controller.
|
|
|
|
endif
|