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)"
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)
102 This driver can also be built as a module. If so, the module
103 will be called i2c-i801.
106 tristate "Intel SCH SMBus 1.0"
109 Say Y here if you want to use SMBus controller on the Intel SCH
112 This driver can also be built as a module. If so, the module
113 will be called i2c-isch.
116 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
119 If you say yes to this option, support will be included for the Intel
120 PIIX4 family of mainboard I2C interfaces. Specifically, the following
121 versions of the chipset are supported (note that Serverworks is part
137 This driver can also be built as a module. If so, the module
138 will be called i2c-piix4.
141 tristate "Nvidia nForce2, nForce3 and nForce4"
144 If you say yes to this option, support will be included for the Nvidia
145 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
147 This driver can also be built as a module. If so, the module
148 will be called i2c-nforce2.
150 config I2C_NFORCE2_S4985
151 tristate "SMBus multiplexing on the Tyan S4985"
152 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
154 Enabling this option will add specific SMBus support for the Tyan
155 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
156 over 4 different channels, where the various memory module EEPROMs
157 live. Saying yes here will give you access to these in addition
160 This driver can also be built as a module. If so, the module
161 will be called i2c-nforce2-s4985.
167 If you say yes to this option, support will be included for the
168 SiS5595 SMBus (a subset of I2C) interface.
170 This driver can also be built as a module. If so, the module
171 will be called i2c-sis5595.
174 tristate "SiS 630/730"
177 If you say yes to this option, support will be included for the
178 SiS630 and SiS730 SMBus (a subset of I2C) interface.
180 This driver can also be built as a module. If so, the module
181 will be called i2c-sis630.
187 If you say yes to this option, support will be included for the SiS
188 96x SMBus (a subset of I2C) interfaces. Specifically, the following
189 chipsets are supported:
198 This driver can also be built as a module. If so, the module
199 will be called i2c-sis96x.
202 tristate "VIA VT82C586B"
203 depends on PCI && EXPERIMENTAL
206 If you say yes to this option, support will be included for the VIA
207 82C586B I2C interface
209 This driver can also be built as a module. If so, the module
210 will be called i2c-via.
213 tristate "VIA VT82C596/82C686/82xx and CX700/VX800/VX820"
216 If you say yes to this option, support will be included for the VIA
217 VT82C596 and later SMBus interface. Specifically, the following
218 chipsets are supported:
230 This driver can also be built as a module. If so, the module
231 will be called i2c-viapro.
233 comment "Mac SMBus host controller drivers"
234 depends on PPC_CHRP || PPC_PMAC
237 tristate "CHRP Apple Hydra Mac I/O I2C interface"
238 depends on PCI && PPC_CHRP && EXPERIMENTAL
241 This supports the use of the I2C interface in the Apple Hydra Mac
242 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
245 This support is also available as a module. If so, the module
246 will be called i2c-hydra.
249 tristate "Powermac I2C interface"
253 This exposes the various PowerMac i2c interfaces to the linux i2c
254 layer and to userland. It is used by various drivers on the PowerMac
255 platform, and should generally be enabled.
257 This support is also available as a module. If so, the module
258 will be called i2c-powermac.
260 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
263 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
264 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
266 This supports the use of the I2C interface on Atmel AT91
269 This driver is BROKEN because the controller which it uses
270 will easily trigger RX overrun and TX underrun errors. Using
271 low I2C clock rates may partially work around those issues
272 on some systems. Another serious problem is that there is no
273 documented way to issue repeated START conditions, as needed
274 to support combined I2C messages. Use the i2c-gpio driver
275 unless your system can cope with those limitations.
278 tristate "Au1550/Au1200 SMBus interface"
279 depends on SOC_AU1550 || SOC_AU1200
281 If you say yes to this option, support will be included for the
282 Au1550 and Au1200 SMBus interface.
284 This driver can also be built as a module. If so, the module
285 will be called i2c-au1550.
287 config I2C_BLACKFIN_TWI
288 tristate "Blackfin TWI I2C support"
290 depends on !BF561 && !BF531 && !BF532 && !BF533
292 This is the I2C bus driver for Blackfin on-chip TWI interface.
294 This driver can also be built as a module. If so, the module
295 will be called i2c-bfin-twi.
297 config I2C_BLACKFIN_TWI_CLK_KHZ
298 int "Blackfin TWI I2C clock (kHz)"
299 depends on I2C_BLACKFIN_TWI
303 The unit of the TWI clock is kHz.
306 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
307 depends on (CPM1 || CPM2) && OF_I2C
309 This supports the use of the I2C interface on Freescale
310 processors with CPM1 or CPM2.
312 This driver can also be built as a module. If so, the module
313 will be called i2c-cpm.
316 tristate "DaVinci I2C driver"
317 depends on ARCH_DAVINCI
319 Support for TI DaVinci I2C controller driver.
321 This driver can also be built as a module. If so, the module
322 will be called i2c-davinci.
324 Please note that this driver might be needed to bring up other
325 devices such as DaVinci NIC.
326 For details please see http://www.ti.com/davinci
329 tristate "GPIO-based bitbanging I2C"
330 depends on GENERIC_GPIO
333 This is a very simple bitbanging I2C driver utilizing the
334 arch-neutral GPIO API to control the SCL and SDA lines.
336 config I2C_HIGHLANDER
337 tristate "Highlander FPGA SMBus interface"
338 depends on SH_HIGHLANDER
340 If you say yes to this option, support will be included for
341 the SMBus interface located in the FPGA on various Highlander
342 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
343 FPGAs. This is wholly unrelated to the SoC I2C.
345 This driver can also be built as a module. If so, the module
346 will be called i2c-highlander.
349 tristate "IBM PPC 4xx on-chip I2C interface"
352 Say Y here if you want to use IIC peripheral found on
353 embedded IBM PPC 4xx based systems.
355 This driver can also be built as a module. If so, the module
356 will be called i2c-ibm_iic.
359 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
360 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
362 Say Y here if you want to use the IIC bus controller on
363 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
365 This driver can also be built as a module. If so, the module
366 will be called i2c-iop3xx.
369 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
370 depends on ARCH_IXP2000
373 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
374 system and are using GPIO lines for an I2C bus.
376 This support is also available as a module. If so, the module
377 will be called i2c-ixp2000.
379 This driver is deprecated and will be dropped soon. Use i2c-gpio
383 tristate "MPC107/824x/85xx/52xx/86xx"
386 If you say yes to this option, support will be included for the
387 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
388 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
389 family processors, though interrupts are known not to work.
391 This driver can also be built as a module. If so, the module
392 will be called i2c-mpc.
395 tristate "Marvell mv64xxx I2C Controller"
396 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
398 If you say yes to this option, support will be included for the
399 built-in I2C interface on the Marvell 64xxx line of host bridges.
401 This driver can also be built as a module. If so, the module
402 will be called i2c-mv64xxx.
405 tristate "OpenCores I2C Controller"
406 depends on EXPERIMENTAL
408 If you say yes to this option, support will be included for the
409 OpenCores I2C controller. For details see
410 http://www.opencores.org/projects.cgi/web/i2c/overview
412 This driver can also be built as a module. If so, the module
413 will be called i2c-ocores.
416 tristate "OMAP I2C adapter"
418 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
420 If you say yes to this option, support will be included for the
421 I2C interface on the Texas Instruments OMAP1/2/3 family of
423 Like OMAP1510/1610/1710/5912, OMAP242x, OMAP34x and OMAP35x.
424 For details see http://www.ti.com/omap.
426 config I2C2_OMAP_BEAGLE
427 bool "Enable I2C2 for OMAP3 BeagleBoard"
428 depends on ARCH_OMAP && MACH_OMAP3_BEAGLE
432 Say Y here if you want to enable I2C bus 2 at OMAP3 based
434 I2C2 at BeagleBoard is connected to expansion connector, i.e. unused
435 if nothing is connected to this connector. As internal OMAP3 pull up
436 resistors are not strong enough, enabled but unused I2C2 bus results
437 in error messages (e.g. I2C timeouts). Enable this only if you have
438 something connected to I2C2 at board's expansion connector and this
439 extension has additional pull up resistors for I2C2 bus.
442 tristate "PA Semi SMBus interface"
443 depends on PPC_PASEMI && PCI
445 Supports the PA Semi PWRficient on-chip SMBus interfaces.
448 tristate "I2C bus support for Philips PNX targets"
449 depends on ARCH_PNX4008
451 This driver supports the Philips IP3204 I2C IP block master and/or
454 This driver can also be built as a module. If so, the module
455 will be called i2c-pnx.
458 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
459 depends on EXPERIMENTAL && ARCH_PXA
461 If you have devices in the PXA I2C bus, say yes to this option.
462 This driver can also be built as a module. If so, the module
463 will be called i2c-pxa.
466 bool "Intel PXA2XX I2C Slave comms support"
469 Support I2C slave mode communications on the PXA I2C bus. This
470 is necessary for systems where the PXA may be a target on the
474 tristate "S3C2410 I2C Driver"
475 depends on ARCH_S3C2410
477 Say Y here to include support for I2C controller in the
478 Samsung S3C2410 based System-on-Chip devices.
481 tristate "Renesas SH7760 I2C Controller"
482 depends on CPU_SUBTYPE_SH7760
484 This driver supports the 2 I2C interfaces on the Renesas SH7760.
486 This driver can also be built as a module. If so, the module
487 will be called i2c-sh7760.
490 tristate "SuperH Mobile I2C Controller"
493 If you say yes to this option, support will be included for the
494 built-in I2C interface on the Renesas SH-Mobile processor.
496 This driver can also be built as a module. If so, the module
497 will be called i2c-sh_mobile.
500 tristate "Simtec Generic I2C interface"
503 If you say yes to this option, support will be included for
504 the Simtec Generic I2C interface. This driver is for the
505 simple I2C bus used on newer Simtec products for general
506 I2C, such as DDC on the Simtec BBD2016A.
508 This driver can also be built as a module. If so, the module
509 will be called i2c-simtec.
512 tristate "ARM Versatile/Realview I2C bus support"
513 depends on ARCH_VERSATILE || ARCH_REALVIEW
516 Say yes if you want to support the I2C serial bus on ARMs Versatile
519 This driver can also be built as a module. If so, the module
520 will be called i2c-versatile.
522 comment "External I2C/SMBus adapter drivers"
525 tristate "Parallel port adapter"
529 This supports parallel port I2C adapters such as the ones made by
530 Philips or Velleman, Analog Devices evaluation boards, and more.
531 Basically any adapter using the parallel port as an I2C bus with
532 no extra chipset is supported by this driver, or could be.
534 This driver is a replacement for (and was inspired by) an older
535 driver named i2c-philips-par. The new driver supports more devices,
536 and makes it easier to add support for new devices.
538 An adapter type parameter is now mandatory. Please read the file
539 Documentation/i2c/busses/i2c-parport for details.
541 Another driver exists, named i2c-parport-light, which doesn't depend
542 on the parport driver. This is meant for embedded systems. Don't say
543 Y here if you intend to say Y or M there.
545 This support is also available as a module. If so, the module
546 will be called i2c-parport.
548 config I2C_PARPORT_LIGHT
549 tristate "Parallel port adapter (light)"
552 This supports parallel port I2C adapters such as the ones made by
553 Philips or Velleman, Analog Devices evaluation boards, and more.
554 Basically any adapter using the parallel port as an I2C bus with
555 no extra chipset is supported by this driver, or could be.
557 This driver is a light version of i2c-parport. It doesn't depend
558 on the parport driver, and uses direct I/O access instead. This
559 might be preferred on embedded systems where wasting memory for
560 the clean but heavy parport handling is not an option. The
561 drawback is a reduced portability and the impossibility to
562 daisy-chain other parallel port devices.
564 Don't say Y here if you said Y or M to i2c-parport. Saying M to
565 both is possible but both modules should not be loaded at the same
568 This support is also available as a module. If so, the module
569 will be called i2c-parport-light.
572 tristate "TAOS evaluation module"
573 depends on EXPERIMENTAL
578 This supports TAOS evaluation modules on serial port. In order to
579 use this driver, you will need the inputattach tool, which is part
580 of the input-utils package.
584 This support is also available as a module. If so, the module
585 will be called i2c-taos-evm.
588 tristate "Tiny-USB adapter"
591 If you say yes to this option, support will be included for the
592 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
593 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
595 This driver can also be built as a module. If so, the module
596 will be called i2c-tiny-usb.
598 comment "Graphics adapter I2C/DDC channel drivers"
606 If you say yes to this option, support will be included for the
607 Voodoo 3 I2C interface.
609 This driver can also be built as a module. If so, the module
610 will be called i2c-voodoo3.
612 comment "Other I2C/SMBus bus drivers"
615 tristate "Acorn IOC/IOMD I2C bus support"
616 depends on ARCH_ACORN
620 Say yes if you want to support the I2C bus on Acorn platforms.
622 If you don't know, say Y.
625 tristate "Elektor ISA card"
626 depends on ISA && BROKEN_ON_SMP
629 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
632 This support is also available as a module. If so, the module
633 will be called i2c-elektor.
636 tristate "PCA9564 on an ISA bus"
641 This driver supports ISA boards using the Philips PCA9564
642 parallel bus to I2C bus controller.
644 This driver can also be built as a module. If so, the module
645 will be called i2c-pca-isa.
647 This device is almost undetectable and using this driver on a
648 system which doesn't have this device will result in long
649 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
650 time). If unsure, say N.
652 config I2C_PCA_PLATFORM
653 tristate "PCA9564 as platform device"
657 This driver supports a memory mapped Philips PCA9564
658 parallel bus to I2C bus controller.
660 This driver can also be built as a module. If so, the module
661 will be called i2c-pca-platform.
664 tristate "PMC MSP I2C TWI Controller"
667 This driver supports the PMC TWI controller on MSP devices.
669 This driver can also be built as module. If so, the module
670 will be called i2c-pmcmsp.
673 tristate "SiByte SMBus interface"
674 depends on SIBYTE_SB1xxx_SOC
676 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
679 tristate "I2C/SMBus Test Stub"
680 depends on EXPERIMENTAL && m
683 This module may be useful to developers of SMBus client drivers,
684 especially for certain kinds of sensor chips.
686 If you do build this module, be sure to read the notes and warnings
687 in <file:Documentation/i2c/i2c-stub>.
689 If you don't know what to do here, definitely say N.
692 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
693 depends on SCx200_GPIO
696 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
698 If you don't know what to do here, say N.
700 This support is also available as a module. If so, the module
701 will be called scx200_i2c.
703 This driver is deprecated and will be dropped soon. Use i2c-gpio
704 (or scx200_acb) instead.
706 config SCx200_I2C_SCL
707 int "GPIO pin used for SCL"
708 depends on SCx200_I2C
711 Enter the GPIO pin number used for the SCL signal. This value can
712 also be specified with a module parameter.
714 config SCx200_I2C_SDA
715 int "GPIO pin used for SDA"
716 depends on SCx200_I2C
719 Enter the GPIO pin number used for the SSA signal. This value can
720 also be specified with a module parameter.
723 tristate "Geode ACCESS.bus support"
724 depends on X86_32 && PCI
726 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
727 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
729 If you don't know what to do here, say N.
731 This support is also available as a module. If so, the module
732 will be called scx200_acb.