2005-04-16 22:20:36 +00:00
|
|
|
#
|
|
|
|
# Misc strange devices
|
|
|
|
#
|
|
|
|
|
2011-03-21 16:59:36 +00:00
|
|
|
# This one has to live outside of the MISC_DEVICES conditional,
|
|
|
|
# because it may be selected by drivers/platform/x86/hp_accel.
|
|
|
|
config SENSORS_LIS3LV02D
|
|
|
|
tristate
|
|
|
|
depends on INPUT
|
|
|
|
select INPUT_POLLDEV
|
|
|
|
default n
|
|
|
|
|
2007-07-16 06:40:15 +00:00
|
|
|
menuconfig MISC_DEVICES
|
2007-07-16 06:39:29 +00:00
|
|
|
bool "Misc devices"
|
2007-08-18 10:56:21 +00:00
|
|
|
---help---
|
|
|
|
Say Y here to get to see options for device drivers from various
|
|
|
|
different categories. This option alone does not add any kernel code.
|
|
|
|
|
|
|
|
If you say N, all options in this submenu will be skipped and disabled.
|
2007-07-16 06:39:29 +00:00
|
|
|
|
2007-07-16 06:40:15 +00:00
|
|
|
if MISC_DEVICES
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2009-12-15 02:00:15 +00:00
|
|
|
config AD525X_DPOT
|
ad525x_dpot: add support for SPI parts
Split the bus logic out into separate files so that we can handle I2C and
SPI busses independently. The new SPI bus logic brings in support for a
lot more parts:
AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
AD7376, AD8400, AD8402, AD8403, ADN2850
[randy.dunlap@oracle.com: fix ad525X_dpot build]
Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-05-24 21:33:14 +00:00
|
|
|
tristate "Analog Devices Digital Potentiometers"
|
|
|
|
depends on (I2C || SPI) && SYSFS
|
2009-12-15 02:00:15 +00:00
|
|
|
help
|
|
|
|
If you say yes here, you get support for the Analog Devices
|
ad525x_dpot: add support for SPI parts
Split the bus logic out into separate files so that we can handle I2C and
SPI busses independently. The new SPI bus logic brings in support for a
lot more parts:
AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
AD7376, AD8400, AD8402, AD8403, ADN2850
[randy.dunlap@oracle.com: fix ad525X_dpot build]
Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-05-24 21:33:14 +00:00
|
|
|
AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
|
|
|
|
AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
|
|
|
|
AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
|
|
|
|
AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
|
2010-05-24 21:33:15 +00:00
|
|
|
AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
|
2010-05-24 21:33:15 +00:00
|
|
|
AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
|
2010-10-26 21:22:36 +00:00
|
|
|
ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
|
|
|
|
AD5271, AD5272, AD5274
|
2009-12-15 02:00:15 +00:00
|
|
|
digital potentiometer chips.
|
|
|
|
|
|
|
|
See Documentation/misc-devices/ad525x_dpot.txt for the
|
|
|
|
userspace interface.
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
will be called ad525x_dpot.
|
|
|
|
|
ad525x_dpot: add support for SPI parts
Split the bus logic out into separate files so that we can handle I2C and
SPI busses independently. The new SPI bus logic brings in support for a
lot more parts:
AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
AD7376, AD8400, AD8402, AD8403, ADN2850
[randy.dunlap@oracle.com: fix ad525X_dpot build]
Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-05-24 21:33:14 +00:00
|
|
|
config AD525X_DPOT_I2C
|
|
|
|
tristate "support I2C bus connection"
|
|
|
|
depends on AD525X_DPOT && I2C
|
|
|
|
help
|
|
|
|
Say Y here if you have a digital potentiometers hooked to an I2C bus.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
module will be called ad525x_dpot-i2c.
|
|
|
|
|
|
|
|
config AD525X_DPOT_SPI
|
|
|
|
tristate "support SPI bus connection"
|
|
|
|
depends on AD525X_DPOT && SPI_MASTER
|
|
|
|
help
|
|
|
|
Say Y here if you have a digital potentiometers hooked to an SPI bus.
|
|
|
|
|
|
|
|
If unsure, say N (but it's safe to say "Y").
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
module will be called ad525x_dpot-spi.
|
|
|
|
|
2008-02-08 12:21:21 +00:00
|
|
|
config ATMEL_PWM
|
|
|
|
tristate "Atmel AT32/AT91 PWM support"
|
2008-10-16 05:01:55 +00:00
|
|
|
depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
|
2008-02-08 12:21:21 +00:00
|
|
|
help
|
|
|
|
This option enables device driver support for the PWM channels
|
2009-01-26 10:12:25 +00:00
|
|
|
on certain Atmel processors. Pulse Width Modulation is used for
|
|
|
|
purposes including software controlled power-efficient backlights
|
2008-02-08 12:21:21 +00:00
|
|
|
on LCD displays, motor control, and waveform generation.
|
|
|
|
|
2010-09-06 06:54:52 +00:00
|
|
|
config AB8500_PWM
|
|
|
|
bool "AB8500 PWM support"
|
2010-12-20 12:28:11 +00:00
|
|
|
depends on AB8500_CORE && ARCH_U8500
|
2010-09-06 06:54:52 +00:00
|
|
|
select HAVE_PWM
|
|
|
|
help
|
|
|
|
This driver exports functions to enable/disble/config/free Pulse
|
|
|
|
Width Modulation in the Analog Baseband Chip AB8500.
|
|
|
|
It is used by led and backlight driver to control the intensity.
|
|
|
|
|
2008-02-23 01:23:23 +00:00
|
|
|
config ATMEL_TCLIB
|
|
|
|
bool "Atmel AT32/AT91 Timer/Counter Library"
|
|
|
|
depends on (AVR32 || ARCH_AT91)
|
|
|
|
help
|
|
|
|
Select this if you want a library to allocate the Timer/Counter
|
|
|
|
blocks found on many Atmel processors. This facilitates using
|
|
|
|
these blocks by different drivers despite processor differences.
|
|
|
|
|
2008-02-23 01:28:37 +00:00
|
|
|
config ATMEL_TCB_CLKSRC
|
|
|
|
bool "TC Block Clocksource"
|
2010-07-14 00:56:20 +00:00
|
|
|
depends on ATMEL_TCLIB
|
2008-02-23 01:28:37 +00:00
|
|
|
default y
|
|
|
|
help
|
|
|
|
Select this to get a high precision clocksource based on a
|
|
|
|
TC block with a 5+ MHz base clock rate. Two timer channels
|
|
|
|
are combined to make a single 32-bit timer.
|
|
|
|
|
|
|
|
When GENERIC_CLOCKEVENTS is defined, the third timer channel
|
|
|
|
may be used as a clock event device supporting oneshot mode
|
|
|
|
(delays of up to two seconds) based on the 32 KiHz clock.
|
|
|
|
|
|
|
|
config ATMEL_TCB_CLKSRC_BLOCK
|
|
|
|
int
|
|
|
|
depends on ATMEL_TCB_CLKSRC
|
|
|
|
prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
|
|
|
|
default 0
|
|
|
|
range 0 1
|
|
|
|
help
|
|
|
|
Some chips provide more than one TC block, so you have the
|
|
|
|
choice of which one to use for the clock framework. The other
|
|
|
|
TC can be used for other purposes, such as PWM generation and
|
|
|
|
interval timing.
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config IBM_ASM
|
|
|
|
tristate "Device driver for IBM RSA service processor"
|
2007-07-17 11:04:01 +00:00
|
|
|
depends on X86 && PCI && INPUT && EXPERIMENTAL
|
2005-04-16 22:20:36 +00:00
|
|
|
---help---
|
|
|
|
This option enables device driver support for in-band access to the
|
|
|
|
IBM RSA (Condor) service processor in eServer xSeries systems.
|
|
|
|
The ibmasm device driver allows user space application to access
|
|
|
|
ASM (Advanced Systems Management) functions on the service
|
|
|
|
processor. The driver is meant to be used in conjunction with
|
|
|
|
a user space API.
|
|
|
|
The ibmasm driver also enables the OS to use the UART on the
|
|
|
|
service processor board as a regular serial port. To make use of
|
|
|
|
this feature serial driver support (CONFIG_SERIAL_8250) must be
|
|
|
|
enabled.
|
2006-10-04 09:15:38 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
WARNING: This software may not be supported or function
|
|
|
|
correctly on your IBM server. Please consult the IBM ServerProven
|
2010-10-18 09:03:14 +00:00
|
|
|
website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
|
|
|
|
for information on the specific driver level and support statement
|
2005-04-16 22:20:36 +00:00
|
|
|
for your IBM server.
|
|
|
|
|
2007-05-08 07:31:45 +00:00
|
|
|
config PHANTOM
|
2008-07-25 08:48:23 +00:00
|
|
|
tristate "Sensable PHANToM (PCI)"
|
2007-05-08 07:31:45 +00:00
|
|
|
depends on PCI
|
|
|
|
help
|
|
|
|
Say Y here if you want to build a driver for Sensable PHANToM device.
|
|
|
|
|
2008-07-25 08:48:23 +00:00
|
|
|
This driver is only for PCI PHANToMs.
|
|
|
|
|
2007-05-08 07:31:45 +00:00
|
|
|
If you choose to build module, its name will be phantom. If unsure,
|
|
|
|
say N here.
|
|
|
|
|
2011-05-06 23:56:49 +00:00
|
|
|
config INTEL_MID_PTI
|
|
|
|
tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
The PTI (Parallel Trace Interface) driver directs
|
|
|
|
trace data routed from various parts in the system out
|
|
|
|
through an Intel Penwell PTI port and out of the mobile
|
|
|
|
device for analysis with a debugging tool (Lauterbach or Fido).
|
|
|
|
|
|
|
|
You should select this driver if the target kernel is meant for
|
|
|
|
an Intel Atom (non-netbook) mobile device containing a MIPI
|
|
|
|
P1149.7 standard implementation.
|
|
|
|
|
2006-10-17 07:09:25 +00:00
|
|
|
config SGI_IOC4
|
|
|
|
tristate "SGI IOC4 Base IO support"
|
2006-10-24 10:16:29 +00:00
|
|
|
depends on PCI
|
2006-10-17 07:09:25 +00:00
|
|
|
---help---
|
|
|
|
This option enables basic support for the IOC4 chip on certain
|
|
|
|
SGI IO controller cards (IO9, IO10, and PCI-RT). This option
|
|
|
|
does not enable any specific functions on such a card, but provides
|
|
|
|
necessary infrastructure for other drivers to utilize.
|
|
|
|
|
|
|
|
If you have an SGI Altix with an IOC4-based card say Y.
|
|
|
|
Otherwise say N.
|
|
|
|
|
2006-10-04 09:15:38 +00:00
|
|
|
config TIFM_CORE
|
|
|
|
tristate "TI Flash Media interface support (EXPERIMENTAL)"
|
2007-02-09 16:05:42 +00:00
|
|
|
depends on EXPERIMENTAL && PCI
|
2006-10-04 09:15:38 +00:00
|
|
|
help
|
|
|
|
If you want support for Texas Instruments(R) Flash Media adapters
|
|
|
|
you should select this option and then also choose an appropriate
|
|
|
|
host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
|
|
|
|
support', if you have a TI PCI74xx compatible card reader, for
|
|
|
|
example.
|
|
|
|
You will also have to select some flash card format drivers. MMC/SD
|
|
|
|
cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
|
|
|
|
Interface support (MMC_TIFM_SD)'.
|
|
|
|
|
2008-12-01 04:59:07 +00:00
|
|
|
To compile this driver as a module, choose M here: the module will
|
2006-10-04 09:15:38 +00:00
|
|
|
be called tifm_core.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-10-04 09:15:38 +00:00
|
|
|
config TIFM_7XX1
|
|
|
|
tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
|
|
|
|
depends on PCI && TIFM_CORE && EXPERIMENTAL
|
|
|
|
default TIFM_CORE
|
|
|
|
help
|
|
|
|
This option enables support for Texas Instruments(R) PCI74xx and
|
|
|
|
PCI76xx families of Flash Media adapters, found in many laptops.
|
|
|
|
To make actual use of the device, you will have to select some
|
|
|
|
flash card format drivers, as outlined in the TIFM_CORE Help.
|
|
|
|
|
2008-12-01 04:59:07 +00:00
|
|
|
To compile this driver as a module, choose M here: the module will
|
2006-10-04 09:15:38 +00:00
|
|
|
be called tifm_7xx1.
|
|
|
|
|
2008-11-12 21:27:04 +00:00
|
|
|
config ICS932S401
|
|
|
|
tristate "Integrated Circuits ICS932S401"
|
|
|
|
depends on I2C && EXPERIMENTAL
|
|
|
|
help
|
|
|
|
If you say yes here you get support for the Integrated Circuits
|
|
|
|
ICS932S401 clock control chips.
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
will be called ics932s401.
|
|
|
|
|
2007-10-17 06:26:11 +00:00
|
|
|
config ATMEL_SSC
|
|
|
|
tristate "Device driver for Atmel SSC peripheral"
|
|
|
|
depends on AVR32 || ARCH_AT91
|
|
|
|
---help---
|
2009-01-26 10:12:25 +00:00
|
|
|
This option enables device driver support for Atmel Synchronized
|
2007-10-17 06:26:11 +00:00
|
|
|
Serial Communication peripheral (SSC).
|
|
|
|
|
|
|
|
The SSC peripheral supports a wide variety of serial frame based
|
|
|
|
communications, i.e. I2S, SPI, etc.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2008-02-03 21:40:56 +00:00
|
|
|
config ENCLOSURE_SERVICES
|
|
|
|
tristate "Enclosure Services"
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Provides support for intelligent enclosures (bays which
|
|
|
|
contain storage devices). You also need either a host
|
|
|
|
driver (SCSI/ATA) which supports enclosures
|
|
|
|
or a SCSI enclosure device (SES) to use these services.
|
|
|
|
|
2008-04-22 19:46:56 +00:00
|
|
|
config SGI_XP
|
|
|
|
tristate "Support communication between SGI SSIs"
|
2008-08-01 19:19:08 +00:00
|
|
|
depends on NET
|
2009-01-20 03:36:04 +00:00
|
|
|
depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
|
2008-04-22 19:46:56 +00:00
|
|
|
select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
|
|
|
|
select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
|
2009-04-02 23:59:13 +00:00
|
|
|
select SGI_GRU if X86_64 && SMP
|
2008-04-22 19:46:56 +00:00
|
|
|
---help---
|
|
|
|
An SGI machine can be divided into multiple Single System
|
|
|
|
Images which act independently of each other and have
|
|
|
|
hardware based memory protection from the others. Enabling
|
|
|
|
this feature will allow for direct communication between SSIs
|
|
|
|
based on a network adapter and DMA messaging.
|
|
|
|
|
2009-12-15 02:00:37 +00:00
|
|
|
config CS5535_MFGPT
|
|
|
|
tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
|
2009-12-15 02:00:41 +00:00
|
|
|
depends on PCI
|
2009-12-15 02:00:37 +00:00
|
|
|
depends on X86
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
This driver provides access to MFGPT functionality for other
|
|
|
|
drivers that need timers. MFGPTs are available in the CS5535 and
|
|
|
|
CS5536 companion chips that are found in AMD Geode and several
|
|
|
|
other platforms. They have a better resolution and max interval
|
|
|
|
than the generic PIT, and are suitable for use as high-res timers.
|
|
|
|
You probably don't want to enable this manually; other drivers that
|
|
|
|
make use of it should enable it.
|
|
|
|
|
|
|
|
config CS5535_MFGPT_DEFAULT_IRQ
|
|
|
|
int
|
2009-12-17 23:27:05 +00:00
|
|
|
depends on CS5535_MFGPT
|
2009-12-15 02:00:37 +00:00
|
|
|
default 7
|
|
|
|
help
|
|
|
|
MFGPTs on the CS5535 require an interrupt. The selected IRQ
|
|
|
|
can be overridden as a module option as well as by driver that
|
|
|
|
use the cs5535_mfgpt_ API; however, different architectures might
|
|
|
|
want to use a different IRQ by default. This is here for
|
|
|
|
architectures to set as necessary.
|
|
|
|
|
2010-03-05 21:42:35 +00:00
|
|
|
config CS5535_CLOCK_EVENT_SRC
|
|
|
|
tristate "CS5535/CS5536 high-res timer (MFGPT) events"
|
2010-07-14 00:56:20 +00:00
|
|
|
depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
|
2010-03-05 21:42:35 +00:00
|
|
|
help
|
|
|
|
This driver provides a clock event source based on the MFGPT
|
|
|
|
timer(s) in the CS5535 and CS5536 companion chips.
|
|
|
|
MFGPTs have a better resolution and max interval than the
|
|
|
|
generic PIT, and are suitable for use as high-res timers.
|
|
|
|
|
2008-07-02 15:38:53 +00:00
|
|
|
config HP_ILO
|
2010-10-15 16:14:34 +00:00
|
|
|
tristate "Channel interface driver for the HP iLO processor"
|
2008-07-25 08:45:52 +00:00
|
|
|
depends on PCI
|
2008-07-02 15:38:53 +00:00
|
|
|
default n
|
|
|
|
help
|
|
|
|
The channel interface driver allows applications to communicate
|
2010-10-15 16:14:34 +00:00
|
|
|
with iLO management processors present on HP ProLiant servers.
|
|
|
|
Upon loading, the driver creates /dev/hpilo/dXccbN files, which
|
|
|
|
can be used to gather data from the management processor, via
|
|
|
|
read and write system calls.
|
2008-07-02 15:38:53 +00:00
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
module will be called hpilo.
|
|
|
|
|
2008-07-30 05:34:01 +00:00
|
|
|
config SGI_GRU
|
|
|
|
tristate "SGI GRU driver"
|
2009-04-02 23:59:13 +00:00
|
|
|
depends on X86_UV && SMP
|
2008-07-30 05:34:01 +00:00
|
|
|
default n
|
|
|
|
select MMU_NOTIFIER
|
|
|
|
---help---
|
|
|
|
The GRU is a hardware resource located in the system chipset. The GRU
|
|
|
|
contains memory that can be mmapped into the user address space. This memory is
|
|
|
|
used to communicate with the GRU to perform functions such as load/store,
|
|
|
|
scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
|
|
|
|
instructions using user virtual addresses. GRU instructions (ex., bcopy) use
|
|
|
|
user virtual addresses for operands.
|
|
|
|
|
|
|
|
If you are not running on a SGI UV system, say N.
|
|
|
|
|
|
|
|
config SGI_GRU_DEBUG
|
|
|
|
bool "SGI GRU driver debug"
|
|
|
|
depends on SGI_GRU
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
This option enables addition debugging code for the SGI GRU driver. If
|
|
|
|
you are unsure, say N.
|
|
|
|
|
2010-10-26 21:22:41 +00:00
|
|
|
config APDS9802ALS
|
|
|
|
tristate "Medfield Avago APDS9802 ALS Sensor module"
|
|
|
|
depends on I2C
|
|
|
|
help
|
|
|
|
If you say yes here you get support for the ALS APDS9802 ambient
|
|
|
|
light sensor.
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
will be called apds9802als.
|
|
|
|
|
2009-03-31 22:23:53 +00:00
|
|
|
config ISL29003
|
|
|
|
tristate "Intersil ISL29003 ambient light sensor"
|
|
|
|
depends on I2C && SYSFS
|
|
|
|
help
|
|
|
|
If you say yes here you get support for the Intersil ISL29003
|
|
|
|
ambient light sensor.
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
will be called isl29003.
|
|
|
|
|
2010-10-26 21:22:40 +00:00
|
|
|
config ISL29020
|
|
|
|
tristate "Intersil ISL29020 ambient light sensor"
|
|
|
|
depends on I2C
|
|
|
|
help
|
|
|
|
If you say yes here you get support for the Intersil ISL29020
|
|
|
|
ambient light sensor.
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
will be called isl29020.
|
|
|
|
|
2010-03-13 19:56:54 +00:00
|
|
|
config SENSORS_TSL2550
|
|
|
|
tristate "Taos TSL2550 ambient light sensor"
|
|
|
|
depends on I2C && SYSFS
|
|
|
|
help
|
|
|
|
If you say yes here you get support for the Taos TSL2550
|
|
|
|
ambient light sensor.
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
will be called tsl2550.
|
|
|
|
|
2010-08-10 00:20:25 +00:00
|
|
|
config SENSORS_BH1780
|
|
|
|
tristate "ROHM BH1780GLI ambient light sensor"
|
|
|
|
depends on I2C && SYSFS
|
|
|
|
help
|
|
|
|
If you say yes here you get support for the ROHM BH1780GLI
|
|
|
|
ambient light sensor.
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
will be called bh1780gli.
|
|
|
|
|
2010-10-26 21:22:37 +00:00
|
|
|
config SENSORS_BH1770
|
|
|
|
tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
|
|
|
|
depends on I2C
|
|
|
|
---help---
|
|
|
|
Say Y here if you want to build a driver for BH1770GLC (ROHM) or
|
|
|
|
SFH7770 (Osram) combined ambient light and proximity sensor chip.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
module will be called bh1770glc. If unsure, say N here.
|
|
|
|
|
2010-10-26 21:22:38 +00:00
|
|
|
config SENSORS_APDS990X
|
|
|
|
tristate "APDS990X combined als and proximity sensors"
|
|
|
|
depends on I2C
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
Say Y here if you want to build a driver for Avago APDS990x
|
|
|
|
combined ambient light and proximity sensor chip.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
module will be called apds990x. If unsure, say N here.
|
|
|
|
|
2010-08-10 00:21:05 +00:00
|
|
|
config HMC6352
|
|
|
|
tristate "Honeywell HMC6352 compass"
|
|
|
|
depends on I2C
|
|
|
|
help
|
|
|
|
This driver provides support for the Honeywell HMC6352 compass,
|
|
|
|
providing configuration and heading data via sysfs.
|
|
|
|
|
2009-07-29 21:41:06 +00:00
|
|
|
config EP93XX_PWM
|
|
|
|
tristate "EP93xx PWM support"
|
|
|
|
depends on ARCH_EP93XX
|
|
|
|
help
|
|
|
|
This option enables device driver support for the PWM channels
|
|
|
|
on the Cirrus EP93xx processors. The EP9307 chip only has one
|
|
|
|
PWM channel all the others have two, the second channel is an
|
|
|
|
alternate function of the EGPIO14 pin. A sysfs interface is
|
|
|
|
provided to control the PWM channels.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
be called ep93xx_pwm.
|
|
|
|
|
2009-12-06 16:06:16 +00:00
|
|
|
config DS1682
|
|
|
|
tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
|
|
|
|
depends on I2C && EXPERIMENTAL
|
|
|
|
help
|
|
|
|
If you say yes here you get support for Dallas Semiconductor
|
|
|
|
DS1682 Total Elapsed Time Recorder.
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
will be called ds1682.
|
|
|
|
|
2011-03-22 23:33:58 +00:00
|
|
|
config SPEAR13XX_PCIE_GADGET
|
|
|
|
bool "PCIe gadget support for SPEAr13XX platform"
|
|
|
|
depends on ARCH_SPEAR13XX
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
This option enables gadget support for PCIe controller. If
|
|
|
|
board file defines any controller as PCIe endpoint then a sysfs
|
|
|
|
entry will be created for that controller. User can use these
|
|
|
|
sysfs node to configure PCIe EP as per his requirements.
|
|
|
|
|
2009-12-15 02:00:17 +00:00
|
|
|
config TI_DAC7512
|
|
|
|
tristate "Texas Instruments DAC7512"
|
|
|
|
depends on SPI && SYSFS
|
|
|
|
help
|
|
|
|
If you say yes here you get support for the Texas Instruments
|
|
|
|
DAC7512 16-bit digital-to-analog converter.
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
2010-11-09 22:20:26 +00:00
|
|
|
will be called ti_dac7512.
|
2009-12-15 02:00:17 +00:00
|
|
|
|
2010-04-23 17:18:08 +00:00
|
|
|
config VMWARE_BALLOON
|
|
|
|
tristate "VMware Balloon Driver"
|
|
|
|
depends on X86
|
|
|
|
help
|
|
|
|
This is VMware physical memory management driver which acts
|
|
|
|
like a "balloon" that can be inflated to reclaim physical pages
|
|
|
|
by reserving them in the guest and invalidating them in the
|
|
|
|
monitor, freeing up the underlying machine pages so they can
|
|
|
|
be allocated to other guests. The balloon can also be deflated
|
|
|
|
to allow the guest to use more physical memory.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
2010-09-22 20:04:57 +00:00
|
|
|
module will be called vmw_balloon.
|
2010-04-23 17:18:08 +00:00
|
|
|
|
2010-07-17 11:33:48 +00:00
|
|
|
config ARM_CHARLCD
|
|
|
|
bool "ARM Ltd. Character LCD Driver"
|
|
|
|
depends on PLAT_VERSATILE
|
|
|
|
help
|
|
|
|
This is a driver for the character LCD found on the ARM Ltd.
|
|
|
|
Versatile and RealView Platform Baseboards. It doesn't do
|
|
|
|
very much more than display the text "ARM Linux" on the first
|
|
|
|
line and the Linux version on the second line, but that's
|
|
|
|
still useful.
|
|
|
|
|
2010-08-10 00:20:28 +00:00
|
|
|
config BMP085
|
|
|
|
tristate "BMP085 digital pressure sensor"
|
|
|
|
depends on I2C && SYSFS
|
|
|
|
help
|
|
|
|
If you say yes here you get support for the Bosch Sensortec
|
2010-08-23 09:20:34 +00:00
|
|
|
BMP085 digital pressure sensor.
|
2010-08-10 00:20:28 +00:00
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
module will be called bmp085.
|
|
|
|
|
2010-09-01 12:16:30 +00:00
|
|
|
config PCH_PHUB
|
2011-05-12 04:12:36 +00:00
|
|
|
tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223) PHUB"
|
2010-09-01 12:16:30 +00:00
|
|
|
depends on PCI
|
|
|
|
help
|
|
|
|
This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
|
|
|
|
Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
|
|
|
|
processor. The Topcliff has MAC address and Option ROM data in SROM.
|
|
|
|
This driver can access MAC address and Option ROM data in SROM.
|
|
|
|
|
2011-05-12 04:12:36 +00:00
|
|
|
This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
|
|
|
|
Output Hub), ML7213 and ML7223.
|
|
|
|
ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
|
|
|
|
for MP(Media Phone) use.
|
|
|
|
ML7213/ML7223 is companion chip for Intel Atom E6xx series.
|
|
|
|
ML7213/ML7223 is completely compatible for Intel EG20T PCH.
|
2010-12-22 12:04:11 +00:00
|
|
|
|
2010-09-01 12:16:30 +00:00
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
be called pch_phub.
|
|
|
|
|
2008-11-12 21:27:12 +00:00
|
|
|
source "drivers/misc/c2port/Kconfig"
|
2009-01-26 20:19:53 +00:00
|
|
|
source "drivers/misc/eeprom/Kconfig"
|
2009-05-22 18:33:59 +00:00
|
|
|
source "drivers/misc/cb710/Kconfig"
|
2009-10-17 09:09:34 +00:00
|
|
|
source "drivers/misc/iwmc3200top/Kconfig"
|
2010-10-06 16:18:15 +00:00
|
|
|
source "drivers/misc/ti-st/Kconfig"
|
2011-03-21 16:59:36 +00:00
|
|
|
source "drivers/misc/lis3lv02d/Kconfig"
|
2011-02-11 13:34:29 +00:00
|
|
|
source "drivers/misc/carma/Kconfig"
|
2008-11-12 21:27:12 +00:00
|
|
|
|
2007-07-16 06:40:15 +00:00
|
|
|
endif # MISC_DEVICES
|