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
59 # broke an Athlon 64 X2 Asus A8N-E with:
60 # http://redhat.com/~mingo/misc/config-Thu_Jul_17_11_34_08_CEST_2008.bad
63 Enabling this option will add specific SMBus support for the Tyan
64 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
65 over 8 different channels, where the various memory module EEPROMs
66 and temperature sensors live. Saying yes here will give you access
67 to these in addition to the trunk.
69 This driver can also be built as a module. If so, the module
70 will be called i2c-amd756-s4882.
76 If you say yes to this option, support will be included for the
77 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
79 This driver can also be built as a module. If so, the module
80 will be called i2c-amd8111.
83 tristate "Intel 82801 (ICH)"
86 If you say yes to this option, support will be included for the Intel
87 801 family of mainboard I2C interfaces. Specifically, the following
88 versions of the chipset are supported:
94 82801EB/ER (ICH5/ICH5R)
105 This driver can also be built as a module. If so, the module
106 will be called i2c-i801.
109 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/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
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
156 # broke a T60 Core2Duo with:
157 # http://redhat.com/~mingo/misc/config-Thu_Jul_17_10_47_42_CEST_2008.bad
160 Enabling this option will add specific SMBus support for the Tyan
161 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
162 over 4 different channels, where the various memory module EEPROMs
163 live. Saying yes here will give you access to these in addition
166 This driver can also be built as a module. If so, the module
167 will be called i2c-nforce2-s4985.
173 If you say yes to this option, support will be included for the
174 SiS5595 SMBus (a subset of I2C) interface.
176 This driver can also be built as a module. If so, the module
177 will be called i2c-sis5595.
180 tristate "SiS 630/730"
183 If you say yes to this option, support will be included for the
184 SiS630 and SiS730 SMBus (a subset of I2C) interface.
186 This driver can also be built as a module. If so, the module
187 will be called i2c-sis630.
193 If you say yes to this option, support will be included for the SiS
194 96x SMBus (a subset of I2C) interfaces. Specifically, the following
195 chipsets are supported:
204 This driver can also be built as a module. If so, the module
205 will be called i2c-sis96x.
208 tristate "VIA VT82C586B"
209 depends on PCI && EXPERIMENTAL
212 If you say yes to this option, support will be included for the VIA
213 82C586B I2C interface
215 This driver can also be built as a module. If so, the module
216 will be called i2c-via.
219 tristate "VIA VT82C596/82C686/82xx and CX700/VX800/VX820"
222 If you say yes to this option, support will be included for the VIA
223 VT82C596 and later SMBus interface. Specifically, the following
224 chipsets are supported:
236 This driver can also be built as a module. If so, the module
237 will be called i2c-viapro.
239 comment "Mac SMBus host controller drivers"
240 depends on PPC_CHRP || PPC_PMAC
243 tristate "CHRP Apple Hydra Mac I/O I2C interface"
244 depends on PCI && PPC_CHRP && EXPERIMENTAL
247 This supports the use of the I2C interface in the Apple Hydra Mac
248 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
251 This support is also available as a module. If so, the module
252 will be called i2c-hydra.
255 tristate "Powermac I2C interface"
259 This exposes the various PowerMac i2c interfaces to the linux i2c
260 layer and to userland. It is used by various drivers on the PowerMac
261 platform, and should generally be enabled.
263 This support is also available as a module. If so, the module
264 will be called i2c-powermac.
266 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
269 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
270 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
272 This supports the use of the I2C interface on Atmel AT91
275 This driver is BROKEN because the controller which it uses
276 will easily trigger RX overrun and TX underrun errors. Using
277 low I2C clock rates may partially work around those issues
278 on some systems. Another serious problem is that there is no
279 documented way to issue repeated START conditions, as needed
280 to support combined I2C messages. Use the i2c-gpio driver
281 unless your system can cope with those limitations.
284 tristate "Au1550/Au1200 SMBus interface"
285 depends on SOC_AU1550 || SOC_AU1200
287 If you say yes to this option, support will be included for the
288 Au1550 and Au1200 SMBus interface.
290 This driver can also be built as a module. If so, the module
291 will be called i2c-au1550.
293 config I2C_BLACKFIN_TWI
294 tristate "Blackfin TWI I2C support"
296 depends on !BF561 && !BF531 && !BF532 && !BF533
298 This is the I2C bus driver for Blackfin on-chip TWI interface.
300 This driver can also be built as a module. If so, the module
301 will be called i2c-bfin-twi.
303 config I2C_BLACKFIN_TWI_CLK_KHZ
304 int "Blackfin TWI I2C clock (kHz)"
305 depends on I2C_BLACKFIN_TWI
309 The unit of the TWI clock is kHz.
312 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
313 depends on (CPM1 || CPM2) && OF_I2C
315 This supports the use of the I2C interface on Freescale
316 processors with CPM1 or CPM2.
318 This driver can also be built as a module. If so, the module
319 will be called i2c-cpm.
322 tristate "DaVinci I2C driver"
323 depends on ARCH_DAVINCI
325 Support for TI DaVinci I2C controller driver.
327 This driver can also be built as a module. If so, the module
328 will be called i2c-davinci.
330 Please note that this driver might be needed to bring up other
331 devices such as DaVinci NIC.
332 For details please see http://www.ti.com/davinci
335 tristate "GPIO-based bitbanging I2C"
336 depends on GENERIC_GPIO
339 This is a very simple bitbanging I2C driver utilizing the
340 arch-neutral GPIO API to control the SCL and SDA lines.
342 config I2C_HIGHLANDER
343 tristate "Highlander FPGA SMBus interface"
344 depends on SH_HIGHLANDER
346 If you say yes to this option, support will be included for
347 the SMBus interface located in the FPGA on various Highlander
348 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
349 FPGAs. This is wholly unrelated to the SoC I2C.
351 This driver can also be built as a module. If so, the module
352 will be called i2c-highlander.
355 tristate "IBM PPC 4xx on-chip I2C interface"
358 Say Y here if you want to use IIC peripheral found on
359 embedded IBM PPC 4xx based systems.
361 This driver can also be built as a module. If so, the module
362 will be called i2c-ibm_iic.
365 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
366 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
368 Say Y here if you want to use the IIC bus controller on
369 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
371 This driver can also be built as a module. If so, the module
372 will be called i2c-iop3xx.
375 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
376 depends on ARCH_IXP2000
379 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
380 system and are using GPIO lines for an I2C bus.
382 This support is also available as a module. If so, the module
383 will be called i2c-ixp2000.
385 This driver is deprecated and will be dropped soon. Use i2c-gpio
389 tristate "MPC107/824x/85xx/52xx/86xx"
392 If you say yes to this option, support will be included for the
393 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
394 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
395 family processors, though interrupts are known not to work.
397 This driver can also be built as a module. If so, the module
398 will be called i2c-mpc.
401 tristate "Marvell mv64xxx I2C Controller"
402 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
404 If you say yes to this option, support will be included for the
405 built-in I2C interface on the Marvell 64xxx line of host bridges.
407 This driver can also be built as a module. If so, the module
408 will be called i2c-mv64xxx.
411 tristate "OpenCores I2C Controller"
412 depends on EXPERIMENTAL
414 If you say yes to this option, support will be included for the
415 OpenCores I2C controller. For details see
416 http://www.opencores.org/projects.cgi/web/i2c/overview
418 This driver can also be built as a module. If so, the module
419 will be called i2c-ocores.
422 tristate "OMAP I2C adapter"
424 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
426 If you say yes to this option, support will be included for the
427 I2C interface on the Texas Instruments OMAP1/2 family of processors.
428 Like OMAP1510/1610/1710/5912 and OMAP242x.
429 For details see http://www.ti.com/omap.
432 tristate "PA Semi SMBus interface"
433 depends on PPC_PASEMI && PCI
435 Supports the PA Semi PWRficient on-chip SMBus interfaces.
438 tristate "I2C bus support for Philips PNX targets"
439 depends on ARCH_PNX4008
441 This driver supports the Philips IP3204 I2C IP block master and/or
444 This driver can also be built as a module. If so, the module
445 will be called i2c-pnx.
448 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
449 depends on EXPERIMENTAL && ARCH_PXA
451 If you have devices in the PXA I2C bus, say yes to this option.
452 This driver can also be built as a module. If so, the module
453 will be called i2c-pxa.
456 bool "Intel PXA2XX I2C Slave comms support"
459 Support I2C slave mode communications on the PXA I2C bus. This
460 is necessary for systems where the PXA may be a target on the
464 tristate "S3C2410 I2C Driver"
465 depends on ARCH_S3C2410
467 Say Y here to include support for I2C controller in the
468 Samsung S3C2410 based System-on-Chip devices.
471 tristate "Renesas SH7760 I2C Controller"
472 depends on CPU_SUBTYPE_SH7760
474 This driver supports the 2 I2C interfaces on the Renesas SH7760.
476 This driver can also be built as a module. If so, the module
477 will be called i2c-sh7760.
480 tristate "SuperH Mobile I2C Controller"
483 If you say yes to this option, support will be included for the
484 built-in I2C interface on the Renesas SH-Mobile processor.
486 This driver can also be built as a module. If so, the module
487 will be called i2c-sh_mobile.
490 tristate "Simtec Generic I2C interface"
493 If you say yes to this option, support will be included for
494 the Simtec Generic I2C interface. This driver is for the
495 simple I2C bus used on newer Simtec products for general
496 I2C, such as DDC on the Simtec BBD2016A.
498 This driver can also be built as a module. If so, the module
499 will be called i2c-simtec.
502 tristate "ARM Versatile/Realview I2C bus support"
503 depends on ARCH_VERSATILE || ARCH_REALVIEW
506 Say yes if you want to support the I2C serial bus on ARMs Versatile
509 This driver can also be built as a module. If so, the module
510 will be called i2c-versatile.
512 comment "External I2C/SMBus adapter drivers"
515 tristate "Parallel port adapter"
519 This supports parallel port I2C adapters such as the ones made by
520 Philips or Velleman, Analog Devices evaluation boards, and more.
521 Basically any adapter using the parallel port as an I2C bus with
522 no extra chipset is supported by this driver, or could be.
524 This driver is a replacement for (and was inspired by) an older
525 driver named i2c-philips-par. The new driver supports more devices,
526 and makes it easier to add support for new devices.
528 An adapter type parameter is now mandatory. Please read the file
529 Documentation/i2c/busses/i2c-parport for details.
531 Another driver exists, named i2c-parport-light, which doesn't depend
532 on the parport driver. This is meant for embedded systems. Don't say
533 Y here if you intend to say Y or M there.
535 This support is also available as a module. If so, the module
536 will be called i2c-parport.
538 config I2C_PARPORT_LIGHT
539 tristate "Parallel port adapter (light)"
542 This supports parallel port I2C adapters such as the ones made by
543 Philips or Velleman, Analog Devices evaluation boards, and more.
544 Basically any adapter using the parallel port as an I2C bus with
545 no extra chipset is supported by this driver, or could be.
547 This driver is a light version of i2c-parport. It doesn't depend
548 on the parport driver, and uses direct I/O access instead. This
549 might be preferred on embedded systems where wasting memory for
550 the clean but heavy parport handling is not an option. The
551 drawback is a reduced portability and the impossibility to
552 daisy-chain other parallel port devices.
554 Don't say Y here if you said Y or M to i2c-parport. Saying M to
555 both is possible but both modules should not be loaded at the same
558 This support is also available as a module. If so, the module
559 will be called i2c-parport-light.
562 tristate "TAOS evaluation module"
563 depends on EXPERIMENTAL
568 This supports TAOS evaluation modules on serial port. In order to
569 use this driver, you will need the inputattach tool, which is part
570 of the input-utils package.
574 This support is also available as a module. If so, the module
575 will be called i2c-taos-evm.
578 tristate "Tiny-USB adapter"
581 If you say yes to this option, support will be included for the
582 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
583 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
585 This driver can also be built as a module. If so, the module
586 will be called i2c-tiny-usb.
588 comment "Graphics adapter I2C/DDC channel drivers"
596 If you say yes to this option, support will be included for the
597 Voodoo 3 I2C interface.
599 This driver can also be built as a module. If so, the module
600 will be called i2c-voodoo3.
602 comment "Other I2C/SMBus bus drivers"
605 tristate "Acorn IOC/IOMD I2C bus support"
606 depends on ARCH_ACORN
610 Say yes if you want to support the I2C bus on Acorn platforms.
612 If you don't know, say Y.
615 tristate "Elektor ISA card"
616 depends on ISA && BROKEN_ON_SMP
619 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
622 This support is also available as a module. If so, the module
623 will be called i2c-elektor.
626 tristate "PCA9564 on an ISA bus"
631 This driver supports ISA boards using the Philips PCA9564
632 parallel bus to I2C bus controller.
634 This driver can also be built as a module. If so, the module
635 will be called i2c-pca-isa.
637 This device is almost undetectable and using this driver on a
638 system which doesn't have this device will result in long
639 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
640 time). If unsure, say N.
642 config I2C_PCA_PLATFORM
643 tristate "PCA9564 as platform device"
647 This driver supports a memory mapped Philips PCA9564
648 parallel bus to I2C bus controller.
650 This driver can also be built as a module. If so, the module
651 will be called i2c-pca-platform.
654 tristate "PMC MSP I2C TWI Controller"
657 This driver supports the PMC TWI controller on MSP devices.
659 This driver can also be built as module. If so, the module
660 will be called i2c-pmcmsp.
663 tristate "SiByte SMBus interface"
664 depends on SIBYTE_SB1xxx_SOC
666 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
669 tristate "I2C/SMBus Test Stub"
670 depends on EXPERIMENTAL && m
673 This module may be useful to developers of SMBus client drivers,
674 especially for certain kinds of sensor chips.
676 If you do build this module, be sure to read the notes and warnings
677 in <file:Documentation/i2c/i2c-stub>.
679 If you don't know what to do here, definitely say N.
682 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
683 depends on SCx200_GPIO
686 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
688 If you don't know what to do here, say N.
690 This support is also available as a module. If so, the module
691 will be called scx200_i2c.
693 This driver is deprecated and will be dropped soon. Use i2c-gpio
694 (or scx200_acb) instead.
696 config SCx200_I2C_SCL
697 int "GPIO pin used for SCL"
698 depends on SCx200_I2C
701 Enter the GPIO pin number used for the SCL signal. This value can
702 also be specified with a module parameter.
704 config SCx200_I2C_SDA
705 int "GPIO pin used for SDA"
706 depends on SCx200_I2C
709 Enter the GPIO pin number used for the SSA signal. This value can
710 also be specified with a module parameter.
713 tristate "Geode ACCESS.bus support"
714 depends on X86_32 && PCI
716 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
717 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
719 If you don't know what to do here, say N.
721 This support is also available as a module. If so, the module
722 will be called scx200_acb.
725 tristate "I2C bus on serial port"
726 depends on SERIAL_8250
728 This driver supports I2C bus on serial port (Aldebaran)