2 # Sensor device configuration
5 menu "I2C Hardware Bus support"
11 If you say yes to this option, support will be included for the SMB
12 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
13 controller is part of the 7101 device, which is an ACPI-compliant
14 Power Management Unit (PMU).
16 This driver can also be built as a module. If so, the module
17 will be called i2c-ali1535.
21 depends on PCI && EXPERIMENTAL
23 If you say yes to this option, support will be included for the SMB
24 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
25 controller is part of the 7101 device, which is an ACPI-compliant
26 Power Management Unit (PMU).
28 This driver can also be built as a module. If so, the module
29 will be called i2c-ali1563.
35 If you say yes to this option, support will be included for the
36 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
38 This driver can also be built as a module. If so, the module
39 will be called i2c-ali15x3.
42 tristate "AMD 756/766/768/8111 and nVidia nForce"
45 If you say yes to this option, support will be included for the AMD
46 756/766/768 mainboard I2C interfaces. The driver also includes
47 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
48 the nVidia nForce I2C interface.
50 This driver can also be built as a module. If so, the module
51 will be called i2c-amd756.
53 config I2C_AMD756_S4882
54 tristate "SMBus multiplexing on the Tyan S4882"
55 depends on I2C_AMD756 && EXPERIMENTAL
57 Enabling this option will add specific SMBus support for the Tyan
58 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
59 over 8 different channels, where the various memory module EEPROMs
60 and temperature sensors live. Saying yes here will give you access
61 to these in addition to the trunk.
63 This driver can also be built as a module. If so, the module
64 will be called i2c-amd756-s4882.
70 If you say yes to this option, support will be included for the
71 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
73 This driver can also be built as a module. If so, the module
74 will be called i2c-amd8111.
77 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
78 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
80 This supports the use of the I2C interface on Atmel AT91
83 This driver is BROKEN because the controller which it uses
84 will easily trigger RX overrun and TX underrun errors. Using
85 low I2C clock rates may partially work around those issues
86 on some systems. Another serious problem is that there is no
87 documented way to issue repeated START conditions, as needed
88 to support combined I2C messages. Use the i2c-gpio driver
89 unless your system can cope with those limitations.
92 tristate "Au1550/Au1200 SMBus interface"
93 depends on SOC_AU1550 || SOC_AU1200
95 If you say yes to this option, support will be included for the
96 Au1550 and Au1200 SMBus interface.
98 This driver can also be built as a module. If so, the module
99 will be called i2c-au1550.
101 config I2C_BLACKFIN_TWI
102 tristate "Blackfin TWI I2C support"
105 This is the TWI I2C device driver for Blackfin BF522, BF525,
106 BF527, BF534, BF536, BF537 and BF54x. For other Blackfin processors,
107 please don't use this driver.
109 This driver can also be built as a module. If so, the module
110 will be called i2c-bfin-twi.
112 config I2C_BLACKFIN_TWI_CLK_KHZ
113 int "Blackfin TWI I2C clock (kHz)"
114 depends on I2C_BLACKFIN_TWI
118 The unit of the TWI clock is kHz.
121 tristate "DaVinci I2C driver"
122 depends on ARCH_DAVINCI
124 Support for TI DaVinci I2C controller driver.
126 This driver can also be built as a module. If so, the module
127 will be called i2c-davinci.
129 Please note that this driver might be needed to bring up other
130 devices such as DaVinci NIC.
131 For details please see http://www.ti.com/davinci
134 tristate "Elektor ISA card"
135 depends on ISA && BROKEN_ON_SMP
138 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
141 This support is also available as a module. If so, the module
142 will be called i2c-elektor.
145 tristate "GPIO-based bitbanging I2C"
146 depends on GENERIC_GPIO
149 This is a very simple bitbanging I2C driver utilizing the
150 arch-neutral GPIO API to control the SCL and SDA lines.
153 tristate "CHRP Apple Hydra Mac I/O I2C interface"
154 depends on PCI && PPC_CHRP && EXPERIMENTAL
157 This supports the use of the I2C interface in the Apple Hydra Mac
158 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
161 This support is also available as a module. If so, the module
162 will be called i2c-hydra.
165 tristate "Intel 82801 (ICH)"
168 If you say yes to this option, support will be included for the Intel
169 801 family of mainboard I2C interfaces. Specifically, the following
170 versions of the chipset are supported:
176 82801EB/ER (ICH5/ICH5R)
186 This driver can also be built as a module. If so, the module
187 will be called i2c-i801.
190 tristate "Intel 810/815 (DEPRECATED)"
195 If you say yes to this option, support will be included for the Intel
196 810/815 family of mainboard I2C interfaces. Specifically, the
197 following versions of the chipset are supported:
204 This driver is deprecated in favor of the i810fb and intelfb drivers.
206 This driver can also be built as a module. If so, the module
207 will be called i2c-i810.
210 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
211 depends on EXPERIMENTAL && ARCH_PXA
213 If you have devices in the PXA I2C bus, say yes to this option.
214 This driver can also be built as a module. If so, the module
215 will be called i2c-pxa.
218 bool "Intel PXA2XX I2C Slave comms support"
221 Support I2C slave mode communications on the PXA I2C bus. This
222 is necessary for systems where the PXA may be a target on the
226 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
229 If you say yes to this option, support will be included for the Intel
230 PIIX4 family of mainboard I2C interfaces. Specifically, the following
231 versions of the chipset are supported (note that Serverworks is part
247 This driver can also be built as a module. If so, the module
248 will be called i2c-piix4.
251 tristate "IBM PPC 4xx on-chip I2C interface"
254 Say Y here if you want to use IIC peripheral found on
255 embedded IBM PPC 4xx based systems.
257 This driver can also be built as a module. If so, the module
258 will be called i2c-ibm_iic.
261 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
262 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
264 Say Y here if you want to use the IIC bus controller on
265 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
267 This driver can also be built as a module. If so, the module
268 will be called i2c-iop3xx.
271 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
272 depends on ARCH_IXP2000
275 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
276 system and are using GPIO lines for an I2C bus.
278 This support is also available as a module. If so, the module
279 will be called i2c-ixp2000.
281 This driver is deprecated and will be dropped soon. Use i2c-gpio
285 tristate "Powermac I2C interface"
289 This exposes the various PowerMac i2c interfaces to the linux i2c
290 layer and to userland. It is used by various drivers on the PowerMac
291 platform, and should generally be enabled.
293 This support is also available as a module. If so, the module
294 will be called i2c-powermac.
297 tristate "MPC107/824x/85xx/52xx/86xx"
300 If you say yes to this option, support will be included for the
301 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
302 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
303 family processors, though interrupts are known not to work.
305 This driver can also be built as a module. If so, the module
306 will be called i2c-mpc.
309 tristate "Nvidia nForce2, nForce3 and nForce4"
312 If you say yes to this option, support will be included for the Nvidia
313 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
315 This driver can also be built as a module. If so, the module
316 will be called i2c-nforce2.
319 tristate "OpenCores I2C Controller"
320 depends on EXPERIMENTAL
322 If you say yes to this option, support will be included for the
323 OpenCores I2C controller. For details see
324 http://www.opencores.org/projects.cgi/web/i2c/overview
326 This driver can also be built as a module. If so, the module
327 will be called i2c-ocores.
330 tristate "OMAP I2C adapter"
332 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
334 If you say yes to this option, support will be included for the
335 I2C interface on the Texas Instruments OMAP1/2/3 family of
337 Like OMAP1510/1610/1710/5912, OMAP242x, OMAP34x and OMAP35x.
338 For details see http://www.ti.com/omap.
340 config I2C2_OMAP_BEAGLE
341 bool "Enable I2C2 for OMAP3 BeagleBoard"
342 depends on ARCH_OMAP && MACH_OMAP3_BEAGLE
346 Say Y here if you want to enable I2C bus 2 at OMAP3 based
348 I2C2 at BeagleBoard is connected to expansion connector, i.e. unused
349 if nothing is connected to this connector. As internal OMAP3 pull up
350 resistors are not strong enough, enabled but unused I2C2 bus results
351 in error messages (e.g. I2C timeouts). Enable this only if you have
352 something connected to I2C2 at board's expansion connector and this
353 extension has additional pull up resistors for I2C2 bus.
357 tristate "Parallel port adapter"
361 This supports parallel port I2C adapters such as the ones made by
362 Philips or Velleman, Analog Devices evaluation boards, and more.
363 Basically any adapter using the parallel port as an I2C bus with
364 no extra chipset is supported by this driver, or could be.
366 This driver is a replacement for (and was inspired by) an older
367 driver named i2c-philips-par. The new driver supports more devices,
368 and makes it easier to add support for new devices.
370 An adapter type parameter is now mandatory. Please read the file
371 Documentation/i2c/busses/i2c-parport for details.
373 Another driver exists, named i2c-parport-light, which doesn't depend
374 on the parport driver. This is meant for embedded systems. Don't say
375 Y here if you intend to say Y or M there.
377 This support is also available as a module. If so, the module
378 will be called i2c-parport.
380 config I2C_PARPORT_LIGHT
381 tristate "Parallel port adapter (light)"
384 This supports parallel port I2C adapters such as the ones made by
385 Philips or Velleman, Analog Devices evaluation boards, and more.
386 Basically any adapter using the parallel port as an I2C bus with
387 no extra chipset is supported by this driver, or could be.
389 This driver is a light version of i2c-parport. It doesn't depend
390 on the parport driver, and uses direct I/O access instead. This
391 might be preferred on embedded systems where wasting memory for
392 the clean but heavy parport handling is not an option. The
393 drawback is a reduced portability and the impossibility to
394 daisy-chain other parallel port devices.
396 Don't say Y here if you said Y or M to i2c-parport. Saying M to
397 both is possible but both modules should not be loaded at the same
400 This support is also available as a module. If so, the module
401 will be called i2c-parport-light.
404 tristate "PA Semi SMBus interface"
405 depends on PPC_PASEMI && PCI
407 Supports the PA Semi PWRficient on-chip SMBus interfaces.
410 tristate "S3/VIA (Pro)Savage (DEPRECATED)"
415 If you say yes to this option, support will be included for the
416 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
419 S3/VIA KM266/VT8375 aka ProSavage8
420 S3/VIA KM133/VT8365 aka Savage4
422 This driver is deprecated in favor of the savagefb driver.
424 This support is also available as a module. If so, the module
425 will be called i2c-prosavage.
428 tristate "S3C2410 I2C Driver"
429 depends on ARCH_S3C2410
431 Say Y here to include support for I2C controller in the
432 Samsung S3C2410 based System-on-Chip devices.
435 tristate "S3 Savage 4 (DEPRECATED)"
440 If you say yes to this option, support will be included for the
441 S3 Savage 4 I2C interface.
443 This driver is deprecated in favor of the savagefb driver.
445 This driver can also be built as a module. If so, the module
446 will be called i2c-savage4.
449 tristate "SiByte SMBus interface"
450 depends on SIBYTE_SB1xxx_SOC
452 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
455 tristate "Simtec Generic I2C interface"
458 If you say yes to this option, support will be included for
459 the Simtec Generic I2C interface. This driver is for the
460 simple I2C bus used on newer Simtec products for general
461 I2C, such as DDC on the Simtec BBD2016A.
463 This driver can also be built as a module. If so, the module
464 will be called i2c-simtec.
467 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
468 depends on SCx200_GPIO
471 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
473 If you don't know what to do here, say N.
475 This support is also available as a module. If so, the module
476 will be called scx200_i2c.
478 This driver is deprecated and will be dropped soon. Use i2c-gpio
479 (or scx200_acb) instead.
481 config SCx200_I2C_SCL
482 int "GPIO pin used for SCL"
483 depends on SCx200_I2C
486 Enter the GPIO pin number used for the SCL signal. This value can
487 also be specified with a module parameter.
489 config SCx200_I2C_SDA
490 int "GPIO pin used for SDA"
491 depends on SCx200_I2C
494 Enter the GPIO pin number used for the SSA signal. This value can
495 also be specified with a module parameter.
498 tristate "Geode ACCESS.bus support"
499 depends on X86_32 && PCI
501 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
502 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
504 If you don't know what to do here, say N.
506 This support is also available as a module. If so, the module
507 will be called scx200_acb.
513 If you say yes to this option, support will be included for the
514 SiS5595 SMBus (a subset of I2C) interface.
516 This driver can also be built as a module. If so, the module
517 will be called i2c-sis5595.
520 tristate "SiS 630/730"
523 If you say yes to this option, support will be included for the
524 SiS630 and SiS730 SMBus (a subset of I2C) interface.
526 This driver can also be built as a module. If so, the module
527 will be called i2c-sis630.
533 If you say yes to this option, support will be included for the SiS
534 96x SMBus (a subset of I2C) interfaces. Specifically, the following
535 chipsets are supported:
544 This driver can also be built as a module. If so, the module
545 will be called i2c-sis96x.
548 tristate "TAOS evaluation module"
549 depends on EXPERIMENTAL
554 This supports TAOS evaluation modules on serial port. In order to
555 use this driver, you will need the inputattach tool, which is part
556 of the input-utils package.
560 This support is also available as a module. If so, the module
561 will be called i2c-taos-evm.
564 tristate "I2C/SMBus Test Stub"
565 depends on EXPERIMENTAL && m
568 This module may be useful to developers of SMBus client drivers,
569 especially for certain kinds of sensor chips.
571 If you do build this module, be sure to read the notes and warnings
572 in <file:Documentation/i2c/i2c-stub>.
574 If you don't know what to do here, definitely say N.
577 tristate "I2C-Tiny-USB"
580 If you say yes to this option, support will be included for the
581 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
582 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
584 This driver can also be built as a module. If so, the module
585 will be called i2c-tiny-usb.
588 tristate "ARM Versatile/Realview I2C bus support"
589 depends on ARCH_VERSATILE || ARCH_REALVIEW
592 Say yes if you want to support the I2C serial bus on ARMs Versatile
595 This driver can also be built as a module. If so, the module
596 will be called i2c-versatile.
599 tristate "Acorn IOC/IOMD I2C bus support"
600 depends on ARCH_ACORN
604 Say yes if you want to support the I2C bus on Acorn platforms.
606 If you don't know, say Y.
609 tristate "VIA 82C586B"
610 depends on PCI && EXPERIMENTAL
613 If you say yes to this option, support will be included for the VIA
614 82C586B I2C interface
616 This driver can also be built as a module. If so, the module
617 will be called i2c-via.
620 tristate "VIA VT82C596/82C686/82xx and CX700"
623 If you say yes to this option, support will be included for the VIA
624 VT82C596 and later SMBus interface. Specifically, the following
625 chipsets are supported:
635 This driver can also be built as a module. If so, the module
636 will be called i2c-viapro.
643 If you say yes to this option, support will be included for the
644 Voodoo 3 I2C interface.
646 This driver can also be built as a module. If so, the module
647 will be called i2c-voodoo3.
650 tristate "PCA9564 on an ISA bus"
655 This driver supports ISA boards using the Philips PCA9564
656 parallel bus to I2C bus controller.
658 This driver can also be built as a module. If so, the module
659 will be called i2c-pca-isa.
661 This device is almost undetectable and using this driver on a
662 system which doesn't have this device will result in long
663 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
664 time). If unsure, say N.
666 config I2C_PCA_PLATFORM
667 tristate "PCA9564 as platform device"
671 This driver supports a memory mapped Philips PCA9564
672 parallel bus to I2C bus controller.
674 This driver can also be built as a module. If so, the module
675 will be called i2c-pca-platform.
678 tristate "Marvell mv64xxx I2C Controller"
679 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
681 If you say yes to this option, support will be included for the
682 built-in I2C interface on the Marvell 64xxx line of host bridges.
684 This driver can also be built as a module. If so, the module
685 will be called i2c-mv64xxx.
688 tristate "I2C bus support for Philips PNX targets"
689 depends on ARCH_PNX4008
691 This driver supports the Philips IP3204 I2C IP block master and/or
694 This driver can also be built as a module. If so, the module
695 will be called i2c-pnx.
698 tristate "PMC MSP I2C TWI Controller"
701 This driver supports the PMC TWI controller on MSP devices.
703 This driver can also be built as module. If so, the module
704 will be called i2c-pmcmsp.
707 tristate "Renesas SH7760 I2C Controller"
708 depends on CPU_SUBTYPE_SH7760
710 This driver supports the 2 I2C interfaces on the Renesas SH7760.
712 This driver can also be built as a module. If so, the module
713 will be called i2c-sh7760.
716 tristate "SuperH Mobile I2C Controller"
719 If you say yes to this option, support will be included for the
720 built-in I2C interface on the Renesas SH-Mobile processor.
722 This driver can also be built as a module. If so, the module
723 will be called i2c-sh_mobile.