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 PXA2XX I2C adapter (EXPERIMENTAL)"
191 depends on EXPERIMENTAL && ARCH_PXA
193 If you have devices in the PXA I2C bus, say yes to this option.
194 This driver can also be built as a module. If so, the module
195 will be called i2c-pxa.
198 bool "Intel PXA2XX I2C Slave comms support"
201 Support I2C slave mode communications on the PXA I2C bus. This
202 is necessary for systems where the PXA may be a target on the
206 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
209 If you say yes to this option, support will be included for the Intel
210 PIIX4 family of mainboard I2C interfaces. Specifically, the following
211 versions of the chipset are supported (note that Serverworks is part
227 This driver can also be built as a module. If so, the module
228 will be called i2c-piix4.
231 tristate "IBM PPC 4xx on-chip I2C interface"
234 Say Y here if you want to use IIC peripheral found on
235 embedded IBM PPC 4xx based systems.
237 This driver can also be built as a module. If so, the module
238 will be called i2c-ibm_iic.
241 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
242 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
244 Say Y here if you want to use the IIC bus controller on
245 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
247 This driver can also be built as a module. If so, the module
248 will be called i2c-iop3xx.
251 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
252 depends on ARCH_IXP2000
255 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
256 system and are using GPIO lines for an I2C bus.
258 This support is also available as a module. If so, the module
259 will be called i2c-ixp2000.
261 This driver is deprecated and will be dropped soon. Use i2c-gpio
265 tristate "Powermac I2C interface"
269 This exposes the various PowerMac i2c interfaces to the linux i2c
270 layer and to userland. It is used by various drivers on the PowerMac
271 platform, and should generally be enabled.
273 This support is also available as a module. If so, the module
274 will be called i2c-powermac.
277 tristate "MPC107/824x/85xx/52xx/86xx"
280 If you say yes to this option, support will be included for the
281 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
282 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
283 family processors, though interrupts are known not to work.
285 This driver can also be built as a module. If so, the module
286 will be called i2c-mpc.
289 tristate "Nvidia nForce2, nForce3 and nForce4"
292 If you say yes to this option, support will be included for the Nvidia
293 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
295 This driver can also be built as a module. If so, the module
296 will be called i2c-nforce2.
298 config I2C_NFORCE2_S4985
299 tristate "SMBus multiplexing on the Tyan S4985"
300 depends on I2C_NFORCE2 && EXPERIMENTAL
302 Enabling this option will add specific SMBus support for the Tyan
303 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
304 over 4 different channels, where the various memory module EEPROMs
305 live. Saying yes here will give you access to these in addition
308 This driver can also be built as a module. If so, the module
309 will be called i2c-nforce2-s4985.
312 tristate "OpenCores I2C Controller"
313 depends on EXPERIMENTAL
315 If you say yes to this option, support will be included for the
316 OpenCores I2C controller. For details see
317 http://www.opencores.org/projects.cgi/web/i2c/overview
319 This driver can also be built as a module. If so, the module
320 will be called i2c-ocores.
323 tristate "OMAP I2C adapter"
325 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
327 If you say yes to this option, support will be included for the
328 I2C interface on the Texas Instruments OMAP1/2 family of processors.
329 Like OMAP1510/1610/1710/5912 and OMAP242x.
330 For details see http://www.ti.com/omap.
333 tristate "Parallel port adapter"
337 This supports parallel port I2C adapters such as the ones made by
338 Philips or Velleman, Analog Devices evaluation boards, and more.
339 Basically any adapter using the parallel port as an I2C bus with
340 no extra chipset is supported by this driver, or could be.
342 This driver is a replacement for (and was inspired by) an older
343 driver named i2c-philips-par. The new driver supports more devices,
344 and makes it easier to add support for new devices.
346 An adapter type parameter is now mandatory. Please read the file
347 Documentation/i2c/busses/i2c-parport for details.
349 Another driver exists, named i2c-parport-light, which doesn't depend
350 on the parport driver. This is meant for embedded systems. Don't say
351 Y here if you intend to say Y or M there.
353 This support is also available as a module. If so, the module
354 will be called i2c-parport.
356 config I2C_PARPORT_LIGHT
357 tristate "Parallel port adapter (light)"
360 This supports parallel port I2C adapters such as the ones made by
361 Philips or Velleman, Analog Devices evaluation boards, and more.
362 Basically any adapter using the parallel port as an I2C bus with
363 no extra chipset is supported by this driver, or could be.
365 This driver is a light version of i2c-parport. It doesn't depend
366 on the parport driver, and uses direct I/O access instead. This
367 might be preferred on embedded systems where wasting memory for
368 the clean but heavy parport handling is not an option. The
369 drawback is a reduced portability and the impossibility to
370 daisy-chain other parallel port devices.
372 Don't say Y here if you said Y or M to i2c-parport. Saying M to
373 both is possible but both modules should not be loaded at the same
376 This support is also available as a module. If so, the module
377 will be called i2c-parport-light.
380 tristate "PA Semi SMBus interface"
381 depends on PPC_PASEMI && PCI
383 Supports the PA Semi PWRficient on-chip SMBus interfaces.
386 tristate "S3C2410 I2C Driver"
387 depends on ARCH_S3C2410
389 Say Y here to include support for I2C controller in the
390 Samsung S3C2410 based System-on-Chip devices.
393 tristate "SiByte SMBus interface"
394 depends on SIBYTE_SB1xxx_SOC
396 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
399 tristate "Simtec Generic I2C interface"
402 If you say yes to this option, support will be included for
403 the Simtec Generic I2C interface. This driver is for the
404 simple I2C bus used on newer Simtec products for general
405 I2C, such as DDC on the Simtec BBD2016A.
407 This driver can also be built as a module. If so, the module
408 will be called i2c-simtec.
411 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
412 depends on SCx200_GPIO
415 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
417 If you don't know what to do here, say N.
419 This support is also available as a module. If so, the module
420 will be called scx200_i2c.
422 This driver is deprecated and will be dropped soon. Use i2c-gpio
423 (or scx200_acb) instead.
425 config SCx200_I2C_SCL
426 int "GPIO pin used for SCL"
427 depends on SCx200_I2C
430 Enter the GPIO pin number used for the SCL signal. This value can
431 also be specified with a module parameter.
433 config SCx200_I2C_SDA
434 int "GPIO pin used for SDA"
435 depends on SCx200_I2C
438 Enter the GPIO pin number used for the SSA signal. This value can
439 also be specified with a module parameter.
442 tristate "Geode ACCESS.bus support"
443 depends on X86_32 && PCI
445 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
446 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
448 If you don't know what to do here, say N.
450 This support is also available as a module. If so, the module
451 will be called scx200_acb.
457 If you say yes to this option, support will be included for the
458 SiS5595 SMBus (a subset of I2C) interface.
460 This driver can also be built as a module. If so, the module
461 will be called i2c-sis5595.
464 tristate "SiS 630/730"
467 If you say yes to this option, support will be included for the
468 SiS630 and SiS730 SMBus (a subset of I2C) interface.
470 This driver can also be built as a module. If so, the module
471 will be called i2c-sis630.
477 If you say yes to this option, support will be included for the SiS
478 96x SMBus (a subset of I2C) interfaces. Specifically, the following
479 chipsets are supported:
488 This driver can also be built as a module. If so, the module
489 will be called i2c-sis96x.
492 tristate "TAOS evaluation module"
493 depends on EXPERIMENTAL
498 This supports TAOS evaluation modules on serial port. In order to
499 use this driver, you will need the inputattach tool, which is part
500 of the input-utils package.
504 This support is also available as a module. If so, the module
505 will be called i2c-taos-evm.
508 tristate "I2C/SMBus Test Stub"
509 depends on EXPERIMENTAL && m
512 This module may be useful to developers of SMBus client drivers,
513 especially for certain kinds of sensor chips.
515 If you do build this module, be sure to read the notes and warnings
516 in <file:Documentation/i2c/i2c-stub>.
518 If you don't know what to do here, definitely say N.
521 tristate "I2C-Tiny-USB"
524 If you say yes to this option, support will be included for the
525 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
526 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
528 This driver can also be built as a module. If so, the module
529 will be called i2c-tiny-usb.
532 tristate "ARM Versatile/Realview I2C bus support"
533 depends on ARCH_VERSATILE || ARCH_REALVIEW
536 Say yes if you want to support the I2C serial bus on ARMs Versatile
539 This driver can also be built as a module. If so, the module
540 will be called i2c-versatile.
543 tristate "Acorn IOC/IOMD I2C bus support"
544 depends on ARCH_ACORN
548 Say yes if you want to support the I2C bus on Acorn platforms.
550 If you don't know, say Y.
553 tristate "VIA 82C586B"
554 depends on PCI && EXPERIMENTAL
557 If you say yes to this option, support will be included for the VIA
558 82C586B I2C interface
560 This driver can also be built as a module. If so, the module
561 will be called i2c-via.
564 tristate "VIA VT82C596/82C686/82xx and CX700"
567 If you say yes to this option, support will be included for the VIA
568 VT82C596 and later SMBus interface. Specifically, the following
569 chipsets are supported:
579 This driver can also be built as a module. If so, the module
580 will be called i2c-viapro.
587 If you say yes to this option, support will be included for the
588 Voodoo 3 I2C interface.
590 This driver can also be built as a module. If so, the module
591 will be called i2c-voodoo3.
594 tristate "PCA9564 on an ISA bus"
599 This driver supports ISA boards using the Philips PCA9564
600 parallel bus to I2C bus controller.
602 This driver can also be built as a module. If so, the module
603 will be called i2c-pca-isa.
605 This device is almost undetectable and using this driver on a
606 system which doesn't have this device will result in long
607 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
608 time). If unsure, say N.
610 config I2C_PCA_PLATFORM
611 tristate "PCA9564 as platform device"
615 This driver supports a memory mapped Philips PCA9564
616 parallel bus to I2C bus controller.
618 This driver can also be built as a module. If so, the module
619 will be called i2c-pca-platform.
622 tristate "Marvell mv64xxx I2C Controller"
623 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
625 If you say yes to this option, support will be included for the
626 built-in I2C interface on the Marvell 64xxx line of host bridges.
628 This driver can also be built as a module. If so, the module
629 will be called i2c-mv64xxx.
632 tristate "I2C bus support for Philips PNX targets"
633 depends on ARCH_PNX4008
635 This driver supports the Philips IP3204 I2C IP block master and/or
638 This driver can also be built as a module. If so, the module
639 will be called i2c-pnx.
642 tristate "PMC MSP I2C TWI Controller"
645 This driver supports the PMC TWI controller on MSP devices.
647 This driver can also be built as module. If so, the module
648 will be called i2c-pmcmsp.
651 tristate "Renesas SH7760 I2C Controller"
652 depends on CPU_SUBTYPE_SH7760
654 This driver supports the 2 I2C interfaces on the Renesas SH7760.
656 This driver can also be built as a module. If so, the module
657 will be called i2c-sh7760.
660 tristate "SuperH Mobile I2C Controller"
663 If you say yes to this option, support will be included for the
664 built-in I2C interface on the Renesas SH-Mobile processor.
666 This driver can also be built as a module. If so, the module
667 will be called i2c-sh_mobile.