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"
112 Say Y here if you want to use SMBus controller on the Intel SCH
115 This driver can also be built as a module. If so, the module
116 will be called i2c-isch.
119 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
122 If you say yes to this option, support will be included for the Intel
123 PIIX4 family of mainboard I2C interfaces. Specifically, the following
124 versions of the chipset are supported (note that Serverworks is part
142 This driver can also be built as a module. If so, the module
143 will be called i2c-piix4.
146 tristate "Nvidia nForce2, nForce3 and nForce4"
149 If you say yes to this option, support will be included for the Nvidia
150 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
152 This driver can also be built as a module. If so, the module
153 will be called i2c-nforce2.
155 config I2C_NFORCE2_S4985
156 tristate "SMBus multiplexing on the Tyan S4985"
157 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
159 Enabling this option will add specific SMBus support for the Tyan
160 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
161 over 4 different channels, where the various memory module EEPROMs
162 live. Saying yes here will give you access to these in addition
165 This driver can also be built as a module. If so, the module
166 will be called i2c-nforce2-s4985.
172 If you say yes to this option, support will be included for the
173 SiS5595 SMBus (a subset of I2C) interface.
175 This driver can also be built as a module. If so, the module
176 will be called i2c-sis5595.
179 tristate "SiS 630/730"
182 If you say yes to this option, support will be included for the
183 SiS630 and SiS730 SMBus (a subset of I2C) interface.
185 This driver can also be built as a module. If so, the module
186 will be called i2c-sis630.
192 If you say yes to this option, support will be included for the SiS
193 96x SMBus (a subset of I2C) interfaces. Specifically, the following
194 chipsets are supported:
203 This driver can also be built as a module. If so, the module
204 will be called i2c-sis96x.
207 tristate "VIA VT82C586B"
208 depends on PCI && EXPERIMENTAL
211 If you say yes to this option, support will be included for the VIA
212 82C586B I2C interface
214 This driver can also be built as a module. If so, the module
215 will be called i2c-via.
218 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
221 If you say yes to this option, support will be included for the VIA
222 VT82C596 and later SMBus interface. Specifically, the following
223 chipsets are supported:
235 This driver can also be built as a module. If so, the module
236 will be called i2c-viapro.
240 comment "ACPI drivers"
243 tristate "SMBus Control Method Interface"
245 This driver supports the SMBus Control Method Interface. It needs the
246 BIOS to declare ACPI control methods as described in the SMBus Control
247 Method Interface specification.
249 To compile this driver as a module, choose M here:
250 the module will be called i2c-scmi.
254 comment "Mac SMBus host controller drivers"
255 depends on PPC_CHRP || PPC_PMAC
258 tristate "CHRP Apple Hydra Mac I/O I2C interface"
259 depends on PCI && PPC_CHRP && EXPERIMENTAL
262 This supports the use of the I2C interface in the Apple Hydra Mac
263 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
266 This support is also available as a module. If so, the module
267 will be called i2c-hydra.
270 tristate "Powermac I2C interface"
274 This exposes the various PowerMac i2c interfaces to the linux i2c
275 layer and to userland. It is used by various drivers on the PowerMac
276 platform, and should generally be enabled.
278 This support is also available as a module. If so, the module
279 will be called i2c-powermac.
281 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
284 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
285 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
287 This supports the use of the I2C interface on Atmel AT91
290 This driver is BROKEN because the controller which it uses
291 will easily trigger RX overrun and TX underrun errors. Using
292 low I2C clock rates may partially work around those issues
293 on some systems. Another serious problem is that there is no
294 documented way to issue repeated START conditions, as needed
295 to support combined I2C messages. Use the i2c-gpio driver
296 unless your system can cope with those limitations.
299 tristate "Au1550/Au1200 SMBus interface"
300 depends on SOC_AU1550 || SOC_AU1200
302 If you say yes to this option, support will be included for the
303 Au1550 and Au1200 SMBus interface.
305 This driver can also be built as a module. If so, the module
306 will be called i2c-au1550.
308 config I2C_BLACKFIN_TWI
309 tristate "Blackfin TWI I2C support"
311 depends on !BF561 && !BF531 && !BF532 && !BF533
313 This is the I2C bus driver for Blackfin on-chip TWI interface.
315 This driver can also be built as a module. If so, the module
316 will be called i2c-bfin-twi.
318 config I2C_BLACKFIN_TWI_CLK_KHZ
319 int "Blackfin TWI I2C clock (kHz)"
320 depends on I2C_BLACKFIN_TWI
324 The unit of the TWI clock is kHz.
327 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
328 depends on (CPM1 || CPM2) && OF_I2C
330 This supports the use of the I2C interface on Freescale
331 processors with CPM1 or CPM2.
333 This driver can also be built as a module. If so, the module
334 will be called i2c-cpm.
337 tristate "DaVinci I2C driver"
338 depends on ARCH_DAVINCI
340 Support for TI DaVinci I2C controller driver.
342 This driver can also be built as a module. If so, the module
343 will be called i2c-davinci.
345 Please note that this driver might be needed to bring up other
346 devices such as DaVinci NIC.
347 For details please see http://www.ti.com/davinci
349 config I2C_DESIGNWARE
350 tristate "Synopsys DesignWare"
353 If you say yes to this option, support will be included for the
354 Synopsys DesignWare I2C adapter. Only master mode is supported.
356 This driver can also be built as a module. If so, the module
357 will be called i2c-designware.
360 tristate "GPIO-based bitbanging I2C"
361 depends on GENERIC_GPIO
364 This is a very simple bitbanging I2C driver utilizing the
365 arch-neutral GPIO API to control the SCL and SDA lines.
367 config I2C_HIGHLANDER
368 tristate "Highlander FPGA SMBus interface"
369 depends on SH_HIGHLANDER
371 If you say yes to this option, support will be included for
372 the SMBus interface located in the FPGA on various Highlander
373 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
374 FPGAs. This is wholly unrelated to the SoC I2C.
376 This driver can also be built as a module. If so, the module
377 will be called i2c-highlander.
380 tristate "IBM PPC 4xx on-chip I2C interface"
383 Say Y here if you want to use IIC peripheral found on
384 embedded IBM PPC 4xx based systems.
386 This driver can also be built as a module. If so, the module
387 will be called i2c-ibm_iic.
390 tristate "IMX I2C interface"
393 Say Y here if you want to use the IIC bus controller on
394 the Freescale i.MX/MXC processors.
396 This driver can also be built as a module. If so, the module
397 will be called i2c-imx.
400 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
401 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
403 Say Y here if you want to use the IIC bus controller on
404 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
406 This driver can also be built as a module. If so, the module
407 will be called i2c-iop3xx.
410 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
411 depends on ARCH_IXP2000
414 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
415 system and are using GPIO lines for an I2C bus.
417 This support is also available as a module. If so, the module
418 will be called i2c-ixp2000.
420 This driver is deprecated and will be dropped soon. Use i2c-gpio
424 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
427 If you say yes to this option, support will be included for the
428 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
429 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
431 This driver can also be built as a module. If so, the module
432 will be called i2c-mpc.
435 tristate "Marvell mv64xxx I2C Controller"
436 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
438 If you say yes to this option, support will be included for the
439 built-in I2C interface on the Marvell 64xxx line of host bridges.
441 This driver can also be built as a module. If so, the module
442 will be called i2c-mv64xxx.
445 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
446 depends on PLAT_NOMADIK
448 If you say yes to this option, support will be included for the
449 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
452 tristate "OpenCores I2C Controller"
453 depends on EXPERIMENTAL
455 If you say yes to this option, support will be included for the
456 OpenCores I2C controller. For details see
457 http://www.opencores.org/projects.cgi/web/i2c/overview
459 This driver can also be built as a module. If so, the module
460 will be called i2c-ocores.
463 tristate "OMAP I2C adapter"
465 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
467 If you say yes to this option, support will be included for the
468 I2C interface on the Texas Instruments OMAP1/2 family of processors.
469 Like OMAP1510/1610/1710/5912 and OMAP242x.
470 For details see http://www.ti.com/omap.
473 tristate "PA Semi SMBus interface"
474 depends on PPC_PASEMI && PCI
476 Supports the PA Semi PWRficient on-chip SMBus interfaces.
478 config I2C_PCA_PLATFORM
479 tristate "PCA9564/PCA9665 as platform device"
483 This driver supports a memory mapped Philips PCA9564/PCA9665
484 parallel bus to I2C bus controller.
486 This driver can also be built as a module. If so, the module
487 will be called i2c-pca-platform.
490 tristate "PMC MSP I2C TWI Controller"
493 This driver supports the PMC TWI controller on MSP devices.
495 This driver can also be built as module. If so, the module
496 will be called i2c-pmcmsp.
499 tristate "I2C bus support for Philips PNX targets"
500 depends on ARCH_PNX4008
502 This driver supports the Philips IP3204 I2C IP block master and/or
505 This driver can also be built as a module. If so, the module
506 will be called i2c-pnx.
509 tristate "Intel PXA2XX I2C adapter"
510 depends on ARCH_PXA || ARCH_MMP
512 If you have devices in the PXA I2C bus, say yes to this option.
513 This driver can also be built as a module. If so, the module
514 will be called i2c-pxa.
517 bool "Intel PXA2XX I2C Slave comms support"
520 Support I2C slave mode communications on the PXA I2C bus. This
521 is necessary for systems where the PXA may be a target on the
525 tristate "S3C2410 I2C Driver"
526 depends on ARCH_S3C2410 || ARCH_S3C64XX
528 Say Y here to include support for I2C controller in the
529 Samsung S3C2410 based System-on-Chip devices.
532 tristate "S6000 I2C support"
533 depends on XTENSA_VARIANT_S6000
535 This driver supports the on chip I2C device on the
536 S6000 xtensa processor family.
538 To compile this driver as a module, choose M here. The module
539 will be called i2c-s6000.
542 tristate "Renesas SH7760 I2C Controller"
543 depends on CPU_SUBTYPE_SH7760
545 This driver supports the 2 I2C interfaces on the Renesas SH7760.
547 This driver can also be built as a module. If so, the module
548 will be called i2c-sh7760.
551 tristate "SuperH Mobile I2C Controller"
554 If you say yes to this option, support will be included for the
555 built-in I2C interface on the Renesas SH-Mobile processor.
557 This driver can also be built as a module. If so, the module
558 will be called i2c-sh_mobile.
561 tristate "Simtec Generic I2C interface"
564 If you say yes to this option, support will be included for
565 the Simtec Generic I2C interface. This driver is for the
566 simple I2C bus used on newer Simtec products for general
567 I2C, such as DDC on the Simtec BBD2016A.
569 This driver can also be built as a module. If so, the module
570 will be called i2c-simtec.
573 tristate "ST Microelectronics DDC I2C interface"
575 default y if MACH_U300
577 If you say yes to this option, support will be included for the
578 I2C interface from ST Microelectronics simply called "DDC I2C"
579 supporting both I2C and DDC, used in e.g. the U300 series
582 This driver can also be built as a module. If so, the module
583 will be called i2c-stu300.
586 tristate "ARM Versatile/Realview I2C bus support"
587 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
590 Say yes if you want to support the I2C serial bus on ARMs Versatile
593 This driver can also be built as a module. If so, the module
594 will be called i2c-versatile.
597 tristate "Cavium OCTEON I2C bus support"
598 depends on CPU_CAVIUM_OCTEON
600 Say yes if you want to support the I2C serial bus on Cavium
603 This driver can also be built as a module. If so, the module
604 will be called i2c-octeon.
607 tristate "Xilinx I2C Controller"
608 depends on EXPERIMENTAL && HAS_IOMEM
610 If you say yes to this option, support will be included for the
611 Xilinx I2C controller.
613 This driver can also be built as a module. If so, the module
614 will be called xilinx_i2c.
616 comment "External I2C/SMBus adapter drivers"
619 tristate "Parallel port adapter"
624 This supports parallel port I2C adapters such as the ones made by
625 Philips or Velleman, Analog Devices evaluation boards, and more.
626 Basically any adapter using the parallel port as an I2C bus with
627 no extra chipset is supported by this driver, or could be.
629 This driver is a replacement for (and was inspired by) an older
630 driver named i2c-philips-par. The new driver supports more devices,
631 and makes it easier to add support for new devices.
633 An adapter type parameter is now mandatory. Please read the file
634 Documentation/i2c/busses/i2c-parport for details.
636 Another driver exists, named i2c-parport-light, which doesn't depend
637 on the parport driver. This is meant for embedded systems. Don't say
638 Y here if you intend to say Y or M there.
640 This support is also available as a module. If so, the module
641 will be called i2c-parport.
643 config I2C_PARPORT_LIGHT
644 tristate "Parallel port adapter (light)"
648 This supports parallel port I2C adapters such as the ones made by
649 Philips or Velleman, Analog Devices evaluation boards, and more.
650 Basically any adapter using the parallel port as an I2C bus with
651 no extra chipset is supported by this driver, or could be.
653 This driver is a light version of i2c-parport. It doesn't depend
654 on the parport driver, and uses direct I/O access instead. This
655 might be preferred on embedded systems where wasting memory for
656 the clean but heavy parport handling is not an option. The
657 drawback is a reduced portability and the impossibility to
658 daisy-chain other parallel port devices.
660 Don't say Y here if you said Y or M to i2c-parport. Saying M to
661 both is possible but both modules should not be loaded at the same
664 This support is also available as a module. If so, the module
665 will be called i2c-parport-light.
668 tristate "TAOS evaluation module"
669 depends on EXPERIMENTAL
674 This supports TAOS evaluation modules on serial port. In order to
675 use this driver, you will need the inputattach tool, which is part
676 of the input-utils package.
680 This support is also available as a module. If so, the module
681 will be called i2c-taos-evm.
684 tristate "Tiny-USB adapter"
687 If you say yes to this option, support will be included for the
688 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
689 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
691 This driver can also be built as a module. If so, the module
692 will be called i2c-tiny-usb.
694 comment "Other I2C/SMBus bus drivers"
697 tristate "Acorn IOC/IOMD I2C bus support"
698 depends on ARCH_ACORN
702 Say yes if you want to support the I2C bus on Acorn platforms.
704 If you don't know, say Y.
707 tristate "Elektor ISA card"
708 depends on ISA && BROKEN_ON_SMP
711 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
714 This support is also available as a module. If so, the module
715 will be called i2c-elektor.
718 tristate "PCA9564/PCA9665 on an ISA bus"
723 This driver supports ISA boards using the Philips PCA9564/PCA9665
724 parallel bus to I2C bus controller.
726 This driver can also be built as a module. If so, the module
727 will be called i2c-pca-isa.
729 This device is almost undetectable and using this driver on a
730 system which doesn't have this device will result in long
731 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
732 time). If unsure, say N.
735 tristate "SiByte SMBus interface"
736 depends on SIBYTE_SB1xxx_SOC
738 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
741 tristate "I2C/SMBus Test Stub"
742 depends on EXPERIMENTAL && m
745 This module may be useful to developers of SMBus client drivers,
746 especially for certain kinds of sensor chips.
748 If you do build this module, be sure to read the notes and warnings
749 in <file:Documentation/i2c/i2c-stub>.
751 If you don't know what to do here, definitely say N.
754 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
755 depends on SCx200_GPIO
758 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
760 If you don't know what to do here, say N.
762 This support is also available as a module. If so, the module
763 will be called scx200_i2c.
765 This driver is deprecated and will be dropped soon. Use i2c-gpio
766 (or scx200_acb) instead.
768 config SCx200_I2C_SCL
769 int "GPIO pin used for SCL"
770 depends on SCx200_I2C
773 Enter the GPIO pin number used for the SCL signal. This value can
774 also be specified with a module parameter.
776 config SCx200_I2C_SDA
777 int "GPIO pin used for SDA"
778 depends on SCx200_I2C
781 Enter the GPIO pin number used for the SSA signal. This value can
782 also be specified with a module parameter.
785 tristate "Geode ACCESS.bus support"
786 depends on X86_32 && PCI
788 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
789 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
791 If you don't know what to do here, say N.
793 This support is also available as a module. If so, the module
794 will be called scx200_acb.