2 # Sensor device configuration
5 menu "I2C Hardware Bus support"
7 comment "PC SMBus host controller drivers"
14 If you say yes to this option, support will be included for the SMB
15 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
16 controller is part of the 7101 device, which is an ACPI-compliant
17 Power Management Unit (PMU).
19 This driver can also be built as a module. If so, the module
20 will be called i2c-ali1535.
24 depends on PCI && EXPERIMENTAL
26 If you say yes to this option, support will be included for the SMB
27 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
28 controller is part of the 7101 device, which is an ACPI-compliant
29 Power Management Unit (PMU).
31 This driver can also be built as a module. If so, the module
32 will be called i2c-ali1563.
38 If you say yes to this option, support will be included for the
39 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
41 This driver can also be built as a module. If so, the module
42 will be called i2c-ali15x3.
45 tristate "AMD 756/766/768/8111 and nVidia nForce"
48 If you say yes to this option, support will be included for the AMD
49 756/766/768 mainboard I2C interfaces. The driver also includes
50 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
51 the nVidia nForce I2C interface.
53 This driver can also be built as a module. If so, the module
54 will be called i2c-amd756.
56 config I2C_AMD756_S4882
57 tristate "SMBus multiplexing on the Tyan S4882"
58 depends on I2C_AMD756 && X86 && EXPERIMENTAL
60 Enabling this option will add specific SMBus support for the Tyan
61 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
62 over 8 different channels, where the various memory module EEPROMs
63 and temperature sensors live. Saying yes here will give you access
64 to these in addition to the trunk.
66 This driver can also be built as a module. If so, the module
67 will be called i2c-amd756-s4882.
73 If you say yes to this option, support will be included for the
74 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
76 This driver can also be built as a module. If so, the module
77 will be called i2c-amd8111.
80 tristate "Intel 82801 (ICH/PCH)"
83 If you say yes to this option, support will be included for the Intel
84 801 family of mainboard I2C interfaces. Specifically, the following
85 versions of the chipset are supported:
91 82801EB/ER (ICH5/ICH5R)
103 This driver can also be built as a module. If so, the module
104 will be called i2c-i801.
107 tristate "Intel SCH SMBus 1.0"
110 Say Y here if you want to use SMBus controller on the Intel SCH
113 This driver can also be built as a module. If so, the module
114 will be called i2c-isch.
117 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
120 If you say yes to this option, support will be included for the Intel
121 PIIX4 family of mainboard I2C interfaces. Specifically, the following
122 versions of the chipset are supported (note that Serverworks is part
140 This driver can also be built as a module. If so, the module
141 will be called i2c-piix4.
144 tristate "Nvidia nForce2, nForce3 and nForce4"
147 If you say yes to this option, support will be included for the Nvidia
148 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
150 This driver can also be built as a module. If so, the module
151 will be called i2c-nforce2.
153 config I2C_NFORCE2_S4985
154 tristate "SMBus multiplexing on the Tyan S4985"
155 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
157 Enabling this option will add specific SMBus support for the Tyan
158 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
159 over 4 different channels, where the various memory module EEPROMs
160 live. Saying yes here will give you access to these in addition
163 This driver can also be built as a module. If so, the module
164 will be called i2c-nforce2-s4985.
170 If you say yes to this option, support will be included for the
171 SiS5595 SMBus (a subset of I2C) interface.
173 This driver can also be built as a module. If so, the module
174 will be called i2c-sis5595.
177 tristate "SiS 630/730"
180 If you say yes to this option, support will be included for the
181 SiS630 and SiS730 SMBus (a subset of I2C) interface.
183 This driver can also be built as a module. If so, the module
184 will be called i2c-sis630.
190 If you say yes to this option, support will be included for the SiS
191 96x SMBus (a subset of I2C) interfaces. Specifically, the following
192 chipsets are supported:
201 This driver can also be built as a module. If so, the module
202 will be called i2c-sis96x.
205 tristate "VIA VT82C586B"
206 depends on PCI && EXPERIMENTAL
209 If you say yes to this option, support will be included for the VIA
210 82C586B I2C interface
212 This driver can also be built as a module. If so, the module
213 will be called i2c-via.
216 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
219 If you say yes to this option, support will be included for the VIA
220 VT82C596 and later SMBus interface. Specifically, the following
221 chipsets are supported:
233 This driver can also be built as a module. If so, the module
234 will be called i2c-viapro.
238 comment "ACPI drivers"
241 tristate "SMBus Control Method Interface"
243 This driver supports the SMBus Control Method Interface. It needs the
244 BIOS to declare ACPI control methods as described in the SMBus Control
245 Method Interface specification.
247 To compile this driver as a module, choose M here:
248 the module will be called i2c-scmi.
252 comment "Mac SMBus host controller drivers"
253 depends on PPC_CHRP || PPC_PMAC
256 tristate "CHRP Apple Hydra Mac I/O I2C interface"
257 depends on PCI && PPC_CHRP && EXPERIMENTAL
260 This supports the use of the I2C interface in the Apple Hydra Mac
261 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
264 This support is also available as a module. If so, the module
265 will be called i2c-hydra.
268 tristate "Powermac I2C interface"
272 This exposes the various PowerMac i2c interfaces to the linux i2c
273 layer and to userland. It is used by various drivers on the PowerMac
274 platform, and should generally be enabled.
276 This support is also available as a module. If so, the module
277 will be called i2c-powermac.
279 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
282 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
283 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
285 This supports the use of the I2C interface on Atmel AT91
288 This driver is BROKEN because the controller which it uses
289 will easily trigger RX overrun and TX underrun errors. Using
290 low I2C clock rates may partially work around those issues
291 on some systems. Another serious problem is that there is no
292 documented way to issue repeated START conditions, as needed
293 to support combined I2C messages. Use the i2c-gpio driver
294 unless your system can cope with those limitations.
297 tristate "Au1550/Au1200 SMBus interface"
298 depends on SOC_AU1550 || SOC_AU1200
300 If you say yes to this option, support will be included for the
301 Au1550 and Au1200 SMBus interface.
303 This driver can also be built as a module. If so, the module
304 will be called i2c-au1550.
306 config I2C_BLACKFIN_TWI
307 tristate "Blackfin TWI I2C support"
309 depends on !BF561 && !BF531 && !BF532 && !BF533
311 This is the I2C bus driver for Blackfin on-chip TWI interface.
313 This driver can also be built as a module. If so, the module
314 will be called i2c-bfin-twi.
316 config I2C_BLACKFIN_TWI_CLK_KHZ
317 int "Blackfin TWI I2C clock (kHz)"
318 depends on I2C_BLACKFIN_TWI
322 The unit of the TWI clock is kHz.
325 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
326 depends on (CPM1 || CPM2) && OF_I2C
328 This supports the use of the I2C interface on Freescale
329 processors with CPM1 or CPM2.
331 This driver can also be built as a module. If so, the module
332 will be called i2c-cpm.
335 tristate "DaVinci I2C driver"
336 depends on ARCH_DAVINCI
338 Support for TI DaVinci I2C controller driver.
340 This driver can also be built as a module. If so, the module
341 will be called i2c-davinci.
343 Please note that this driver might be needed to bring up other
344 devices such as DaVinci NIC.
345 For details please see http://www.ti.com/davinci
347 config I2C_DESIGNWARE
348 tristate "Synopsys DesignWare"
351 If you say yes to this option, support will be included for the
352 Synopsys DesignWare I2C adapter. Only master mode is supported.
354 This driver can also be built as a module. If so, the module
355 will be called i2c-designware.
358 tristate "GPIO-based bitbanging I2C"
359 depends on GENERIC_GPIO
362 This is a very simple bitbanging I2C driver utilizing the
363 arch-neutral GPIO API to control the SCL and SDA lines.
365 config I2C_HIGHLANDER
366 tristate "Highlander FPGA SMBus interface"
367 depends on SH_HIGHLANDER
369 If you say yes to this option, support will be included for
370 the SMBus interface located in the FPGA on various Highlander
371 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
372 FPGAs. This is wholly unrelated to the SoC I2C.
374 This driver can also be built as a module. If so, the module
375 will be called i2c-highlander.
378 tristate "IBM PPC 4xx on-chip I2C interface"
381 Say Y here if you want to use IIC peripheral found on
382 embedded IBM PPC 4xx based systems.
384 This driver can also be built as a module. If so, the module
385 will be called i2c-ibm_iic.
388 tristate "IMX I2C interface"
391 Say Y here if you want to use the IIC bus controller on
392 the Freescale i.MX/MXC processors.
394 This driver can also be built as a module. If so, the module
395 will be called i2c-imx.
398 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
399 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
401 Say Y here if you want to use the IIC bus controller on
402 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
404 This driver can also be built as a module. If so, the module
405 will be called i2c-iop3xx.
408 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
409 depends on ARCH_IXP2000
412 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
413 system and are using GPIO lines for an I2C bus.
415 This support is also available as a module. If so, the module
416 will be called i2c-ixp2000.
418 This driver is deprecated and will be dropped soon. Use i2c-gpio
422 tristate "MPC107/824x/85xx/52xx/86xx"
425 If you say yes to this option, support will be included for the
426 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
427 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
428 family processors, though interrupts are known not to work.
430 This driver can also be built as a module. If so, the module
431 will be called i2c-mpc.
434 tristate "Marvell mv64xxx I2C Controller"
435 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
437 If you say yes to this option, support will be included for the
438 built-in I2C interface on the Marvell 64xxx line of host bridges.
440 This driver can also be built as a module. If so, the module
441 will be called i2c-mv64xxx.
444 tristate "OpenCores I2C Controller"
445 depends on EXPERIMENTAL
447 If you say yes to this option, support will be included for the
448 OpenCores I2C controller. For details see
449 http://www.opencores.org/projects.cgi/web/i2c/overview
451 This driver can also be built as a module. If so, the module
452 will be called i2c-ocores.
455 tristate "OMAP I2C adapter"
457 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
459 If you say yes to this option, support will be included for the
460 I2C interface on the Texas Instruments OMAP1/2 family of processors.
461 Like OMAP1510/1610/1710/5912 and OMAP242x.
462 For details see http://www.ti.com/omap.
465 tristate "PA Semi SMBus interface"
466 depends on PPC_PASEMI && PCI
468 Supports the PA Semi PWRficient on-chip SMBus interfaces.
471 tristate "I2C bus support for Philips PNX targets"
472 depends on ARCH_PNX4008
474 This driver supports the Philips IP3204 I2C IP block master and/or
477 This driver can also be built as a module. If so, the module
478 will be called i2c-pnx.
481 tristate "Intel PXA2XX I2C adapter"
482 depends on ARCH_PXA || ARCH_MMP
484 If you have devices in the PXA I2C bus, say yes to this option.
485 This driver can also be built as a module. If so, the module
486 will be called i2c-pxa.
489 bool "Intel PXA2XX I2C Slave comms support"
492 Support I2C slave mode communications on the PXA I2C bus. This
493 is necessary for systems where the PXA may be a target on the
497 tristate "S3C2410 I2C Driver"
498 depends on ARCH_S3C2410 || ARCH_S3C64XX
500 Say Y here to include support for I2C controller in the
501 Samsung S3C2410 based System-on-Chip devices.
504 tristate "S6000 I2C support"
505 depends on XTENSA_VARIANT_S6000
507 This driver supports the on chip I2C device on the
508 S6000 xtensa processor family.
510 To compile this driver as a module, choose M here. The module
511 will be called i2c-s6000.
514 tristate "Renesas SH7760 I2C Controller"
515 depends on CPU_SUBTYPE_SH7760
517 This driver supports the 2 I2C interfaces on the Renesas SH7760.
519 This driver can also be built as a module. If so, the module
520 will be called i2c-sh7760.
523 tristate "SuperH Mobile I2C Controller"
526 If you say yes to this option, support will be included for the
527 built-in I2C interface on the Renesas SH-Mobile processor.
529 This driver can also be built as a module. If so, the module
530 will be called i2c-sh_mobile.
533 tristate "Simtec Generic I2C interface"
536 If you say yes to this option, support will be included for
537 the Simtec Generic I2C interface. This driver is for the
538 simple I2C bus used on newer Simtec products for general
539 I2C, such as DDC on the Simtec BBD2016A.
541 This driver can also be built as a module. If so, the module
542 will be called i2c-simtec.
545 tristate "ST Microelectronics DDC I2C interface"
547 default y if MACH_U300
549 If you say yes to this option, support will be included for the
550 I2C interface from ST Microelectronics simply called "DDC I2C"
551 supporting both I2C and DDC, used in e.g. the U300 series
554 This driver can also be built as a module. If so, the module
555 will be called i2c-stu300.
558 tristate "ARM Versatile/Realview I2C bus support"
559 depends on ARCH_VERSATILE || ARCH_REALVIEW
562 Say yes if you want to support the I2C serial bus on ARMs Versatile
565 This driver can also be built as a module. If so, the module
566 will be called i2c-versatile.
569 tristate "Cavium OCTEON I2C bus support"
570 depends on CPU_CAVIUM_OCTEON
572 Say yes if you want to support the I2C serial bus on Cavium
575 This driver can also be built as a module. If so, the module
576 will be called i2c-octeon.
578 comment "External I2C/SMBus adapter drivers"
581 tristate "Parallel port adapter"
586 This supports parallel port I2C adapters such as the ones made by
587 Philips or Velleman, Analog Devices evaluation boards, and more.
588 Basically any adapter using the parallel port as an I2C bus with
589 no extra chipset is supported by this driver, or could be.
591 This driver is a replacement for (and was inspired by) an older
592 driver named i2c-philips-par. The new driver supports more devices,
593 and makes it easier to add support for new devices.
595 An adapter type parameter is now mandatory. Please read the file
596 Documentation/i2c/busses/i2c-parport for details.
598 Another driver exists, named i2c-parport-light, which doesn't depend
599 on the parport driver. This is meant for embedded systems. Don't say
600 Y here if you intend to say Y or M there.
602 This support is also available as a module. If so, the module
603 will be called i2c-parport.
605 config I2C_PARPORT_LIGHT
606 tristate "Parallel port adapter (light)"
609 This supports parallel port I2C adapters such as the ones made by
610 Philips or Velleman, Analog Devices evaluation boards, and more.
611 Basically any adapter using the parallel port as an I2C bus with
612 no extra chipset is supported by this driver, or could be.
614 This driver is a light version of i2c-parport. It doesn't depend
615 on the parport driver, and uses direct I/O access instead. This
616 might be preferred on embedded systems where wasting memory for
617 the clean but heavy parport handling is not an option. The
618 drawback is a reduced portability and the impossibility to
619 daisy-chain other parallel port devices.
621 Don't say Y here if you said Y or M to i2c-parport. Saying M to
622 both is possible but both modules should not be loaded at the same
625 This support is also available as a module. If so, the module
626 will be called i2c-parport-light.
629 tristate "TAOS evaluation module"
630 depends on EXPERIMENTAL
635 This supports TAOS evaluation modules on serial port. In order to
636 use this driver, you will need the inputattach tool, which is part
637 of the input-utils package.
641 This support is also available as a module. If so, the module
642 will be called i2c-taos-evm.
645 tristate "Tiny-USB adapter"
648 If you say yes to this option, support will be included for the
649 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
650 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
652 This driver can also be built as a module. If so, the module
653 will be called i2c-tiny-usb.
655 comment "Other I2C/SMBus bus drivers"
658 tristate "Acorn IOC/IOMD I2C bus support"
659 depends on ARCH_ACORN
663 Say yes if you want to support the I2C bus on Acorn platforms.
665 If you don't know, say Y.
668 tristate "Elektor ISA card"
669 depends on ISA && BROKEN_ON_SMP
672 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
675 This support is also available as a module. If so, the module
676 will be called i2c-elektor.
679 tristate "PCA9564/PCA9665 on an ISA bus"
684 This driver supports ISA boards using the Philips PCA9564/PCA9665
685 parallel bus to I2C bus controller.
687 This driver can also be built as a module. If so, the module
688 will be called i2c-pca-isa.
690 This device is almost undetectable and using this driver on a
691 system which doesn't have this device will result in long
692 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
693 time). If unsure, say N.
695 config I2C_PCA_PLATFORM
696 tristate "PCA9564/PCA9665 as platform device"
700 This driver supports a memory mapped Philips PCA9564/PCA9665
701 parallel bus to I2C bus controller.
703 This driver can also be built as a module. If so, the module
704 will be called i2c-pca-platform.
707 tristate "PMC MSP I2C TWI Controller"
710 This driver supports the PMC TWI controller on MSP devices.
712 This driver can also be built as module. If so, the module
713 will be called i2c-pmcmsp.
716 tristate "SiByte SMBus interface"
717 depends on SIBYTE_SB1xxx_SOC
719 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
722 tristate "I2C/SMBus Test Stub"
723 depends on EXPERIMENTAL && m
726 This module may be useful to developers of SMBus client drivers,
727 especially for certain kinds of sensor chips.
729 If you do build this module, be sure to read the notes and warnings
730 in <file:Documentation/i2c/i2c-stub>.
732 If you don't know what to do here, definitely say N.
735 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
736 depends on SCx200_GPIO
739 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
741 If you don't know what to do here, say N.
743 This support is also available as a module. If so, the module
744 will be called scx200_i2c.
746 This driver is deprecated and will be dropped soon. Use i2c-gpio
747 (or scx200_acb) instead.
749 config SCx200_I2C_SCL
750 int "GPIO pin used for SCL"
751 depends on SCx200_I2C
754 Enter the GPIO pin number used for the SCL signal. This value can
755 also be specified with a module parameter.
757 config SCx200_I2C_SDA
758 int "GPIO pin used for SDA"
759 depends on SCx200_I2C
762 Enter the GPIO pin number used for the SSA signal. This value can
763 also be specified with a module parameter.
766 tristate "Geode ACCESS.bus support"
767 depends on X86_32 && PCI
769 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
770 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
772 If you don't know what to do here, say N.
774 This support is also available as a module. If so, the module
775 will be called scx200_acb.