2005-04-17 06:20:36 +08:00
|
|
|
#
|
|
|
|
|
# Misc strange devices
|
|
|
|
|
#
|
|
|
|
|
|
2012-01-24 12:11:25 +08:00
|
|
|
menu "Misc devices"
|
|
|
|
|
|
2011-03-22 00:59:36 +08:00
|
|
|
config SENSORS_LIS3LV02D
|
|
|
|
|
tristate
|
|
|
|
|
depends on INPUT
|
|
|
|
|
select INPUT_POLLDEV
|
|
|
|
|
default n
|
|
|
|
|
|
2009-12-15 10:00:15 +08: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-25 05:33:14 +08:00
|
|
|
tristate "Analog Devices Digital Potentiometers"
|
|
|
|
|
depends on (I2C || SPI) && SYSFS
|
2009-12-15 10:00:15 +08: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-25 05:33:14 +08: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-25 05:33:15 +08:00
|
|
|
AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
|
2010-05-25 05:33:15 +08:00
|
|
|
AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
|
2010-10-27 05:22:36 +08:00
|
|
|
ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
|
|
|
|
|
AD5271, AD5272, AD5274
|
2009-12-15 10:00:15 +08: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-25 05:33:14 +08: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-23 09:23:23 +08:00
|
|
|
config ATMEL_TCLIB
|
|
|
|
|
bool "Atmel AT32/AT91 Timer/Counter Library"
|
2018-01-19 03:55:34 +08:00
|
|
|
depends on ARCH_AT91
|
2008-02-23 09:23:23 +08:00
|
|
|
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 09:28:37 +08:00
|
|
|
config ATMEL_TCB_CLKSRC
|
|
|
|
|
bool "TC Block Clocksource"
|
2010-07-14 08:56:20 +08:00
|
|
|
depends on ATMEL_TCLIB
|
2008-02-23 09:28:37 +08: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
|
|
|
|
|
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.
|
|
|
|
|
|
2013-03-21 07:21:21 +08:00
|
|
|
config DUMMY_IRQ
|
|
|
|
|
tristate "Dummy IRQ handler"
|
|
|
|
|
default n
|
|
|
|
|
---help---
|
|
|
|
|
This module accepts a single 'irq' parameter, which it should register for.
|
|
|
|
|
The sole purpose of this module is to help with debugging of systems on
|
|
|
|
|
which spurious IRQs would happen on disabled IRQ vector.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config IBM_ASM
|
|
|
|
|
tristate "Device driver for IBM RSA service processor"
|
2012-09-18 23:14:53 +08:00
|
|
|
depends on X86 && PCI && INPUT
|
2016-01-21 06:58:21 +08:00
|
|
|
depends on SERIAL_8250 || SERIAL_8250=n
|
2005-04-17 06:20:36 +08: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 17:15:38 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
WARNING: This software may not be supported or function
|
|
|
|
|
correctly on your IBM server. Please consult the IBM ServerProven
|
2010-10-18 17:03:14 +08: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-17 06:20:36 +08:00
|
|
|
for your IBM server.
|
|
|
|
|
|
2018-04-26 05:32:57 +08:00
|
|
|
config IBMVMC
|
|
|
|
|
tristate "IBM Virtual Management Channel support"
|
|
|
|
|
depends on PPC_PSERIES
|
|
|
|
|
help
|
|
|
|
|
This is the IBM POWER Virtual Management Channel
|
|
|
|
|
|
|
|
|
|
This driver is to be used for the POWER Virtual
|
|
|
|
|
Management Channel virtual adapter on the PowerVM
|
|
|
|
|
platform. It provides both request/response and
|
|
|
|
|
async message support through the /dev/ibmvmc node.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called ibmvmc.
|
|
|
|
|
|
2007-05-08 15:31:45 +08:00
|
|
|
config PHANTOM
|
2008-07-25 16:48:23 +08:00
|
|
|
tristate "Sensable PHANToM (PCI)"
|
2007-05-08 15:31:45 +08:00
|
|
|
depends on PCI
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to build a driver for Sensable PHANToM device.
|
|
|
|
|
|
2008-07-25 16:48:23 +08:00
|
|
|
This driver is only for PCI PHANToMs.
|
|
|
|
|
|
2007-05-08 15:31:45 +08:00
|
|
|
If you choose to build module, its name will be phantom. If unsure,
|
|
|
|
|
say N here.
|
|
|
|
|
|
2011-05-07 07:56:49 +08:00
|
|
|
config INTEL_MID_PTI
|
|
|
|
|
tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
|
2013-05-22 16:56:24 +08:00
|
|
|
depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
|
2011-05-07 07:56:49 +08:00
|
|
|
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 15:09:25 +08:00
|
|
|
config SGI_IOC4
|
|
|
|
|
tristate "SGI IOC4 Base IO support"
|
2006-10-24 18:16:29 +08:00
|
|
|
depends on PCI
|
2006-10-17 15:09:25 +08: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 17:15:38 +08:00
|
|
|
config TIFM_CORE
|
2012-09-18 23:14:53 +08:00
|
|
|
tristate "TI Flash Media interface support"
|
|
|
|
|
depends on PCI
|
2006-10-04 17:15:38 +08: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 12:59:07 +08:00
|
|
|
To compile this driver as a module, choose M here: the module will
|
2006-10-04 17:15:38 +08:00
|
|
|
be called tifm_core.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2006-10-04 17:15:38 +08:00
|
|
|
config TIFM_7XX1
|
2012-09-18 23:14:53 +08:00
|
|
|
tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
|
|
|
|
|
depends on PCI && TIFM_CORE
|
2006-10-04 17:15:38 +08:00
|
|
|
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 12:59:07 +08:00
|
|
|
To compile this driver as a module, choose M here: the module will
|
2006-10-04 17:15:38 +08:00
|
|
|
be called tifm_7xx1.
|
|
|
|
|
|
2008-11-13 05:27:04 +08:00
|
|
|
config ICS932S401
|
|
|
|
|
tristate "Integrated Circuits ICS932S401"
|
2012-09-18 23:14:53 +08:00
|
|
|
depends on I2C
|
2008-11-13 05:27:04 +08:00
|
|
|
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 14:26:11 +08:00
|
|
|
config ATMEL_SSC
|
|
|
|
|
tristate "Device driver for Atmel SSC peripheral"
|
2018-01-19 03:55:34 +08:00
|
|
|
depends on HAS_IOMEM && (ARCH_AT91 || COMPILE_TEST)
|
2007-10-17 14:26:11 +08:00
|
|
|
---help---
|
2009-01-26 18:12:25 +08:00
|
|
|
This option enables device driver support for Atmel Synchronized
|
2007-10-17 14:26:11 +08: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-04 05:40:56 +08: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-23 03:46:56 +08:00
|
|
|
config SGI_XP
|
|
|
|
|
tristate "Support communication between SGI SSIs"
|
2008-08-02 03:19:08 +08:00
|
|
|
depends on NET
|
2009-01-20 11:36:04 +08:00
|
|
|
depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
|
2008-04-23 03:46:56 +08:00
|
|
|
select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
|
|
|
|
|
select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
|
2009-04-03 07:59:13 +08:00
|
|
|
select SGI_GRU if X86_64 && SMP
|
2008-04-23 03:46:56 +08: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 10:00:37 +08:00
|
|
|
config CS5535_MFGPT
|
|
|
|
|
tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
|
2014-03-08 05:06:29 +08:00
|
|
|
depends on MFD_CS5535
|
2009-12-15 10:00:37 +08:00
|
|
|
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-18 07:27:05 +08:00
|
|
|
depends on CS5535_MFGPT
|
2009-12-15 10:00:37 +08: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-06 05:42:35 +08:00
|
|
|
config CS5535_CLOCK_EVENT_SRC
|
|
|
|
|
tristate "CS5535/CS5536 high-res timer (MFGPT) events"
|
2010-07-14 08:56:20 +08:00
|
|
|
depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
|
2010-03-06 05:42:35 +08: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 23:38:53 +08:00
|
|
|
config HP_ILO
|
2010-10-16 00:14:34 +08:00
|
|
|
tristate "Channel interface driver for the HP iLO processor"
|
2008-07-25 16:45:52 +08:00
|
|
|
depends on PCI
|
2008-07-02 23:38:53 +08:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
The channel interface driver allows applications to communicate
|
2010-10-16 00:14:34 +08: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 23:38:53 +08:00
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called hpilo.
|
|
|
|
|
|
2015-07-17 07:55:32 +08:00
|
|
|
config QCOM_COINCELL
|
|
|
|
|
tristate "Qualcomm coincell charger support"
|
|
|
|
|
depends on MFD_SPMI_PMIC || COMPILE_TEST
|
|
|
|
|
help
|
|
|
|
|
This driver supports the coincell block found inside of
|
|
|
|
|
Qualcomm PMICs. The coincell charger provides a means to
|
|
|
|
|
charge a coincell battery or backup capacitor which is used
|
|
|
|
|
to maintain PMIC register and RTC state in the absence of
|
|
|
|
|
external power.
|
|
|
|
|
|
2008-07-30 13:34:01 +08:00
|
|
|
config SGI_GRU
|
|
|
|
|
tristate "SGI GRU driver"
|
2009-04-03 07:59:13 +08:00
|
|
|
depends on X86_UV && SMP
|
2008-07-30 13:34:01 +08: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---
|
2014-04-15 00:55:49 +08:00
|
|
|
This option enables additional debugging code for the SGI GRU driver.
|
|
|
|
|
If you are unsure, say N.
|
2008-07-30 13:34:01 +08:00
|
|
|
|
2010-10-27 05:22:41 +08: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-04-01 06:23:53 +08: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-27 05:22:40 +08: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-14 03:56:54 +08: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-10-27 05:22:37 +08: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-27 05:22:38 +08: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 08:21:05 +08: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-12-07 00:06:16 +08:00
|
|
|
config DS1682
|
|
|
|
|
tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
|
2012-09-18 23:14:53 +08:00
|
|
|
depends on I2C
|
2009-12-07 00:06:16 +08:00
|
|
|
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-23 07:33:58 +08:00
|
|
|
config SPEAR13XX_PCIE_GADGET
|
|
|
|
|
bool "PCIe gadget support for SPEAr13XX platform"
|
2013-04-24 00:30:45 +08:00
|
|
|
depends on ARCH_SPEAR13XX && BROKEN
|
2011-03-23 07:33:58 +08:00
|
|
|
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.
|
|
|
|
|
|
2010-04-24 01:18:08 +08:00
|
|
|
config VMWARE_BALLOON
|
|
|
|
|
tristate "VMware Balloon Driver"
|
2015-08-07 06:18:01 +08:00
|
|
|
depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
|
2010-04-24 01:18:08 +08:00
|
|
|
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-23 04:04:57 +08:00
|
|
|
module will be called vmw_balloon.
|
2010-04-24 01:18:08 +08:00
|
|
|
|
2010-09-01 20:16:30 +08:00
|
|
|
config PCH_PHUB
|
2011-10-28 08:33:13 +08:00
|
|
|
tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
|
2013-06-05 00:46:26 +08:00
|
|
|
select GENERIC_NET_UTILS
|
2015-12-01 00:21:35 +08:00
|
|
|
depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
|
2010-09-01 20:16:30 +08:00
|
|
|
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-10-28 08:33:13 +08:00
|
|
|
This driver also can be used for LAPIS Semiconductor's IOH,
|
|
|
|
|
ML7213/ML7223/ML7831.
|
|
|
|
|
ML7213 which is for IVI(In-Vehicle Infotainment) use.
|
|
|
|
|
ML7223 IOH is for MP(Media Phone) use.
|
|
|
|
|
ML7831 IOH is for general purpose use.
|
|
|
|
|
ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
|
|
|
|
|
ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
|
2010-12-22 20:04:11 +08:00
|
|
|
|
2010-09-01 20:16:30 +08:00
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called pch_phub.
|
|
|
|
|
|
2011-07-26 08:13:07 +08:00
|
|
|
config USB_SWITCH_FSA9480
|
|
|
|
|
tristate "FSA9480 USB Switch"
|
|
|
|
|
depends on I2C
|
|
|
|
|
help
|
|
|
|
|
The FSA9480 is a USB port accessory detector and switch.
|
|
|
|
|
The FSA9480 is fully controlled using I2C and enables USB data,
|
|
|
|
|
stereo and mono audio, video, microphone and UART data to use
|
|
|
|
|
a common connector port.
|
|
|
|
|
|
2012-12-07 16:06:59 +08:00
|
|
|
config LATTICE_ECP3_CONFIG
|
|
|
|
|
tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
|
|
|
|
|
depends on SPI && SYSFS
|
|
|
|
|
select FW_LOADER
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option enables support for bitstream configuration (programming
|
|
|
|
|
or loading) of the Lattice ECP3 FPGA family via SPI.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2013-04-30 07:17:12 +08:00
|
|
|
config SRAM
|
|
|
|
|
bool "Generic on-chip SRAM driver"
|
|
|
|
|
depends on HAS_IOMEM
|
|
|
|
|
select GENERIC_ALLOCATOR
|
2017-01-13 04:52:20 +08:00
|
|
|
select SRAM_EXEC if ARM
|
2013-04-30 07:17:12 +08:00
|
|
|
help
|
|
|
|
|
This driver allows you to declare a memory region to be managed by
|
|
|
|
|
the genalloc API. It is supposed to be used for small on-chip SRAM
|
|
|
|
|
areas found on many SoCs.
|
|
|
|
|
|
2017-01-13 04:52:20 +08:00
|
|
|
config SRAM_EXEC
|
|
|
|
|
bool
|
|
|
|
|
|
2014-04-23 17:49:31 +08:00
|
|
|
config VEXPRESS_SYSCFG
|
|
|
|
|
bool "Versatile Express System Configuration driver"
|
|
|
|
|
depends on VEXPRESS_CONFIG
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
ARM Ltd. Versatile Express uses specialised platform configuration
|
|
|
|
|
bus. System Configuration interface is one of the possible means
|
|
|
|
|
of generating transactions on this bus.
|
2017-02-01 08:02:16 +08:00
|
|
|
|
drivers/misc: Add Aspeed LPC control driver
In order to manage server systems, there is typically another processor
known as a BMC (Baseboard Management Controller) which is responsible
for powering the server and other various elements, sometimes fans,
often the system flash.
The Aspeed BMC family which is what is used on OpenPOWER machines and a
number of x86 as well is typically connected to the host via an LPC
(Low Pin Count) bus (among others).
The LPC bus is an ISA bus on steroids. It's generally used by the
BMC chip to provide the host with access to the system flash (via MEM/FW
cycles) that contains the BIOS or other host firmware along with a
number of SuperIO-style IOs (via IO space) such as UARTs, IPMI
controllers.
On the BMC chip side, this is all configured via a bunch of registers
whose content is related to a given policy of what devices are exposed
at a per system level, which is system/vendor specific, so we don't want
to bolt that into the BMC kernel. This started with a need to provide
something nicer than /dev/mem for user space to configure these things.
One important aspect of the configuration is how the MEM/FW space is
exposed to the host (ie, the x86 or POWER). Some registers in that
bridge can define a window remapping all or portion of the LPC MEM/FW
space to a portion of the BMC internal bus, with no specific limits
imposed in HW.
I think it makes sense to ensure that this window is configured by a
kernel driver that can apply some serious sanity checks on what it is
configured to map.
In practice, user space wants to control this by flipping the mapping
between essentially two types of portions of the BMC address space:
- The flash space. This is a region of the BMC MMIO space that
more/less directly maps the system flash (at least for reads, writes
are somewhat more complicated).
- One (or more) reserved area(s) of the BMC physical memory.
The latter is needed for a number of things, such as avoiding letting
the host manipulate the innards of the BMC flash controller via some
evil backdoor, we want to do flash updates by routing the window to a
portion of memory (under control of a mailbox protocol via some
separate set of registers) which the host can use to write new data in
bulk and then request the BMC to flash it. There are other uses, such
as allowing the host to boot from an in-memory flash image rather than
the one in flash (very handy for continuous integration and test, the
BMC can just download new images).
It is important to note that due to the way the Aspeed chip lets the
kernel configure the mapping between host LPC addresses and BMC ram
addresses the offset within the window must be a multiple of size.
Not doing so will fragment the accessible space rather than simply
moving 'zero' upwards. This is caused by the nature of HICR8 being a
mask and the way host LPC addresses are translated.
Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
Reviewed-by: Joel Stanley <joel@jms.id.au>
Reviewed-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-02-17 11:28:49 +08:00
|
|
|
config ASPEED_LPC_CTRL
|
|
|
|
|
depends on (ARCH_ASPEED || COMPILE_TEST) && REGMAP && MFD_SYSCON
|
|
|
|
|
tristate "Aspeed ast2400/2500 HOST LPC to BMC bridge control"
|
|
|
|
|
---help---
|
|
|
|
|
Control Aspeed ast2400/2500 HOST LPC to BMC mappings through
|
|
|
|
|
ioctl()s, the driver also provides a read/write interface to a BMC ram
|
|
|
|
|
region where the host LPC read/write region can be buffered.
|
|
|
|
|
|
2017-06-03 05:53:22 +08:00
|
|
|
config ASPEED_LPC_SNOOP
|
|
|
|
|
tristate "Aspeed ast2500 HOST LPC snoop support"
|
|
|
|
|
depends on (ARCH_ASPEED || COMPILE_TEST) && REGMAP && MFD_SYSCON
|
|
|
|
|
help
|
|
|
|
|
Provides a driver to control the LPC snoop interface which
|
|
|
|
|
allows the BMC to listen on and save the data written by
|
|
|
|
|
the host to an arbitrary LPC I/O port.
|
|
|
|
|
|
2017-03-27 17:45:14 +08:00
|
|
|
config PCI_ENDPOINT_TEST
|
|
|
|
|
depends on PCI
|
2017-05-09 19:52:02 +08:00
|
|
|
select CRC32
|
2017-03-27 17:45:14 +08:00
|
|
|
tristate "PCI Endpoint Test driver"
|
|
|
|
|
---help---
|
|
|
|
|
Enable this configuration option to enable the host side test driver
|
|
|
|
|
for PCI Endpoint.
|
|
|
|
|
|
2017-11-29 17:08:03 +08:00
|
|
|
config MISC_RTSX
|
|
|
|
|
tristate
|
|
|
|
|
default MISC_RTSX_PCI || MISC_RTSX_USB
|
|
|
|
|
|
2018-11-06 22:57:12 +08:00
|
|
|
config PVPANIC
|
|
|
|
|
tristate "pvpanic device support"
|
2018-11-16 19:13:26 +08:00
|
|
|
depends on HAS_IOMEM && (ACPI || OF)
|
2018-11-06 22:57:12 +08:00
|
|
|
help
|
|
|
|
|
This driver provides support for the pvpanic device. pvpanic is
|
|
|
|
|
a paravirtualized device provided by QEMU; it lets a virtual machine
|
|
|
|
|
(guest) communicate panic events to the host.
|
|
|
|
|
|
2008-11-13 05:27:12 +08:00
|
|
|
source "drivers/misc/c2port/Kconfig"
|
2009-01-27 04:19:53 +08:00
|
|
|
source "drivers/misc/eeprom/Kconfig"
|
2009-05-23 02:33:59 +08:00
|
|
|
source "drivers/misc/cb710/Kconfig"
|
2010-10-07 00:18:15 +08:00
|
|
|
source "drivers/misc/ti-st/Kconfig"
|
2011-03-22 00:59:36 +08:00
|
|
|
source "drivers/misc/lis3lv02d/Kconfig"
|
2011-09-23 22:17:41 +08:00
|
|
|
source "drivers/misc/altera-stapl/Kconfig"
|
2012-05-02 06:23:38 +08:00
|
|
|
source "drivers/misc/mei/Kconfig"
|
2013-01-09 07:55:59 +08:00
|
|
|
source "drivers/misc/vmw_vmci/Kconfig"
|
2013-09-06 07:41:31 +08:00
|
|
|
source "drivers/misc/mic/Kconfig"
|
2013-12-09 20:30:44 +08:00
|
|
|
source "drivers/misc/genwqe/Kconfig"
|
2014-03-01 06:08:42 +08:00
|
|
|
source "drivers/misc/echo/Kconfig"
|
2014-10-08 16:55:01 +08:00
|
|
|
source "drivers/misc/cxl/Kconfig"
|
2018-01-23 19:31:45 +08:00
|
|
|
source "drivers/misc/ocxl/Kconfig"
|
2017-11-29 17:08:03 +08:00
|
|
|
source "drivers/misc/cardreader/Kconfig"
|
2012-01-24 12:11:25 +08:00
|
|
|
endmenu
|
