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 SCH SMBus 1.0"
108 Say Y here if you want to use SMBus controller on the Intel SCH
111 This driver can also be built as a module. If so, the module
112 will be called i2c-isch.
115 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
118 If you say yes to this option, support will be included for the Intel
119 PIIX4 family of mainboard I2C interfaces. Specifically, the following
120 versions of the chipset are supported (note that Serverworks is part
136 This driver can also be built as a module. If so, the module
137 will be called i2c-piix4.
140 tristate "Nvidia nForce2, nForce3 and nForce4"
143 If you say yes to this option, support will be included for the Nvidia
144 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
146 This driver can also be built as a module. If so, the module
147 will be called i2c-nforce2.
149 config I2C_NFORCE2_S4985
150 tristate "SMBus multiplexing on the Tyan S4985"
151 depends on I2C_NFORCE2 && EXPERIMENTAL
153 Enabling this option will add specific SMBus support for the Tyan
154 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
155 over 4 different channels, where the various memory module EEPROMs
156 live. Saying yes here will give you access to these in addition
159 This driver can also be built as a module. If so, the module
160 will be called i2c-nforce2-s4985.
166 If you say yes to this option, support will be included for the
167 SiS5595 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-sis5595.
173 tristate "SiS 630/730"
176 If you say yes to this option, support will be included for the
177 SiS630 and SiS730 SMBus (a subset of I2C) interface.
179 This driver can also be built as a module. If so, the module
180 will be called i2c-sis630.
186 If you say yes to this option, support will be included for the SiS
187 96x SMBus (a subset of I2C) interfaces. Specifically, the following
188 chipsets are supported:
197 This driver can also be built as a module. If so, the module
198 will be called i2c-sis96x.
201 tristate "VIA VT82C586B"
202 depends on PCI && EXPERIMENTAL
205 If you say yes to this option, support will be included for the VIA
206 82C586B I2C interface
208 This driver can also be built as a module. If so, the module
209 will be called i2c-via.
212 tristate "VIA VT82C596/82C686/82xx and CX700"
215 If you say yes to this option, support will be included for the VIA
216 VT82C596 and later SMBus interface. Specifically, the following
217 chipsets are supported:
227 This driver can also be built as a module. If so, the module
228 will be called i2c-viapro.
230 comment "Mac SMBus host controller drivers"
231 depends on PPC_CHRP || PPC_PMAC
234 tristate "CHRP Apple Hydra Mac I/O I2C interface"
235 depends on PCI && PPC_CHRP && EXPERIMENTAL
238 This supports the use of the I2C interface in the Apple Hydra Mac
239 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
242 This support is also available as a module. If so, the module
243 will be called i2c-hydra.
246 tristate "Powermac I2C interface"
250 This exposes the various PowerMac i2c interfaces to the linux i2c
251 layer and to userland. It is used by various drivers on the PowerMac
252 platform, and should generally be enabled.
254 This support is also available as a module. If so, the module
255 will be called i2c-powermac.
257 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
260 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
261 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
263 This supports the use of the I2C interface on Atmel AT91
266 This driver is BROKEN because the controller which it uses
267 will easily trigger RX overrun and TX underrun errors. Using
268 low I2C clock rates may partially work around those issues
269 on some systems. Another serious problem is that there is no
270 documented way to issue repeated START conditions, as needed
271 to support combined I2C messages. Use the i2c-gpio driver
272 unless your system can cope with those limitations.
275 tristate "Au1550/Au1200 SMBus interface"
276 depends on SOC_AU1550 || SOC_AU1200
278 If you say yes to this option, support will be included for the
279 Au1550 and Au1200 SMBus interface.
281 This driver can also be built as a module. If so, the module
282 will be called i2c-au1550.
284 config I2C_BLACKFIN_TWI
285 tristate "Blackfin TWI I2C support"
287 depends on !BF561 && !BF531 && !BF532 && !BF533
289 This is the I2C bus driver for Blackfin on-chip TWI interface.
291 This driver can also be built as a module. If so, the module
292 will be called i2c-bfin-twi.
294 config I2C_BLACKFIN_TWI_CLK_KHZ
295 int "Blackfin TWI I2C clock (kHz)"
296 depends on I2C_BLACKFIN_TWI
300 The unit of the TWI clock is kHz.
303 tristate "DaVinci I2C driver"
304 depends on ARCH_DAVINCI
306 Support for TI DaVinci I2C controller driver.
308 This driver can also be built as a module. If so, the module
309 will be called i2c-davinci.
311 Please note that this driver might be needed to bring up other
312 devices such as DaVinci NIC.
313 For details please see http://www.ti.com/davinci
316 tristate "GPIO-based bitbanging I2C"
317 depends on GENERIC_GPIO
320 This is a very simple bitbanging I2C driver utilizing the
321 arch-neutral GPIO API to control the SCL and SDA lines.
324 tristate "IBM PPC 4xx on-chip I2C interface"
327 Say Y here if you want to use IIC peripheral found on
328 embedded IBM PPC 4xx based systems.
330 This driver can also be built as a module. If so, the module
331 will be called i2c-ibm_iic.
334 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
335 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
337 Say Y here if you want to use the IIC bus controller on
338 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
340 This driver can also be built as a module. If so, the module
341 will be called i2c-iop3xx.
344 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
345 depends on ARCH_IXP2000
348 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
349 system and are using GPIO lines for an I2C bus.
351 This support is also available as a module. If so, the module
352 will be called i2c-ixp2000.
354 This driver is deprecated and will be dropped soon. Use i2c-gpio
358 tristate "MPC107/824x/85xx/52xx/86xx"
361 If you say yes to this option, support will be included for the
362 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
363 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
364 family processors, though interrupts are known not to work.
366 This driver can also be built as a module. If so, the module
367 will be called i2c-mpc.
370 tristate "Marvell mv64xxx I2C Controller"
371 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
373 If you say yes to this option, support will be included for the
374 built-in I2C interface on the Marvell 64xxx line of host bridges.
376 This driver can also be built as a module. If so, the module
377 will be called i2c-mv64xxx.
380 tristate "OpenCores I2C Controller"
381 depends on EXPERIMENTAL
383 If you say yes to this option, support will be included for the
384 OpenCores I2C controller. For details see
385 http://www.opencores.org/projects.cgi/web/i2c/overview
387 This driver can also be built as a module. If so, the module
388 will be called i2c-ocores.
391 tristate "OMAP I2C adapter"
393 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
395 If you say yes to this option, support will be included for the
396 I2C interface on the Texas Instruments OMAP1/2 family of processors.
397 Like OMAP1510/1610/1710/5912 and OMAP242x.
398 For details see http://www.ti.com/omap.
401 tristate "PA Semi SMBus interface"
402 depends on PPC_PASEMI && PCI
404 Supports the PA Semi PWRficient on-chip SMBus interfaces.
407 tristate "I2C bus support for Philips PNX targets"
408 depends on ARCH_PNX4008
410 This driver supports the Philips IP3204 I2C IP block master and/or
413 This driver can also be built as a module. If so, the module
414 will be called i2c-pnx.
417 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
418 depends on EXPERIMENTAL && ARCH_PXA
420 If you have devices in the PXA I2C bus, say yes to this option.
421 This driver can also be built as a module. If so, the module
422 will be called i2c-pxa.
425 bool "Intel PXA2XX I2C Slave comms support"
428 Support I2C slave mode communications on the PXA I2C bus. This
429 is necessary for systems where the PXA may be a target on the
433 tristate "S3C2410 I2C Driver"
434 depends on ARCH_S3C2410
436 Say Y here to include support for I2C controller in the
437 Samsung S3C2410 based System-on-Chip devices.
440 tristate "Renesas SH7760 I2C Controller"
441 depends on CPU_SUBTYPE_SH7760
443 This driver supports the 2 I2C interfaces on the Renesas SH7760.
445 This driver can also be built as a module. If so, the module
446 will be called i2c-sh7760.
449 tristate "SuperH Mobile I2C Controller"
452 If you say yes to this option, support will be included for the
453 built-in I2C interface on the Renesas SH-Mobile processor.
455 This driver can also be built as a module. If so, the module
456 will be called i2c-sh_mobile.
459 tristate "Simtec Generic I2C interface"
462 If you say yes to this option, support will be included for
463 the Simtec Generic I2C interface. This driver is for the
464 simple I2C bus used on newer Simtec products for general
465 I2C, such as DDC on the Simtec BBD2016A.
467 This driver can also be built as a module. If so, the module
468 will be called i2c-simtec.
471 tristate "ARM Versatile/Realview I2C bus support"
472 depends on ARCH_VERSATILE || ARCH_REALVIEW
475 Say yes if you want to support the I2C serial bus on ARMs Versatile
478 This driver can also be built as a module. If so, the module
479 will be called i2c-versatile.
481 comment "External I2C/SMBus adapter drivers"
484 tristate "Parallel port adapter"
488 This supports parallel port I2C adapters such as the ones made by
489 Philips or Velleman, Analog Devices evaluation boards, and more.
490 Basically any adapter using the parallel port as an I2C bus with
491 no extra chipset is supported by this driver, or could be.
493 This driver is a replacement for (and was inspired by) an older
494 driver named i2c-philips-par. The new driver supports more devices,
495 and makes it easier to add support for new devices.
497 An adapter type parameter is now mandatory. Please read the file
498 Documentation/i2c/busses/i2c-parport for details.
500 Another driver exists, named i2c-parport-light, which doesn't depend
501 on the parport driver. This is meant for embedded systems. Don't say
502 Y here if you intend to say Y or M there.
504 This support is also available as a module. If so, the module
505 will be called i2c-parport.
507 config I2C_PARPORT_LIGHT
508 tristate "Parallel port adapter (light)"
511 This supports parallel port I2C adapters such as the ones made by
512 Philips or Velleman, Analog Devices evaluation boards, and more.
513 Basically any adapter using the parallel port as an I2C bus with
514 no extra chipset is supported by this driver, or could be.
516 This driver is a light version of i2c-parport. It doesn't depend
517 on the parport driver, and uses direct I/O access instead. This
518 might be preferred on embedded systems where wasting memory for
519 the clean but heavy parport handling is not an option. The
520 drawback is a reduced portability and the impossibility to
521 daisy-chain other parallel port devices.
523 Don't say Y here if you said Y or M to i2c-parport. Saying M to
524 both is possible but both modules should not be loaded at the same
527 This support is also available as a module. If so, the module
528 will be called i2c-parport-light.
531 tristate "TAOS evaluation module"
532 depends on EXPERIMENTAL
537 This supports TAOS evaluation modules on serial port. In order to
538 use this driver, you will need the inputattach tool, which is part
539 of the input-utils package.
543 This support is also available as a module. If so, the module
544 will be called i2c-taos-evm.
547 tristate "Tiny-USB adapter"
550 If you say yes to this option, support will be included for the
551 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
552 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
554 This driver can also be built as a module. If so, the module
555 will be called i2c-tiny-usb.
557 comment "Graphics adapter I2C/DDC channel drivers"
565 If you say yes to this option, support will be included for the
566 Voodoo 3 I2C interface.
568 This driver can also be built as a module. If so, the module
569 will be called i2c-voodoo3.
571 comment "Other I2C/SMBus bus drivers"
574 tristate "Acorn IOC/IOMD I2C bus support"
575 depends on ARCH_ACORN
579 Say yes if you want to support the I2C bus on Acorn platforms.
581 If you don't know, say Y.
584 tristate "Elektor ISA card"
585 depends on ISA && BROKEN_ON_SMP
588 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
591 This support is also available as a module. If so, the module
592 will be called i2c-elektor.
595 tristate "PCA9564 on an ISA bus"
600 This driver supports ISA boards using the Philips PCA9564
601 parallel bus to I2C bus controller.
603 This driver can also be built as a module. If so, the module
604 will be called i2c-pca-isa.
606 This device is almost undetectable and using this driver on a
607 system which doesn't have this device will result in long
608 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
609 time). If unsure, say N.
611 config I2C_PCA_PLATFORM
612 tristate "PCA9564 as platform device"
616 This driver supports a memory mapped Philips PCA9564
617 parallel bus to I2C bus controller.
619 This driver can also be built as a module. If so, the module
620 will be called i2c-pca-platform.
623 tristate "PMC MSP I2C TWI Controller"
626 This driver supports the PMC TWI controller on MSP devices.
628 This driver can also be built as module. If so, the module
629 will be called i2c-pmcmsp.
632 tristate "SiByte SMBus interface"
633 depends on SIBYTE_SB1xxx_SOC
635 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
638 tristate "I2C/SMBus Test Stub"
639 depends on EXPERIMENTAL && m
642 This module may be useful to developers of SMBus client drivers,
643 especially for certain kinds of sensor chips.
645 If you do build this module, be sure to read the notes and warnings
646 in <file:Documentation/i2c/i2c-stub>.
648 If you don't know what to do here, definitely say N.
651 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
652 depends on SCx200_GPIO
655 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
657 If you don't know what to do here, say N.
659 This support is also available as a module. If so, the module
660 will be called scx200_i2c.
662 This driver is deprecated and will be dropped soon. Use i2c-gpio
663 (or scx200_acb) instead.
665 config SCx200_I2C_SCL
666 int "GPIO pin used for SCL"
667 depends on SCx200_I2C
670 Enter the GPIO pin number used for the SCL signal. This value can
671 also be specified with a module parameter.
673 config SCx200_I2C_SDA
674 int "GPIO pin used for SDA"
675 depends on SCx200_I2C
678 Enter the GPIO pin number used for the SSA signal. This value can
679 also be specified with a module parameter.
682 tristate "Geode ACCESS.bus support"
683 depends on X86_32 && PCI
685 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
686 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
688 If you don't know what to do here, say N.
690 This support is also available as a module. If so, the module
691 will be called scx200_acb.