#
# Sensor device configuration
#
menu "I2C Hardware Bus support"
depends on [31mCONFIG_HAS_IOMEM[0m
comment "PC SMBus host controller drivers"
depends on [31mCONFIG_PCI[0m
config [31mCONFIG_I2C_ALI1535[0m
tristate "ALI 1535"
depends on [31mCONFIG_PCI[0m
help
If you say yes to this option, support will be included for the SMB
Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
controller is part of the 7101 device, which is an [31mCONFIG_ACPI[0m-compliant
Power Management Unit (PMU).
This driver can also be built as a module. If so, the module
will be called i2c-ali1535.
config [31mCONFIG_I2C_ALI1563[0m
tristate "ALI 1563"
depends on [31mCONFIG_PCI[0m
help
If you say yes to this option, support will be included for the SMB
Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
controller is part of the 7101 device, which is an [31mCONFIG_ACPI[0m-compliant
Power Management Unit (PMU).
This driver can also be built as a module. If so, the module
will be called i2c-ali1563.
config [31mCONFIG_I2C_ALI15X3[0m
tristate "ALI 15x3"
depends on [31mCONFIG_PCI[0m
help
If you say yes to this option, support will be included for the
Acer Labs Inc. (ALI) M1514 and M1543 motherboard [31mCONFIG_I2C[0m interfaces.
This driver can also be built as a module. If so, the module
will be called i2c-ali15x3.
config [31mCONFIG_I2C_AMD756[0m
tristate "AMD 756/766/768/8111 and nVidia nForce"
depends on [31mCONFIG_PCI[0m
help
If you say yes to this option, support will be included for the AMD
756/766/768 mainboard [31mCONFIG_I2C[0m interfaces. The driver also includes
support for the first (SMBus 1.0) [31mCONFIG_I2C[0m interface of the AMD 8111 and
the nVidia nForce [31mCONFIG_I2C[0m interface.
This driver can also be built as a module. If so, the module
will be called i2c-amd756.
config [31mCONFIG_I2C_AMD756_S4882[0m
tristate "SMBus multiplexing on the Tyan S4882"
depends on [31mCONFIG_I2C_AMD756[0m && [31mCONFIG_X86[0m
help
Enabling this option will add specific SMBus support for the Tyan
S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
over 8 different channels, where the various memory module EEPROMs
and temperature sensors live. Saying yes here will give you access
to these in addition to the trunk.
This driver can also be built as a module. If so, the module
will be called i2c-amd756-s4882.
config [31mCONFIG_I2C_AMD8111[0m
tristate "AMD 8111"
depends on [31mCONFIG_PCI[0m
help
If you say yes to this option, support will be included for the
second (SMBus 2.0) AMD 8111 mainboard [31mCONFIG_I2C[0m interface.
This driver can also be built as a module. If so, the module
will be called i2c-amd8111.
config [31mCONFIG_I2C_HIX5HD2[0m
tristate "Hix5hd2 high-speed I2C driver"
depends on [31mCONFIG_ARCH_HISI[0m || [31mCONFIG_ARCH_HIX5HD2[0m || [31mCONFIG_COMPILE_TEST[0m
help
Say Y here to include support for the high-speed [31mCONFIG_I2C[0m controller
used in HiSilicon hix5hd2 SoCs.
This driver can also be built as a module. If so, the module
will be called i2c-hix5hd2.
config [31mCONFIG_I2C_I801[0m
tristate "Intel 82801 (ICH/PCH)"
depends on [31mCONFIG_PCI[0m
select [31mCONFIG_CHECK_SIGNATURE[0m if [31mCONFIG_X86[0m && [31mCONFIG_DMI[0m
select [31mCONFIG_I2C_SMBUS[0m
help
If you say yes to this option, support will be included for the Intel
801 family of mainboard [31mCONFIG_I2C[0m interfaces. Specifically, the following
versions of the chipset are supported:
82801AA
82801AB
82801BA
82801CA/CAM
82801DB
82801EB/ER (ICH5/ICH5R)
6300ESB
ICH6
ICH7
ESB2
ICH8
ICH9
EP80579 (Tolapai)
ICH10
5/3400 Series (PCH)
6 Series (PCH)
Patsburg (PCH)
DH89xxCC (PCH)
Panther Point (PCH)
Lynx Point (PCH)
Lynx Point-LP (PCH)
Avoton (SOC)
Wellsburg (PCH)
Coleto Creek (PCH)
Wildcat Point (PCH)
Wildcat Point-LP (PCH)
BayTrail (SOC)
Sunrise Point-H (PCH)
Sunrise Point-LP (PCH)
DNV (SOC)
Broxton (SOC)
Lewisburg (PCH)
This driver can also be built as a module. If so, the module
will be called i2c-i801.
config [31mCONFIG_I2C_ISCH[0m
tristate "Intel SCH SMBus 1.0"
depends on [31mCONFIG_PCI[0m
select [31mCONFIG_LPC_SCH[0m
help
Say Y here if you want to use SMBus controller on the Intel SCH
based systems.
This driver can also be built as a module. If so, the module
will be called i2c-isch.
config [31mCONFIG_I2C_ISMT[0m
tristate "Intel iSMT SMBus Controller"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_X86[0m
help
If you say yes to this option, support will be included for the Intel
iSMT SMBus host controller interface.
This driver can also be built as a module. If so, the module will be
called i2c-ismt.
config [31mCONFIG_I2C_PIIX4[0m
tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
depends on [31mCONFIG_PCI[0m
help
If you say yes to this option, support will be included for the Intel
PIIX4 family of mainboard [31mCONFIG_I2C[0m interfaces. Specifically, the following
versions of the chipset are supported (note that Serverworks is part
of Broadcom):
Intel PIIX4
Intel 440MX
ATI IXP200
ATI IXP300
ATI IXP400
ATI SB600
ATI SB700/SP5100
ATI SB800
AMD Hudson-2
AMD ML
AMD CZ
Serverworks OSB4
Serverworks CSB5
Serverworks CSB6
Serverworks HT-1000
Serverworks HT-1100
SMSC Victory66
Some AMD chipsets contain two PIIX4-compatible SMBus
controllers. This driver will attempt to use both controllers
on the SB700/SP5100, if they have been initialized by the BIOS.
This driver can also be built as a module. If so, the module
will be called i2c-piix4.
config [31mCONFIG_I2C_NFORCE2[0m
tristate "Nvidia nForce2, nForce3 and nForce4"
depends on [31mCONFIG_PCI[0m
help
If you say yes to this option, support will be included for the Nvidia
nForce2, nForce3 and nForce4 families of mainboard [31mCONFIG_I2C[0m interfaces.
This driver can also be built as a module. If so, the module
will be called i2c-nforce2.
config [31mCONFIG_I2C_NFORCE2_S4985[0m
tristate "SMBus multiplexing on the Tyan S4985"
depends on [31mCONFIG_I2C_NFORCE2[0m && [31mCONFIG_X86[0m
help
Enabling this option will add specific SMBus support for the Tyan
S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
over 4 different channels, where the various memory module EEPROMs
live. Saying yes here will give you access to these in addition
to the trunk.
This driver can also be built as a module. If so, the module
will be called i2c-nforce2-s4985.
config [31mCONFIG_I2C_SIS5595[0m
tristate "SiS 5595"
depends on [31mCONFIG_PCI[0m
help
If you say yes to this option, support will be included for the
SiS5595 SMBus (a subset of [31mCONFIG_I2C[0m) interface.
This driver can also be built as a module. If so, the module
will be called i2c-sis5595.
config [31mCONFIG_I2C_SIS630[0m
tristate "SiS 630/730/964"
depends on [31mCONFIG_PCI[0m
help
If you say yes to this option, support will be included for the
SiS630, SiS730 and SiS964 SMBus (a subset of [31mCONFIG_I2C[0m) interface.
This driver can also be built as a module. If so, the module
will be called i2c-sis630.
config [31mCONFIG_I2C_SIS96X[0m
tristate "SiS 96x"
depends on [31mCONFIG_PCI[0m
help
If you say yes to this option, support will be included for the SiS
96x SMBus (a subset of [31mCONFIG_I2C[0m) interfaces. Specifically, the following
chipsets are supported:
645/961
645DX/961
645DX/962
648/961
650/961
735
745
This driver can also be built as a module. If so, the module
will be called i2c-sis96x.
config [31mCONFIG_I2C_VIA[0m
tristate "VIA VT82C586B"
depends on [31mCONFIG_PCI[0m
select [31mCONFIG_I2C_ALGOBIT[0m
help
If you say yes to this option, support will be included for the VIA
82C586B [31mCONFIG_I2C[0m interface
This driver can also be built as a module. If so, the module
will be called i2c-via.
config [31mCONFIG_I2C_VIAPRO[0m
tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
depends on [31mCONFIG_PCI[0m
help
If you say yes to this option, support will be included for the VIA
VT82C596 and later SMBus interface. Specifically, the following
chipsets are supported:
VT82C596A/[31mCONFIG_B[0m
VT82C686A/[31mCONFIG_B[0m
VT8231
VT8233/[31mCONFIG_A[0m
VT8235
VT8237R/[31mCONFIG_A[0m/S
VT8251
CX700
VX800/VX820
VX855/VX875
VX900
This driver can also be built as a module. If so, the module
will be called i2c-viapro.
if [31mCONFIG_ACPI[0m
comment "ACPI drivers"
config [31mCONFIG_I2C_SCMI[0m
tristate "SMBus Control Method Interface"
help
This driver supports the SMBus Control Method Interface. It needs the
BIOS to declare [31mCONFIG_ACPI[0m control methods as described in the SMBus Control
Method Interface specification.
To compile this driver as a module, choose [31mCONFIG_M[0m here:
the module will be called i2c-scmi.
endif # [31mCONFIG_ACPI[0m
comment "Mac SMBus host controller drivers"
depends on [31mCONFIG_PPC_CHRP[0m || [31mCONFIG_PPC_PMAC[0m
config [31mCONFIG_I2C_HYDRA[0m
tristate "CHRP Apple Hydra Mac I/O I2C interface"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_PPC_CHRP[0m
select [31mCONFIG_I2C_ALGOBIT[0m
help
This supports the use of the [31mCONFIG_I2C[0m interface in the Apple Hydra Mac
I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
have such a machine.
This support is also available as a module. If so, the module
will be called i2c-hydra.
config [31mCONFIG_I2C_POWERMAC[0m
tristate "Powermac I2C interface"
depends on [31mCONFIG_PPC_PMAC[0m
default y
help
This exposes the various PowerMac i2c interfaces to the linux i2c
layer and to userland. It is used by various drivers on the PowerMac
platform, and should generally be enabled.
This support is also available as a module. If so, the module
will be called i2c-powermac.
comment "I2C system bus drivers (mostly embedded / system-on-chip)"
config [31mCONFIG_I2C_AT91[0m
tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
depends on [31mCONFIG_ARCH_AT91[0m
help
This supports the use of the [31mCONFIG_I2C[0m interface on Atmel AT91
processors.
[31mCONFIG_A[0m serious problem is that there is no documented way to issue
repeated START conditions for more than two messages, as needed
to support combined [31mCONFIG_I2C[0m messages. Use the i2c-gpio driver
unless your system can cope with this limitation.
Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
don't have clock stretching in transmission mode. For that reason,
you can encounter underrun issues causing premature stop sendings if
the latency to fill the transmission register is too long. If you
are facing this situation, use the i2c-gpio driver.
config [31mCONFIG_I2C_AU1550[0m
tristate "Au1550/Au1200/Au1300 SMBus interface"
depends on [31mCONFIG_MIPS_ALCHEMY[0m
help
If you say yes to this option, support will be included for the
Au1550/Au1200/Au1300 SMBus interface.
This driver can also be built as a module. If so, the module
will be called i2c-au1550.
config [31mCONFIG_I2C_AXXIA[0m
tristate "Axxia I2C controller"
depends on [31mCONFIG_ARCH_AXXIA[0m || [31mCONFIG_COMPILE_TEST[0m
default [31mCONFIG_ARCH_AXXIA[0m
help
Say yes if you want to support the [31mCONFIG_I2C[0m bus on Axxia platforms.
Please note that this controller is limited to transfers of maximum
255 bytes in length. Any attempt to to a larger transfer will return
an error.
config [31mCONFIG_I2C_BCM2835[0m
tristate "Broadcom BCM2835 I2C controller"
depends on [31mCONFIG_ARCH_BCM2835[0m
help
If you say yes to this option, support will be included for the
BCM2835 [31mCONFIG_I2C[0m controller.
If you don't know what to do here, say N.
This support is also available as a module. If so, the module
will be called i2c-bcm2835.
config [31mCONFIG_I2C_BCM_IPROC[0m
tristate "Broadcom iProc I2C controller"
depends on [31mCONFIG_ARCH_BCM_IPROC[0m || [31mCONFIG_COMPILE_TEST[0m
default [31mCONFIG_ARCH_BCM_IPROC[0m
help
If you say yes to this option, support will be included for the
Broadcom iProc [31mCONFIG_I2C[0m controller.
If you don't know what to do here, say N.
config [31mCONFIG_I2C_BCM_KONA[0m
tristate "BCM Kona I2C adapter"
depends on [31mCONFIG_ARCH_BCM_MOBILE[0m
default y
help
If you say yes to this option, support will be included for the
[31mCONFIG_I2C[0m interface on the Broadcom Kona family of processors.
If you do not need KONA [31mCONFIG_I2C[0m interface, say N.
config [31mCONFIG_I2C_BRCMSTB[0m
tristate "BRCM Settop I2C controller"
depends on [31mCONFIG_ARCH_BRCMSTB[0m || [31mCONFIG_BMIPS_GENERIC[0m || [31mCONFIG_COMPILE_TEST[0m
default y
help
If you say yes to this option, support will be included for the
[31mCONFIG_I2C[0m interface on the Broadcom Settop SoCs.
If you do not need [31mCONFIG_I2C[0m interface, say N.
config [31mCONFIG_I2C_BLACKFIN_TWI[0m
tristate "Blackfin TWI I2C support"
depends on [31mCONFIG_BLACKFIN[0m
depends on ![31mCONFIG_BF561[0m && ![31mCONFIG_BF531[0m && ![31mCONFIG_BF532[0m && ![31mCONFIG_BF533[0m
help
This is the [31mCONFIG_I2C[0m bus driver for Blackfin on-chip TWI interface.
This driver can also be built as a module. If so, the module
will be called i2c-bfin-twi.
config [31mCONFIG_I2C_BLACKFIN_TWI_CLK_KHZ[0m
int "Blackfin TWI I2C clock (kHz)"
depends on [31mCONFIG_I2C_BLACKFIN_TWI[0m
range 21 400
default 50
help
The unit of the TWI clock is kHz.
config [31mCONFIG_I2C_CADENCE[0m
tristate "Cadence I2C Controller"
depends on [31mCONFIG_ARCH_ZYNQ[0m || [31mCONFIG_ARM64[0m || [31mCONFIG_XTENSA[0m
help
Say yes here to select Cadence [31mCONFIG_I2C[0m Host Controller. This controller is
e.g. used by Xilinx Zynq.
config [31mCONFIG_I2C_CBUS_GPIO[0m
tristate "CBUS I2C driver"
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
help
Support for CBUS access using [31mCONFIG_I2C[0m API. Mostly relevant for Nokia
Internet Tablets (770, N800 and N810).
This driver can also be built as a module. If so, the module
will be called i2c-cbus-gpio.
config [31mCONFIG_I2C_CPM[0m
tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
depends on [31mCONFIG_CPM1[0m || [31mCONFIG_CPM2[0m
help
This supports the use of the [31mCONFIG_I2C[0m interface on Freescale
processors with [31mCONFIG_CPM1[0m or [31mCONFIG_CPM2[0m.
This driver can also be built as a module. If so, the module
will be called i2c-cpm.
config [31mCONFIG_I2C_DAVINCI[0m
tristate "DaVinci I2C driver"
depends on [31mCONFIG_ARCH_DAVINCI[0m || [31mCONFIG_ARCH_KEYSTONE[0m
help
Support for TI DaVinci [31mCONFIG_I2C[0m controller driver.
This driver can also be built as a module. If so, the module
will be called i2c-davinci.
Please note that this driver might be needed to bring up other
devices such as DaVinci NIC.
For details please see http://www.ti.com/davinci
config [31mCONFIG_I2C_DESIGNWARE_CORE[0m
tristate
config [31mCONFIG_I2C_DESIGNWARE_PLATFORM[0m
tristate "Synopsys DesignWare Platform"
select [31mCONFIG_I2C_DESIGNWARE_CORE[0m
depends on ([31mCONFIG_ACPI[0m && [31mCONFIG_COMMON_CLK[0m) || ![31mCONFIG_ACPI[0m
help
If you say yes to this option, support will be included for the
Synopsys DesignWare [31mCONFIG_I2C[0m adapter. Only master mode is supported.
This driver can also be built as a module. If so, the module
will be called i2c-designware-platform.
config [31mCONFIG_I2C_DESIGNWARE_PCI[0m
tristate "Synopsys DesignWare PCI"
depends on [31mCONFIG_PCI[0m
select [31mCONFIG_I2C_DESIGNWARE_CORE[0m
help
If you say yes to this option, support will be included for the
Synopsys DesignWare [31mCONFIG_I2C[0m adapter. Only master mode is supported.
This driver can also be built as a module. If so, the module
will be called i2c-designware-pci.
config [31mCONFIG_I2C_DESIGNWARE_BAYTRAIL[0m
bool "Intel Baytrail I2C semaphore support"
depends on [31mCONFIG_ACPI[0m
depends on ([31mCONFIG_I2C_DESIGNWARE_PLATFORM[0m=m && [31mCONFIG_IOSF_MBI[0m) || \
([31mCONFIG_I2C_DESIGNWARE_PLATFORM[0m=y && [31mCONFIG_IOSF_MBI[0m=y)
help
This driver enables managed host access to the PMIC [31mCONFIG_I2C[0m bus on select
Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
the host to request uninterrupted access to the PMIC's [31mCONFIG_I2C[0m bus from
the platform firmware controlling it. You should say Y if running on
a BayTrail system using the AXP288.
config [31mCONFIG_I2C_DIGICOLOR[0m
tristate "Conexant Digicolor I2C driver"
depends on [31mCONFIG_ARCH_DIGICOLOR[0m
help
Support for Conexant Digicolor SoCs (CX92755) [31mCONFIG_I2C[0m controller driver.
This driver can also be built as a module. If so, the module
will be called i2c-digicolor.
config [31mCONFIG_I2C_EFM32[0m
tristate "EFM32 I2C controller"
depends on [31mCONFIG_ARCH_EFM32[0m || [31mCONFIG_COMPILE_TEST[0m
help
This driver supports the i2c block found in Energy Micro's EFM32
SoCs.
config [31mCONFIG_I2C_EG20T[0m
tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
depends on [31mCONFIG_PCI[0m && ([31mCONFIG_X86_32[0m || [31mCONFIG_MIPS[0m || [31mCONFIG_COMPILE_TEST[0m)
help
This driver is for PCH(Platform controller Hub) [31mCONFIG_I2C[0m of EG20T which
is an IOH(Input/Output Hub) for x86 embedded processor.
This driver can access PCH [31mCONFIG_I2C[0m bus device.
This driver also can be used for LAPIS Semiconductor IOH(Input/
Output Hub), ML7213, ML7223 and ML7831.
ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
for MP(Media Phone) use and 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.
config [31mCONFIG_I2C_EMEV2[0m
tristate "EMMA Mobile series I2C adapter"
depends on [31mCONFIG_HAVE_CLK[0m
select [31mCONFIG_I2C_SLAVE[0m
help
If you say yes to this option, support will be included for the
[31mCONFIG_I2C[0m interface on the Renesas Electronics EM/EV family of processors.
config [31mCONFIG_I2C_EXYNOS5[0m
tristate "Exynos5 high-speed I2C driver"
depends on [31mCONFIG_ARCH_EXYNOS[0m && [31mCONFIG_OF[0m
default y
help
High-speed [31mCONFIG_I2C[0m controller on Exynos5 based Samsung SoCs.
config [31mCONFIG_I2C_GPIO[0m
tristate "GPIO-based bitbanging I2C"
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_I2C_ALGOBIT[0m
help
This is a very simple bitbanging [31mCONFIG_I2C[0m driver utilizing the
arch-neutral GPIO API to control the SCL and SDA lines.
config [31mCONFIG_I2C_HIGHLANDER[0m
tristate "Highlander FPGA SMBus interface"
depends on [31mCONFIG_SH_HIGHLANDER[0m
help
If you say yes to this option, support will be included for
the SMBus interface located in the [31mCONFIG_FPGA[0m on various Highlander
boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
FPGAs. This is wholly unrelated to the SoC [31mCONFIG_I2C[0m.
This driver can also be built as a module. If so, the module
will be called i2c-highlander.
config [31mCONFIG_I2C_IBM_IIC[0m
tristate "IBM PPC 4xx on-chip I2C interface"
depends on [31mCONFIG_4xx[0m
help
Say Y here if you want to use IIC peripheral found on
embedded IBM [31mCONFIG_PPC[0m [31mCONFIG_4xx[0m based systems.
This driver can also be built as a module. If so, the module
will be called i2c-ibm_iic.
config [31mCONFIG_I2C_IMG[0m
tristate "Imagination Technologies I2C SCB Controller"
depends on [31mCONFIG_MIPS[0m || [31mCONFIG_METAG[0m || [31mCONFIG_COMPILE_TEST[0m
help
Say Y here if you want to use the IMG [31mCONFIG_I2C[0m SCB controller,
available on the TZ1090 and other IMG SoCs.
This driver can also be built as a module. If so, the module
will be called i2c-img-scb.
config [31mCONFIG_I2C_IMX[0m
tristate "IMX I2C interface"
depends on [31mCONFIG_ARCH_MXC[0m || [31mCONFIG_ARCH_LAYERSCAPE[0m || [31mCONFIG_COLDFIRE[0m
help
Say Y here if you want to use the IIC bus controller on
the Freescale i.MX/MXC, Layerscape or ColdFire processors.
This driver can also be built as a module. If so, the module
will be called i2c-imx.
config [31mCONFIG_I2C_IMX_LPI2C[0m
tristate "IMX Low Power I2C interface"
depends on [31mCONFIG_ARCH_MXC[0m || [31mCONFIG_COMPILE_TEST[0m
help
Say Y here if you want to use the Low Power IIC bus controller
on the Freescale i.MX processors.
This driver can also be built as a module. If so, the module
will be called i2c-imx-lpi2c.
config [31mCONFIG_I2C_IOP3XX[0m
tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
depends on [31mCONFIG_ARCH_IOP32X[0m || [31mCONFIG_ARCH_IOP33X[0m || [31mCONFIG_ARCH_IXP4XX[0m || [31mCONFIG_ARCH_IOP13XX[0m
help
Say Y here if you want to use the IIC bus controller on
the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
This driver can also be built as a module. If so, the module
will be called i2c-iop3xx.
config [31mCONFIG_I2C_JZ4780[0m
tristate "JZ4780 I2C controller interface support"
depends on [31mCONFIG_MACH_JZ4780[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes to this option, support will be included for the
Ingenic JZ4780 [31mCONFIG_I2C[0m controller.
If you don't know what to do here, say N.
config [31mCONFIG_I2C_KEMPLD[0m
tristate "Kontron COM I2C Controller"
depends on [31mCONFIG_MFD_KEMPLD[0m
help
This enables support for the [31mCONFIG_I2C[0m bus interface on some Kontron ETX
and COMexpress (ETXexpress) modules.
This driver can also be built as a module. If so, the module
will be called i2c-kempld.
config [31mCONFIG_I2C_LPC2K[0m
tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
depends on [31mCONFIG_OF[0m && ([31mCONFIG_ARCH_LPC18XX[0m || [31mCONFIG_COMPILE_TEST[0m)
help
This driver supports the [31mCONFIG_I2C[0m interface found several NXP
devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
This driver can also be built as a module. If so, the module
will be called i2c-lpc2k.
config [31mCONFIG_I2C_MESON[0m
tristate "Amlogic Meson I2C controller"
depends on [31mCONFIG_ARCH_MESON[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes to this option, support will be included for the
[31mCONFIG_I2C[0m interface on the Amlogic Meson family of SoCs.
config [31mCONFIG_I2C_MPC[0m
tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
depends on [31mCONFIG_PPC[0m
help
If you say yes to this option, support will be included for the
built-in [31mCONFIG_I2C[0m interface on the MPC107, Tsi107, MPC512x, MPC52xx,
MPC8240, MPC8245, MPC83xx, MPC85xx and [31mCONFIG_MPC8641[0m family processors.
This driver can also be built as a module. If so, the module
will be called i2c-mpc.
config [31mCONFIG_I2C_MT65XX[0m
tristate "MediaTek I2C adapter"
depends on [31mCONFIG_ARCH_MEDIATEK[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HAS_DMA[0m
help
This selects the MediaTek(R) Integrated Inter Circuit bus driver
for MT65xx and MT81xx.
If you want to use MediaTek(R) [31mCONFIG_I2C[0m interface, say Y or [31mCONFIG_M[0m here.
If unsure, say N.
config [31mCONFIG_I2C_MV64XXX[0m
tristate "Marvell mv64xxx I2C Controller"
depends on [31mCONFIG_MV64X60[0m || [31mCONFIG_PLAT_ORION[0m || [31mCONFIG_ARCH_SUNXI[0m || [31mCONFIG_ARCH_MVEBU[0m
help
If you say yes to this option, support will be included for the
built-in [31mCONFIG_I2C[0m interface on the Marvell 64xxx line of host bridges.
This driver is also used for Allwinner SoCs [31mCONFIG_I2C[0m controllers.
This driver can also be built as a module. If so, the module
will be called i2c-mv64xxx.
config [31mCONFIG_I2C_MXS[0m
tristate "Freescale i.MX28 I2C interface"
depends on [31mCONFIG_SOC_IMX28[0m
select [31mCONFIG_STMP_DEVICE[0m
help
Say Y here if you want to use the [31mCONFIG_I2C[0m bus controller on
the Freescale i.MX28 processors.
This driver can also be built as a module. If so, the module
will be called i2c-mxs.
config [31mCONFIG_I2C_NOMADIK[0m
tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
depends on [31mCONFIG_ARM_AMBA[0m
help
If you say yes to this option, support will be included for the
[31mCONFIG_I2C[0m interface from ST-Ericsson's Nomadik and Ux500 architectures,
as well as the [31mCONFIG_STA2X11[0m PCIe I/O HUB.
config [31mCONFIG_I2C_OCORES[0m
tristate "OpenCores I2C Controller"
help
If you say yes to this option, support will be included for the
OpenCores [31mCONFIG_I2C[0m controller. For details see
http://www.opencores.org/projects.cgi/web/i2c/overview
This driver can also be built as a module. If so, the module
will be called i2c-ocores.
config [31mCONFIG_I2C_OMAP[0m
tristate "OMAP I2C adapter"
depends on [31mCONFIG_ARCH_OMAP[0m
default y if [31mCONFIG_MACH_OMAP_H3[0m || [31mCONFIG_MACH_OMAP_OSK[0m
help
If you say yes to this option, support will be included for the
[31mCONFIG_I2C[0m interface on the Texas Instruments OMAP1/2 family of processors.
Like OMAP1510/1610/1710/5912 and OMAP242x.
For details see http://www.ti.com/omap.
config [31mCONFIG_I2C_PASEMI[0m
tristate "PA Semi SMBus interface"
depends on [31mCONFIG_PPC_PASEMI[0m && [31mCONFIG_PCI[0m
help
Supports the PA Semi PWRficient on-chip SMBus interfaces.
config [31mCONFIG_I2C_PCA_PLATFORM[0m
tristate "PCA9564/PCA9665 as platform device"
select [31mCONFIG_I2C_ALGOPCA[0m
default n
help
This driver supports a memory mapped Philips PCA9564/PCA9665
parallel bus to [31mCONFIG_I2C[0m bus controller.
This driver can also be built as a module. If so, the module
will be called i2c-pca-platform.
config [31mCONFIG_I2C_PMCMSP[0m
tristate "PMC MSP I2C TWI Controller"
depends on [31mCONFIG_PMC_MSP[0m
help
This driver supports the PMC TWI controller on MSP devices.
This driver can also be built as module. If so, the module
will be called i2c-pmcmsp.
config [31mCONFIG_I2C_PNX[0m
tristate "I2C bus support for Philips PNX and NXP LPC targets"
depends on [31mCONFIG_ARCH_LPC32XX[0m
help
This driver supports the Philips IP3204 [31mCONFIG_I2C[0m IP block master and/or
slave controller
This driver can also be built as a module. If so, the module
will be called i2c-pnx.
config [31mCONFIG_I2C_PUV3[0m
tristate "PKUnity v3 I2C bus support"
depends on [31mCONFIG_UNICORE32[0m && [31mCONFIG_ARCH_PUV3[0m
select [31mCONFIG_I2C_ALGOBIT[0m
help
This driver supports the [31mCONFIG_I2C[0m IP inside the PKUnity-v3 SoC.
This [31mCONFIG_I2C[0m bus controller is under AMBA/AXI bus.
This driver can also be built as a module. If so, the module
will be called i2c-puv3.
config [31mCONFIG_I2C_PXA[0m
tristate "Intel PXA2XX I2C adapter"
depends on [31mCONFIG_ARCH_PXA[0m || [31mCONFIG_ARCH_MMP[0m || [31mCONFIG_ARCH_MVEBU[0m || ([31mCONFIG_X86_32[0m && [31mCONFIG_PCI[0m && [31mCONFIG_OF[0m)
help
If you have devices in the PXA [31mCONFIG_I2C[0m bus, say yes to this option.
This driver can also be built as a module. If so, the module
will be called i2c-pxa.
config [31mCONFIG_I2C_PXA_PCI[0m
def_bool [31mCONFIG_I2C_PXA[0m && [31mCONFIG_X86_32[0m && [31mCONFIG_PCI[0m && [31mCONFIG_OF[0m
config [31mCONFIG_I2C_PXA_SLAVE[0m
bool "Intel PXA2XX I2C Slave comms support"
depends on [31mCONFIG_I2C_PXA[0m && ![31mCONFIG_X86_32[0m
help
Support [31mCONFIG_I2C[0m slave mode communications on the PXA [31mCONFIG_I2C[0m bus. This
is necessary for systems where the PXA may be a target on the
[31mCONFIG_I2C[0m bus.
config [31mCONFIG_I2C_QUP[0m
tristate "Qualcomm QUP based I2C controller"
depends on [31mCONFIG_ARCH_QCOM[0m
help
If you say yes to this option, support will be included for the
built-in [31mCONFIG_I2C[0m interface on the Qualcomm SoCs.
This driver can also be built as a module. If so, the module
will be called i2c-qup.
config [31mCONFIG_I2C_RIIC[0m
tristate "Renesas RIIC adapter"
depends on [31mCONFIG_ARCH_RENESAS[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes to this option, support will be included for the
Renesas RIIC [31mCONFIG_I2C[0m interface.
This driver can also be built as a module. If so, the module
will be called i2c-riic.
config [31mCONFIG_I2C_RK3X[0m
tristate "Rockchip RK3xxx I2C adapter"
depends on [31mCONFIG_OF[0m && [31mCONFIG_COMMON_CLK[0m
help
Say Y here to include support for the [31mCONFIG_I2C[0m adapter in Rockchip RK3xxx
SoCs.
This driver can also be built as a module. If so, the module will
be called i2c-rk3x.
config [31mCONFIG_HAVE_S3C2410_I2C[0m
bool
help
This will include [31mCONFIG_I2C[0m support for Samsung SoCs. If you want to
include [31mCONFIG_I2C[0m support for any machine, kindly select this in the
respective Kconfig file.
config [31mCONFIG_I2C_S3C2410[0m
tristate "S3C2410 I2C Driver"
depends on [31mCONFIG_HAVE_S3C2410_I2C[0m
help
Say Y here to include support for [31mCONFIG_I2C[0m controller in the
Samsung SoCs.
config [31mCONFIG_I2C_SH7760[0m
tristate "Renesas SH7760 I2C Controller"
depends on [31mCONFIG_CPU_SUBTYPE_SH7760[0m
help
This driver supports the 2 [31mCONFIG_I2C[0m interfaces on the Renesas SH7760.
This driver can also be built as a module. If so, the module
will be called i2c-sh7760.
config [31mCONFIG_I2C_SH_MOBILE[0m
tristate "SuperH Mobile I2C Controller"
depends on [31mCONFIG_HAS_DMA[0m
depends on [31mCONFIG_ARCH_SHMOBILE[0m || [31mCONFIG_ARCH_RENESAS[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes to this option, support will be included for the
built-in [31mCONFIG_I2C[0m interface on the Renesas SH-Mobile processor.
This driver can also be built as a module. If so, the module
will be called i2c-sh_mobile.
config [31mCONFIG_I2C_SIMTEC[0m
tristate "Simtec Generic I2C interface"
select [31mCONFIG_I2C_ALGOBIT[0m
help
If you say yes to this option, support will be included for
the Simtec Generic [31mCONFIG_I2C[0m interface. This driver is for the
simple [31mCONFIG_I2C[0m bus used on newer Simtec products for general
[31mCONFIG_I2C[0m, such as DDC on the Simtec BBD2016A.
This driver can also be built as a module. If so, the module
will be called i2c-simtec.
config [31mCONFIG_I2C_SIRF[0m
tristate "CSR SiRFprimaII I2C interface"
depends on [31mCONFIG_ARCH_SIRF[0m
help
If you say yes to this option, support will be included for the
CSR SiRFprimaII [31mCONFIG_I2C[0m interface.
This driver can also be built as a module. If so, the module
will be called i2c-sirf.
config [31mCONFIG_I2C_ST[0m
tristate "STMicroelectronics SSC I2C support"
depends on [31mCONFIG_ARCH_STI[0m
help
Enable this option to add support for STMicroelectronics SoCs
hardware SSC (Synchronous Serial Controller) as an [31mCONFIG_I2C[0m controller.
This driver can also be built as module. If so, the module
will be called i2c-st.
config [31mCONFIG_I2C_STU300[0m
tristate "ST Microelectronics DDC I2C interface"
depends on [31mCONFIG_MACH_U300[0m
default y if [31mCONFIG_MACH_U300[0m
help
If you say yes to this option, support will be included for the
[31mCONFIG_I2C[0m interface from ST Microelectronics simply called "DDC I2C"
supporting both [31mCONFIG_I2C[0m and DDC, used in e.g. the U300 series
mobile platforms.
This driver can also be built as a module. If so, the module
will be called i2c-stu300.
config [31mCONFIG_I2C_SUN6I_P2WI[0m
tristate "Allwinner sun6i internal P2WI controller"
depends on [31mCONFIG_RESET_CONTROLLER[0m
depends on [31mCONFIG_MACH_SUN6I[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes to this option, support will be included for the
P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
SOCs.
The P2WI looks like an SMBus controller (which supports only byte
accesses), except that it only supports one slave device.
This interface is used to connect to specific PMIC devices (like the
AXP221).
config [31mCONFIG_I2C_TEGRA[0m
tristate "NVIDIA Tegra internal I2C controller"
depends on [31mCONFIG_ARCH_TEGRA[0m
help
If you say yes to this option, support will be included for the
[31mCONFIG_I2C[0m controller embedded in NVIDIA Tegra SOCs
config [31mCONFIG_I2C_UNIPHIER[0m
tristate "UniPhier FIFO-less I2C controller"
depends on [31mCONFIG_ARCH_UNIPHIER[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes to this option, support will be included for
the UniPhier FIFO-less [31mCONFIG_I2C[0m interface embedded in PH1-LD4, PH1-sLD8,
or older UniPhier SoCs.
config [31mCONFIG_I2C_UNIPHIER_F[0m
tristate "UniPhier FIFO-builtin I2C controller"
depends on [31mCONFIG_ARCH_UNIPHIER[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes to this option, support will be included for
the UniPhier FIFO-builtin [31mCONFIG_I2C[0m interface embedded in PH1-Pro4,
PH1-Pro5, or newer UniPhier SoCs.
config [31mCONFIG_I2C_VERSATILE[0m
tristate "ARM Versatile/Realview I2C bus support"
depends on [31mCONFIG_ARCH_VERSATILE[0m || [31mCONFIG_ARCH_REALVIEW[0m || [31mCONFIG_ARCH_VEXPRESS[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_I2C_ALGOBIT[0m
help
Say yes if you want to support the [31mCONFIG_I2C[0m serial bus on ARMs Versatile
range of platforms.
This driver can also be built as a module. If so, the module
will be called i2c-versatile.
config [31mCONFIG_I2C_WMT[0m
tristate "Wondermedia WM8xxx SoC I2C bus support"
depends on [31mCONFIG_ARCH_VT8500[0m
help
Say yes if you want to support the [31mCONFIG_I2C[0m bus on Wondermedia 8xxx-series
SoCs.
This driver can also be built as a module. If so, the module will be
called i2c-wmt.
config [31mCONFIG_I2C_OCTEON[0m
tristate "Cavium OCTEON I2C bus support"
depends on [31mCONFIG_CAVIUM_OCTEON_SOC[0m
help
Say yes if you want to support the [31mCONFIG_I2C[0m serial bus on Cavium
OCTEON SOC.
This driver can also be built as a module. If so, the module
will be called i2c-octeon.
config [31mCONFIG_I2C_THUNDERX[0m
tristate "Cavium ThunderX I2C bus support"
depends on [31mCONFIG_64BIT[0m && [31mCONFIG_PCI[0m && ([31mCONFIG_ARM64[0m || [31mCONFIG_COMPILE_TEST[0m)
select [31mCONFIG_I2C_SMBUS[0m
help
Say yes if you want to support the [31mCONFIG_I2C[0m serial bus on Cavium
ThunderX SOC.
This driver can also be built as a module. If so, the module
will be called i2c-thunderx.
config [31mCONFIG_I2C_XILINX[0m
tristate "Xilinx I2C Controller"
depends on [31mCONFIG_HAS_IOMEM[0m
help
If you say yes to this option, support will be included for the
Xilinx [31mCONFIG_I2C[0m controller.
This driver can also be built as a module. If so, the module
will be called xilinx_i2c.
config [31mCONFIG_I2C_XLR[0m
tristate "Netlogic XLR and Sigma Designs I2C support"
depends on [31mCONFIG_CPU_XLR[0m || [31mCONFIG_ARCH_TANGO[0m
help
This driver enables support for the on-chip [31mCONFIG_I2C[0m interface of
the Netlogic XLR/XLS [31mCONFIG_MIPS[0m processors and Sigma Designs SOCs.
This driver can also be built as a module. If so, the module
will be called i2c-xlr.
config [31mCONFIG_I2C_XLP9XX[0m
tristate "XLP9XX I2C support"
depends on [31mCONFIG_CPU_XLP[0m || [31mCONFIG_ARCH_VULCAN[0m || [31mCONFIG_COMPILE_TEST[0m
help
This driver enables support for the on-chip [31mCONFIG_I2C[0m interface of
the Broadcom XLP9xx/XLP5xx [31mCONFIG_MIPS[0m and Vulcan [31mCONFIG_ARM64[0m processors.
This driver can also be built as a module. If so, the module will
be called i2c-xlp9xx.
config [31mCONFIG_I2C_RCAR[0m
tristate "Renesas R-Car I2C Controller"
depends on [31mCONFIG_HAS_DMA[0m
depends on [31mCONFIG_ARCH_RENESAS[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_I2C_SLAVE[0m
help
If you say yes to this option, support will be included for the
R-Car [31mCONFIG_I2C[0m controller.
This driver can also be built as a module. If so, the module
will be called i2c-rcar.
comment "External I2C/SMBus adapter drivers"
config [31mCONFIG_I2C_DIOLAN_U2C[0m
tristate "Diolan U2C-12 USB adapter"
depends on [31mCONFIG_USB[0m
help
If you say yes to this option, support will be included for Diolan
U2C-12, a [31mCONFIG_USB[0m to [31mCONFIG_I2C[0m interface.
This driver can also be built as a module. If so, the module
will be called i2c-diolan-u2c.
config [31mCONFIG_I2C_DLN2[0m
tristate "Diolan DLN-2 USB I2C adapter"
depends on [31mCONFIG_MFD_DLN2[0m
help
If you say yes to this option, support will be included for Diolan
DLN2, a [31mCONFIG_USB[0m to [31mCONFIG_I2C[0m interface.
This driver can also be built as a module. If so, the module
will be called i2c-dln2.
config [31mCONFIG_I2C_PARPORT[0m
tristate "Parallel port adapter"
depends on [31mCONFIG_PARPORT[0m
select [31mCONFIG_I2C_ALGOBIT[0m
select [31mCONFIG_I2C_SMBUS[0m
help
This supports parallel port [31mCONFIG_I2C[0m adapters such as the ones made by
Philips or Velleman, Analog Devices evaluation boards, and more.
Basically any adapter using the parallel port as an [31mCONFIG_I2C[0m bus with
no extra chipset is supported by this driver, or could be.
This driver is a replacement for (and was inspired by) an older
driver named i2c-philips-par. The new driver supports more devices,
and makes it easier to add support for new devices.
An adapter type parameter is now mandatory. Please read the file
Documentation/i2c/busses/i2c-parport for details.
Another driver exists, named i2c-parport-light, which doesn't depend
on the parport driver. This is meant for embedded systems. Don't say
Y here if you intend to say Y or [31mCONFIG_M[0m there.
This support is also available as a module. If so, the module
will be called i2c-parport.
config [31mCONFIG_I2C_PARPORT_LIGHT[0m
tristate "Parallel port adapter (light)"
select [31mCONFIG_I2C_ALGOBIT[0m
select [31mCONFIG_I2C_SMBUS[0m
help
This supports parallel port [31mCONFIG_I2C[0m adapters such as the ones made by
Philips or Velleman, Analog Devices evaluation boards, and more.
Basically any adapter using the parallel port as an [31mCONFIG_I2C[0m bus with
no extra chipset is supported by this driver, or could be.
This driver is a light version of i2c-parport. It doesn't depend
on the parport driver, and uses direct I/O access instead. This
might be preferred on embedded systems where wasting memory for
the clean but heavy parport handling is not an option. The
drawback is a reduced portability and the impossibility to
daisy-chain other parallel port devices.
Don't say Y here if you said Y or [31mCONFIG_M[0m to i2c-parport. Saying [31mCONFIG_M[0m to
both is possible but both modules should not be loaded at the same
time.
This support is also available as a module. If so, the module
will be called i2c-parport-light.
config [31mCONFIG_I2C_ROBOTFUZZ_OSIF[0m
tristate "RobotFuzz Open Source InterFace USB adapter"
depends on [31mCONFIG_USB[0m
help
If you say yes to this option, support will be included for the
RobotFuzz Open Source InterFace [31mCONFIG_USB[0m to [31mCONFIG_I2C[0m interface.
This driver can also be built as a module. If so, the module
will be called i2c-osif.
config [31mCONFIG_I2C_TAOS_EVM[0m
tristate "TAOS evaluation module"
depends on [31mCONFIG_TTY[0m
select [31mCONFIG_SERIO[0m
select [31mCONFIG_SERIO_SERPORT[0m
default n
help
This supports TAOS evaluation modules on serial port. In order to
use this driver, you will need the inputattach tool, which is part
of the input-utils package.
If unsure, say N.
This support is also available as a module. If so, the module
will be called i2c-taos-evm.
config [31mCONFIG_I2C_TINY_USB[0m
tristate "Tiny-USB adapter"
depends on [31mCONFIG_USB[0m
help
If you say yes to this option, support will be included for the
i2c-tiny-usb, a simple do-it-yourself [31mCONFIG_USB[0m to [31mCONFIG_I2C[0m interface. See
http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
This driver can also be built as a module. If so, the module
will be called i2c-tiny-usb.
config [31mCONFIG_I2C_VIPERBOARD[0m
tristate "Viperboard I2C master support"
depends on [31mCONFIG_MFD_VIPERBOARD[0m && [31mCONFIG_USB[0m
help
Say yes here to access the [31mCONFIG_I2C[0m part of the Nano River
Technologies Viperboard as [31mCONFIG_I2C[0m master.
See viperboard API specification and Nano
River Tech's viperboard.h for detailed meaning
of the module parameters.
comment "Other I2C/SMBus bus drivers"
config [31mCONFIG_I2C_ACORN[0m
tristate "Acorn IOC/IOMD I2C bus support"
depends on [31mCONFIG_ARCH_ACORN[0m
default y
select [31mCONFIG_I2C_ALGOBIT[0m
help
Say yes if you want to support the [31mCONFIG_I2C[0m bus on Acorn platforms.
If you don't know, say Y.
config [31mCONFIG_I2C_ELEKTOR[0m
tristate "Elektor ISA card"
depends on [31mCONFIG_ISA[0m && [31mCONFIG_HAS_IOPORT_MAP[0m && [31mCONFIG_BROKEN_ON_SMP[0m
select [31mCONFIG_I2C_ALGOPCF[0m
help
This supports the PCF8584 [31mCONFIG_ISA[0m bus [31mCONFIG_I2C[0m adapter. Say Y if you own
such an adapter.
This support is also available as a module. If so, the module
will be called i2c-elektor.
config [31mCONFIG_I2C_MLXCPLD[0m
tristate "Mellanox I2C driver"
depends on [31mCONFIG_X86_64[0m
help
This exposes the Mellanox platform [31mCONFIG_I2C[0m busses to the linux [31mCONFIG_I2C[0m layer
for [31mCONFIG_X86[0m based systems.
Controller is implemented as CPLD logic.
This driver can also be built as a module. If so, the module will be
called as i2c-mlxcpld.
config [31mCONFIG_I2C_PCA_ISA[0m
tristate "PCA9564/PCA9665 on an ISA bus"
depends on [31mCONFIG_ISA[0m
select [31mCONFIG_I2C_ALGOPCA[0m
default n
help
This driver supports [31mCONFIG_ISA[0m boards using the Philips PCA9564/PCA9665
parallel bus to [31mCONFIG_I2C[0m bus controller.
This driver can also be built as a module. If so, the module
will be called i2c-pca-isa.
This device is almost undetectable and using this driver on a
system which doesn't have this device will result in long
delays when [31mCONFIG_I2C[0m/SMBus chip drivers are loaded (e.g. at boot
time). If unsure, say N.
config [31mCONFIG_I2C_SIBYTE[0m
tristate "SiByte SMBus interface"
depends on [31mCONFIG_SIBYTE_SB1xxx_SOC[0m
help
Supports the SiByte SOC on-chip [31mCONFIG_I2C[0m interfaces (2 channels).
config [31mCONFIG_I2C_CROS_EC_TUNNEL[0m
tristate "ChromeOS EC tunnel I2C bus"
depends on [31mCONFIG_MFD_CROS_EC[0m
help
If you say yes here you get an [31mCONFIG_I2C[0m bus that will tunnel i2c commands
through to the other side of the ChromeOS EC to the i2c bus
connected there. This will work whatever the interface used to
talk to the EC ([31mCONFIG_SPI[0m, [31mCONFIG_I2C[0m or LPC).
config [31mCONFIG_I2C_XGENE_SLIMPRO[0m
tristate "APM X-Gene SoC I2C SLIMpro devices support"
depends on [31mCONFIG_ARCH_XGENE[0m && [31mCONFIG_MAILBOX[0m
help
Enable [31mCONFIG_I2C[0m bus access using the [31mCONFIG_APM[0m X-Gene SoC SLIMpro
co-processor. The [31mCONFIG_I2C[0m device access the [31mCONFIG_I2C[0m bus via the X-Gene
to SLIMpro (On chip coprocessor) mailbox mechanism.
If unsure, say N.
config [31mCONFIG_SCx200_ACB[0m
tristate "Geode ACCESS.bus support"
depends on [31mCONFIG_X86_32[0m && [31mCONFIG_PCI[0m
help
Enable the use of the ACCESS.bus controllers on the Geode [31mCONFIG_SCx200[0m and
SC1100 processors and the CS5535 and [31mCONFIG_CS5536[0m Geode companion devices.
If you don't know what to do here, say N.
This support is also available as a module. If so, the module
will be called scx200_acb.
config [31mCONFIG_I2C_OPAL[0m
tristate "IBM OPAL I2C driver"
depends on [31mCONFIG_PPC_POWERNV[0m
default y
help
This exposes the PowerNV platform i2c busses to the linux i2c layer,
the driver is based on the OPAL interfaces.
This driver can also be built as a module. If so, the module will be
called as i2c-opal.
endmenu