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"
104 depends on !BF561 && !BF531 && !BF532 && !BF533
106 This is the I2C bus driver for Blackfin on-chip TWI interface.
108 This driver can also be built as a module. If so, the module
109 will be called i2c-bfin-twi.
111 config I2C_BLACKFIN_TWI_CLK_KHZ
112 int "Blackfin TWI I2C clock (kHz)"
113 depends on I2C_BLACKFIN_TWI
117 The unit of the TWI clock is kHz.
120 tristate "DaVinci I2C driver"
121 depends on ARCH_DAVINCI
123 Support for TI DaVinci I2C controller driver.
125 This driver can also be built as a module. If so, the module
126 will be called i2c-davinci.
128 Please note that this driver might be needed to bring up other
129 devices such as DaVinci NIC.
130 For details please see http://www.ti.com/davinci
133 tristate "Elektor ISA card"
134 depends on ISA && BROKEN_ON_SMP
137 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
140 This support is also available as a module. If so, the module
141 will be called i2c-elektor.
144 tristate "GPIO-based bitbanging I2C"
145 depends on GENERIC_GPIO
148 This is a very simple bitbanging I2C driver utilizing the
149 arch-neutral GPIO API to control the SCL and SDA lines.
152 tristate "CHRP Apple Hydra Mac I/O I2C interface"
153 depends on PCI && PPC_CHRP && EXPERIMENTAL
156 This supports the use of the I2C interface in the Apple Hydra Mac
157 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
160 This support is also available as a module. If so, the module
161 will be called i2c-hydra.
164 tristate "Intel 82801 (ICH)"
167 If you say yes to this option, support will be included for the Intel
168 801 family of mainboard I2C interfaces. Specifically, the following
169 versions of the chipset are supported:
175 82801EB/ER (ICH5/ICH5R)
185 This driver can also be built as a module. If so, the module
186 will be called i2c-i801.
189 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
190 depends on EXPERIMENTAL && ARCH_PXA
192 If you have devices in the PXA I2C bus, say yes to this option.
193 This driver can also be built as a module. If so, the module
194 will be called i2c-pxa.
197 bool "Intel PXA2XX I2C Slave comms support"
200 Support I2C slave mode communications on the PXA I2C bus. This
201 is necessary for systems where the PXA may be a target on the
205 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
208 If you say yes to this option, support will be included for the Intel
209 PIIX4 family of mainboard I2C interfaces. Specifically, the following
210 versions of the chipset are supported (note that Serverworks is part
226 This driver can also be built as a module. If so, the module
227 will be called i2c-piix4.
230 tristate "IBM PPC 4xx on-chip I2C interface"
233 Say Y here if you want to use IIC peripheral found on
234 embedded IBM PPC 4xx based systems.
236 This driver can also be built as a module. If so, the module
237 will be called i2c-ibm_iic.
240 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
241 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
243 Say Y here if you want to use the IIC bus controller on
244 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
246 This driver can also be built as a module. If so, the module
247 will be called i2c-iop3xx.
250 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
251 depends on ARCH_IXP2000
254 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
255 system and are using GPIO lines for an I2C bus.
257 This support is also available as a module. If so, the module
258 will be called i2c-ixp2000.
260 This driver is deprecated and will be dropped soon. Use i2c-gpio
264 tristate "Powermac I2C interface"
268 This exposes the various PowerMac i2c interfaces to the linux i2c
269 layer and to userland. It is used by various drivers on the PowerMac
270 platform, and should generally be enabled.
272 This support is also available as a module. If so, the module
273 will be called i2c-powermac.
276 tristate "MPC107/824x/85xx/52xx/86xx"
279 If you say yes to this option, support will be included for the
280 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
281 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
282 family processors, though interrupts are known not to work.
284 This driver can also be built as a module. If so, the module
285 will be called i2c-mpc.
288 tristate "Nvidia nForce2, nForce3 and nForce4"
291 If you say yes to this option, support will be included for the Nvidia
292 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
294 This driver can also be built as a module. If so, the module
295 will be called i2c-nforce2.
297 config I2C_NFORCE2_S4985
298 tristate "SMBus multiplexing on the Tyan S4985"
299 depends on I2C_NFORCE2 && EXPERIMENTAL
301 Enabling this option will add specific SMBus support for the Tyan
302 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
303 over 4 different channels, where the various memory module EEPROMs
304 live. Saying yes here will give you access to these in addition
307 This driver can also be built as a module. If so, the module
308 will be called i2c-nforce2-s4985.
311 tristate "OpenCores I2C Controller"
312 depends on EXPERIMENTAL
314 If you say yes to this option, support will be included for the
315 OpenCores I2C controller. For details see
316 http://www.opencores.org/projects.cgi/web/i2c/overview
318 This driver can also be built as a module. If so, the module
319 will be called i2c-ocores.
322 tristate "OMAP I2C adapter"
324 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
326 If you say yes to this option, support will be included for the
327 I2C interface on the Texas Instruments OMAP1/2 family of processors.
328 Like OMAP1510/1610/1710/5912 and OMAP242x.
329 For details see http://www.ti.com/omap.
332 tristate "Parallel port adapter"
336 This supports parallel port I2C adapters such as the ones made by
337 Philips or Velleman, Analog Devices evaluation boards, and more.
338 Basically any adapter using the parallel port as an I2C bus with
339 no extra chipset is supported by this driver, or could be.
341 This driver is a replacement for (and was inspired by) an older
342 driver named i2c-philips-par. The new driver supports more devices,
343 and makes it easier to add support for new devices.
345 An adapter type parameter is now mandatory. Please read the file
346 Documentation/i2c/busses/i2c-parport for details.
348 Another driver exists, named i2c-parport-light, which doesn't depend
349 on the parport driver. This is meant for embedded systems. Don't say
350 Y here if you intend to say Y or M there.
352 This support is also available as a module. If so, the module
353 will be called i2c-parport.
355 config I2C_PARPORT_LIGHT
356 tristate "Parallel port adapter (light)"
359 This supports parallel port I2C adapters such as the ones made by
360 Philips or Velleman, Analog Devices evaluation boards, and more.
361 Basically any adapter using the parallel port as an I2C bus with
362 no extra chipset is supported by this driver, or could be.
364 This driver is a light version of i2c-parport. It doesn't depend
365 on the parport driver, and uses direct I/O access instead. This
366 might be preferred on embedded systems where wasting memory for
367 the clean but heavy parport handling is not an option. The
368 drawback is a reduced portability and the impossibility to
369 daisy-chain other parallel port devices.
371 Don't say Y here if you said Y or M to i2c-parport. Saying M to
372 both is possible but both modules should not be loaded at the same
375 This support is also available as a module. If so, the module
376 will be called i2c-parport-light.
379 tristate "PA Semi SMBus interface"
380 depends on PPC_PASEMI && PCI
382 Supports the PA Semi PWRficient on-chip SMBus interfaces.
385 tristate "S3C2410 I2C Driver"
386 depends on ARCH_S3C2410
388 Say Y here to include support for I2C controller in the
389 Samsung S3C2410 based System-on-Chip devices.
392 tristate "SiByte SMBus interface"
393 depends on SIBYTE_SB1xxx_SOC
395 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
398 tristate "Simtec Generic I2C interface"
401 If you say yes to this option, support will be included for
402 the Simtec Generic I2C interface. This driver is for the
403 simple I2C bus used on newer Simtec products for general
404 I2C, such as DDC on the Simtec BBD2016A.
406 This driver can also be built as a module. If so, the module
407 will be called i2c-simtec.
410 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
411 depends on SCx200_GPIO
414 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
416 If you don't know what to do here, say N.
418 This support is also available as a module. If so, the module
419 will be called scx200_i2c.
421 This driver is deprecated and will be dropped soon. Use i2c-gpio
422 (or scx200_acb) instead.
424 config SCx200_I2C_SCL
425 int "GPIO pin used for SCL"
426 depends on SCx200_I2C
429 Enter the GPIO pin number used for the SCL signal. This value can
430 also be specified with a module parameter.
432 config SCx200_I2C_SDA
433 int "GPIO pin used for SDA"
434 depends on SCx200_I2C
437 Enter the GPIO pin number used for the SSA signal. This value can
438 also be specified with a module parameter.
441 tristate "Geode ACCESS.bus support"
442 depends on X86_32 && PCI
444 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
445 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
447 If you don't know what to do here, say N.
449 This support is also available as a module. If so, the module
450 will be called scx200_acb.
456 If you say yes to this option, support will be included for the
457 SiS5595 SMBus (a subset of I2C) interface.
459 This driver can also be built as a module. If so, the module
460 will be called i2c-sis5595.
463 tristate "SiS 630/730"
466 If you say yes to this option, support will be included for the
467 SiS630 and SiS730 SMBus (a subset of I2C) interface.
469 This driver can also be built as a module. If so, the module
470 will be called i2c-sis630.
476 If you say yes to this option, support will be included for the SiS
477 96x SMBus (a subset of I2C) interfaces. Specifically, the following
478 chipsets are supported:
487 This driver can also be built as a module. If so, the module
488 will be called i2c-sis96x.
491 tristate "TAOS evaluation module"
492 depends on EXPERIMENTAL
497 This supports TAOS evaluation modules on serial port. In order to
498 use this driver, you will need the inputattach tool, which is part
499 of the input-utils package.
503 This support is also available as a module. If so, the module
504 will be called i2c-taos-evm.
507 tristate "I2C/SMBus Test Stub"
508 depends on EXPERIMENTAL && m
511 This module may be useful to developers of SMBus client drivers,
512 especially for certain kinds of sensor chips.
514 If you do build this module, be sure to read the notes and warnings
515 in <file:Documentation/i2c/i2c-stub>.
517 If you don't know what to do here, definitely say N.
520 tristate "I2C-Tiny-USB"
523 If you say yes to this option, support will be included for the
524 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
525 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
527 This driver can also be built as a module. If so, the module
528 will be called i2c-tiny-usb.
531 tristate "ARM Versatile/Realview I2C bus support"
532 depends on ARCH_VERSATILE || ARCH_REALVIEW
535 Say yes if you want to support the I2C serial bus on ARMs Versatile
538 This driver can also be built as a module. If so, the module
539 will be called i2c-versatile.
542 tristate "Acorn IOC/IOMD I2C bus support"
543 depends on ARCH_ACORN
547 Say yes if you want to support the I2C bus on Acorn platforms.
549 If you don't know, say Y.
552 tristate "VIA 82C586B"
553 depends on PCI && EXPERIMENTAL
556 If you say yes to this option, support will be included for the VIA
557 82C586B I2C interface
559 This driver can also be built as a module. If so, the module
560 will be called i2c-via.
563 tristate "VIA VT82C596/82C686/82xx and CX700"
566 If you say yes to this option, support will be included for the VIA
567 VT82C596 and later SMBus interface. Specifically, the following
568 chipsets are supported:
578 This driver can also be built as a module. If so, the module
579 will be called i2c-viapro.
586 If you say yes to this option, support will be included for the
587 Voodoo 3 I2C interface.
589 This driver can also be built as a module. If so, the module
590 will be called i2c-voodoo3.
593 tristate "PCA9564 on an ISA bus"
598 This driver supports ISA boards using the Philips PCA9564
599 parallel bus to I2C bus controller.
601 This driver can also be built as a module. If so, the module
602 will be called i2c-pca-isa.
604 This device is almost undetectable and using this driver on a
605 system which doesn't have this device will result in long
606 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
607 time). If unsure, say N.
609 config I2C_PCA_PLATFORM
610 tristate "PCA9564 as platform device"
614 This driver supports a memory mapped Philips PCA9564
615 parallel bus to I2C bus controller.
617 This driver can also be built as a module. If so, the module
618 will be called i2c-pca-platform.
621 tristate "Marvell mv64xxx I2C Controller"
622 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
624 If you say yes to this option, support will be included for the
625 built-in I2C interface on the Marvell 64xxx line of host bridges.
627 This driver can also be built as a module. If so, the module
628 will be called i2c-mv64xxx.
631 tristate "I2C bus support for Philips PNX targets"
632 depends on ARCH_PNX4008
634 This driver supports the Philips IP3204 I2C IP block master and/or
637 This driver can also be built as a module. If so, the module
638 will be called i2c-pnx.
641 tristate "PMC MSP I2C TWI Controller"
644 This driver supports the PMC TWI controller on MSP devices.
646 This driver can also be built as module. If so, the module
647 will be called i2c-pmcmsp.
650 tristate "Renesas SH7760 I2C Controller"
651 depends on CPU_SUBTYPE_SH7760
653 This driver supports the 2 I2C interfaces on the Renesas SH7760.
655 This driver can also be built as a module. If so, the module
656 will be called i2c-sh7760.
659 tristate "SuperH Mobile I2C Controller"
662 If you say yes to this option, support will be included for the
663 built-in I2C interface on the Renesas SH-Mobile processor.
665 This driver can also be built as a module. If so, the module
666 will be called i2c-sh_mobile.