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 && 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)
101 This driver can also be built as a module. If so, the module
102 will be called i2c-i801.
105 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
108 If you say yes to this option, support will be included for the Intel
109 PIIX4 family of mainboard I2C interfaces. Specifically, the following
110 versions of the chipset are supported (note that Serverworks is part
126 This driver can also be built as a module. If so, the module
127 will be called i2c-piix4.
130 tristate "Nvidia nForce2, nForce3 and nForce4"
133 If you say yes to this option, support will be included for the Nvidia
134 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
136 This driver can also be built as a module. If so, the module
137 will be called i2c-nforce2.
139 config I2C_NFORCE2_S4985
140 tristate "SMBus multiplexing on the Tyan S4985"
141 depends on I2C_NFORCE2 && EXPERIMENTAL
143 Enabling this option will add specific SMBus support for the Tyan
144 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
145 over 4 different channels, where the various memory module EEPROMs
146 live. Saying yes here will give you access to these in addition
149 This driver can also be built as a module. If so, the module
150 will be called i2c-nforce2-s4985.
156 If you say yes to this option, support will be included for the
157 SiS5595 SMBus (a subset of I2C) interface.
159 This driver can also be built as a module. If so, the module
160 will be called i2c-sis5595.
163 tristate "SiS 630/730"
166 If you say yes to this option, support will be included for the
167 SiS630 and SiS730 SMBus (a subset of I2C) interface.
169 This driver can also be built as a module. If so, the module
170 will be called i2c-sis630.
176 If you say yes to this option, support will be included for the SiS
177 96x SMBus (a subset of I2C) interfaces. Specifically, the following
178 chipsets are supported:
187 This driver can also be built as a module. If so, the module
188 will be called i2c-sis96x.
191 tristate "VIA VT82C586B"
192 depends on PCI && EXPERIMENTAL
195 If you say yes to this option, support will be included for the VIA
196 82C586B I2C interface
198 This driver can also be built as a module. If so, the module
199 will be called i2c-via.
202 tristate "VIA VT82C596/82C686/82xx and CX700"
205 If you say yes to this option, support will be included for the VIA
206 VT82C596 and later SMBus interface. Specifically, the following
207 chipsets are supported:
217 This driver can also be built as a module. If so, the module
218 will be called i2c-viapro.
220 comment "Mac SMBus host controller drivers"
221 depends on PPC_CHRP || PPC_PMAC
224 tristate "CHRP Apple Hydra Mac I/O I2C interface"
225 depends on PCI && PPC_CHRP && EXPERIMENTAL
228 This supports the use of the I2C interface in the Apple Hydra Mac
229 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
232 This support is also available as a module. If so, the module
233 will be called i2c-hydra.
236 tristate "Powermac I2C interface"
240 This exposes the various PowerMac i2c interfaces to the linux i2c
241 layer and to userland. It is used by various drivers on the PowerMac
242 platform, and should generally be enabled.
244 This support is also available as a module. If so, the module
245 will be called i2c-powermac.
247 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
250 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
251 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
253 This supports the use of the I2C interface on Atmel AT91
256 This driver is BROKEN because the controller which it uses
257 will easily trigger RX overrun and TX underrun errors. Using
258 low I2C clock rates may partially work around those issues
259 on some systems. Another serious problem is that there is no
260 documented way to issue repeated START conditions, as needed
261 to support combined I2C messages. Use the i2c-gpio driver
262 unless your system can cope with those limitations.
265 tristate "Au1550/Au1200 SMBus interface"
266 depends on SOC_AU1550 || SOC_AU1200
268 If you say yes to this option, support will be included for the
269 Au1550 and Au1200 SMBus interface.
271 This driver can also be built as a module. If so, the module
272 will be called i2c-au1550.
274 config I2C_BLACKFIN_TWI
275 tristate "Blackfin TWI I2C support"
277 depends on !BF561 && !BF531 && !BF532 && !BF533
279 This is the I2C bus driver for Blackfin on-chip TWI interface.
281 This driver can also be built as a module. If so, the module
282 will be called i2c-bfin-twi.
284 config I2C_BLACKFIN_TWI_CLK_KHZ
285 int "Blackfin TWI I2C clock (kHz)"
286 depends on I2C_BLACKFIN_TWI
290 The unit of the TWI clock is kHz.
293 tristate "DaVinci I2C driver"
294 depends on ARCH_DAVINCI
296 Support for TI DaVinci I2C controller driver.
298 This driver can also be built as a module. If so, the module
299 will be called i2c-davinci.
301 Please note that this driver might be needed to bring up other
302 devices such as DaVinci NIC.
303 For details please see http://www.ti.com/davinci
306 tristate "GPIO-based bitbanging I2C"
307 depends on GENERIC_GPIO
310 This is a very simple bitbanging I2C driver utilizing the
311 arch-neutral GPIO API to control the SCL and SDA lines.
314 tristate "IBM PPC 4xx on-chip I2C interface"
317 Say Y here if you want to use IIC peripheral found on
318 embedded IBM PPC 4xx based systems.
320 This driver can also be built as a module. If so, the module
321 will be called i2c-ibm_iic.
324 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
325 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
327 Say Y here if you want to use the IIC bus controller on
328 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
330 This driver can also be built as a module. If so, the module
331 will be called i2c-iop3xx.
334 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
335 depends on ARCH_IXP2000
338 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
339 system and are using GPIO lines for an I2C bus.
341 This support is also available as a module. If so, the module
342 will be called i2c-ixp2000.
344 This driver is deprecated and will be dropped soon. Use i2c-gpio
348 tristate "MPC107/824x/85xx/52xx/86xx"
351 If you say yes to this option, support will be included for the
352 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
353 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
354 family processors, though interrupts are known not to work.
356 This driver can also be built as a module. If so, the module
357 will be called i2c-mpc.
360 tristate "Marvell mv64xxx I2C Controller"
361 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
363 If you say yes to this option, support will be included for the
364 built-in I2C interface on the Marvell 64xxx line of host bridges.
366 This driver can also be built as a module. If so, the module
367 will be called i2c-mv64xxx.
370 tristate "OpenCores I2C Controller"
371 depends on EXPERIMENTAL
373 If you say yes to this option, support will be included for the
374 OpenCores I2C controller. For details see
375 http://www.opencores.org/projects.cgi/web/i2c/overview
377 This driver can also be built as a module. If so, the module
378 will be called i2c-ocores.
381 tristate "OMAP I2C adapter"
383 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
385 If you say yes to this option, support will be included for the
386 I2C interface on the Texas Instruments OMAP1/2 family of processors.
387 Like OMAP1510/1610/1710/5912 and OMAP242x.
388 For details see http://www.ti.com/omap.
391 tristate "PA Semi SMBus interface"
392 depends on PPC_PASEMI && PCI
394 Supports the PA Semi PWRficient on-chip SMBus interfaces.
397 tristate "I2C bus support for Philips PNX targets"
398 depends on ARCH_PNX4008
400 This driver supports the Philips IP3204 I2C IP block master and/or
403 This driver can also be built as a module. If so, the module
404 will be called i2c-pnx.
407 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
408 depends on EXPERIMENTAL && ARCH_PXA
410 If you have devices in the PXA I2C bus, say yes to this option.
411 This driver can also be built as a module. If so, the module
412 will be called i2c-pxa.
415 bool "Intel PXA2XX I2C Slave comms support"
418 Support I2C slave mode communications on the PXA I2C bus. This
419 is necessary for systems where the PXA may be a target on the
423 tristate "S3C2410 I2C Driver"
424 depends on ARCH_S3C2410
426 Say Y here to include support for I2C controller in the
427 Samsung S3C2410 based System-on-Chip devices.
430 tristate "Renesas SH7760 I2C Controller"
431 depends on CPU_SUBTYPE_SH7760
433 This driver supports the 2 I2C interfaces on the Renesas SH7760.
435 This driver can also be built as a module. If so, the module
436 will be called i2c-sh7760.
439 tristate "SuperH Mobile I2C Controller"
442 If you say yes to this option, support will be included for the
443 built-in I2C interface on the Renesas SH-Mobile processor.
445 This driver can also be built as a module. If so, the module
446 will be called i2c-sh_mobile.
449 tristate "Simtec Generic I2C interface"
452 If you say yes to this option, support will be included for
453 the Simtec Generic I2C interface. This driver is for the
454 simple I2C bus used on newer Simtec products for general
455 I2C, such as DDC on the Simtec BBD2016A.
457 This driver can also be built as a module. If so, the module
458 will be called i2c-simtec.
461 tristate "ARM Versatile/Realview I2C bus support"
462 depends on ARCH_VERSATILE || ARCH_REALVIEW
465 Say yes if you want to support the I2C serial bus on ARMs Versatile
468 This driver can also be built as a module. If so, the module
469 will be called i2c-versatile.
471 comment "External I2C/SMBus adapter drivers"
474 tristate "Parallel port adapter"
478 This supports parallel port I2C adapters such as the ones made by
479 Philips or Velleman, Analog Devices evaluation boards, and more.
480 Basically any adapter using the parallel port as an I2C bus with
481 no extra chipset is supported by this driver, or could be.
483 This driver is a replacement for (and was inspired by) an older
484 driver named i2c-philips-par. The new driver supports more devices,
485 and makes it easier to add support for new devices.
487 An adapter type parameter is now mandatory. Please read the file
488 Documentation/i2c/busses/i2c-parport for details.
490 Another driver exists, named i2c-parport-light, which doesn't depend
491 on the parport driver. This is meant for embedded systems. Don't say
492 Y here if you intend to say Y or M there.
494 This support is also available as a module. If so, the module
495 will be called i2c-parport.
497 config I2C_PARPORT_LIGHT
498 tristate "Parallel port adapter (light)"
501 This supports parallel port I2C adapters such as the ones made by
502 Philips or Velleman, Analog Devices evaluation boards, and more.
503 Basically any adapter using the parallel port as an I2C bus with
504 no extra chipset is supported by this driver, or could be.
506 This driver is a light version of i2c-parport. It doesn't depend
507 on the parport driver, and uses direct I/O access instead. This
508 might be preferred on embedded systems where wasting memory for
509 the clean but heavy parport handling is not an option. The
510 drawback is a reduced portability and the impossibility to
511 daisy-chain other parallel port devices.
513 Don't say Y here if you said Y or M to i2c-parport. Saying M to
514 both is possible but both modules should not be loaded at the same
517 This support is also available as a module. If so, the module
518 will be called i2c-parport-light.
521 tristate "TAOS evaluation module"
522 depends on EXPERIMENTAL
527 This supports TAOS evaluation modules on serial port. In order to
528 use this driver, you will need the inputattach tool, which is part
529 of the input-utils package.
533 This support is also available as a module. If so, the module
534 will be called i2c-taos-evm.
537 tristate "Tiny-USB adapter"
540 If you say yes to this option, support will be included for the
541 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
542 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
544 This driver can also be built as a module. If so, the module
545 will be called i2c-tiny-usb.
547 comment "Graphics adapter I2C/DDC channel drivers"
555 If you say yes to this option, support will be included for the
556 Voodoo 3 I2C interface.
558 This driver can also be built as a module. If so, the module
559 will be called i2c-voodoo3.
561 comment "Other I2C/SMBus bus drivers"
564 tristate "Acorn IOC/IOMD I2C bus support"
565 depends on ARCH_ACORN
569 Say yes if you want to support the I2C bus on Acorn platforms.
571 If you don't know, say Y.
574 tristate "Elektor ISA card"
575 depends on ISA && BROKEN_ON_SMP
578 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
581 This support is also available as a module. If so, the module
582 will be called i2c-elektor.
585 tristate "PCA9564 on an ISA bus"
590 This driver supports ISA boards using the Philips PCA9564
591 parallel bus to I2C bus controller.
593 This driver can also be built as a module. If so, the module
594 will be called i2c-pca-isa.
596 This device is almost undetectable and using this driver on a
597 system which doesn't have this device will result in long
598 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
599 time). If unsure, say N.
601 config I2C_PCA_PLATFORM
602 tristate "PCA9564 as platform device"
606 This driver supports a memory mapped Philips PCA9564
607 parallel bus to I2C bus controller.
609 This driver can also be built as a module. If so, the module
610 will be called i2c-pca-platform.
613 tristate "PMC MSP I2C TWI Controller"
616 This driver supports the PMC TWI controller on MSP devices.
618 This driver can also be built as module. If so, the module
619 will be called i2c-pmcmsp.
622 tristate "SiByte SMBus interface"
623 depends on SIBYTE_SB1xxx_SOC
625 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
628 tristate "I2C/SMBus Test Stub"
629 depends on EXPERIMENTAL && m
632 This module may be useful to developers of SMBus client drivers,
633 especially for certain kinds of sensor chips.
635 If you do build this module, be sure to read the notes and warnings
636 in <file:Documentation/i2c/i2c-stub>.
638 If you don't know what to do here, definitely say N.
641 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
642 depends on SCx200_GPIO
645 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
647 If you don't know what to do here, say N.
649 This support is also available as a module. If so, the module
650 will be called scx200_i2c.
652 This driver is deprecated and will be dropped soon. Use i2c-gpio
653 (or scx200_acb) instead.
655 config SCx200_I2C_SCL
656 int "GPIO pin used for SCL"
657 depends on SCx200_I2C
660 Enter the GPIO pin number used for the SCL signal. This value can
661 also be specified with a module parameter.
663 config SCx200_I2C_SDA
664 int "GPIO pin used for SDA"
665 depends on SCx200_I2C
668 Enter the GPIO pin number used for the SSA signal. This value can
669 also be specified with a module parameter.
672 tristate "Geode ACCESS.bus support"
673 depends on X86_32 && PCI
675 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
676 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
678 If you don't know what to do here, say N.
680 This support is also available as a module. If so, the module
681 will be called scx200_acb.