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
80 This supports the use of the I2C interface on Atmel AT91
84 tristate "Au1550/Au1200 SMBus interface"
85 depends on SOC_AU1550 || SOC_AU1200
87 If you say yes to this option, support will be included for the
88 Au1550 and Au1200 SMBus interface.
90 This driver can also be built as a module. If so, the module
91 will be called i2c-au1550.
93 config I2C_BLACKFIN_TWI
94 tristate "Blackfin TWI I2C support"
95 depends on BF534 || BF536 || BF537
97 This is the TWI I2C device driver for Blackfin 534/536/537.
98 This driver can also be built as a module. If so, the module
99 will be called i2c-bfin-twi.
101 config I2C_BLACKFIN_TWI_CLK_KHZ
102 int "Blackfin TWI I2C clock (kHz)"
103 depends on I2C_BLACKFIN_TWI
107 The unit of the TWI clock is kHz.
110 tristate "Elektor ISA card"
111 depends on ISA && BROKEN_ON_SMP
114 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
117 This support is also available as a module. If so, the module
118 will be called i2c-elektor.
121 tristate "GPIO-based bitbanging I2C"
122 depends on GENERIC_GPIO
125 This is a very simple bitbanging I2C driver utilizing the
126 arch-neutral GPIO API to control the SCL and SDA lines.
129 tristate "CHRP Apple Hydra Mac I/O I2C interface"
130 depends on PCI && PPC_CHRP && EXPERIMENTAL
133 This supports the use of the I2C interface in the Apple Hydra Mac
134 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
137 This support is also available as a module. If so, the module
138 will be called i2c-hydra.
141 tristate "Intel 82801 (ICH)"
144 If you say yes to this option, support will be included for the Intel
145 801 family of mainboard I2C interfaces. Specifically, the following
146 versions of the chipset are supported:
152 82801EB/ER (ICH5/ICH5R)
160 This driver can also be built as a module. If so, the module
161 will be called i2c-i801.
164 tristate "Intel 810/815"
168 If you say yes to this option, support will be included for the Intel
169 810/815 family of mainboard I2C interfaces. Specifically, the
170 following versions of the chipset are supported:
177 This driver can also be built as a module. If so, the module
178 will be called i2c-i810.
181 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
182 depends on EXPERIMENTAL && ARCH_PXA
184 If you have devices in the PXA I2C bus, say yes to this option.
185 This driver can also be built as a module. If so, the module
186 will be called i2c-pxa.
189 bool "Intel PXA2XX I2C Slave comms support"
192 Support I2C slave mode communications on the PXA I2C bus. This
193 is necessary for systems where the PXA may be a target on the
197 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
200 If you say yes to this option, support will be included for the Intel
201 PIIX4 family of mainboard I2C interfaces. Specifically, the following
202 versions of the chipset are supported (note that Serverworks is part
217 This driver can also be built as a module. If so, the module
218 will be called i2c-piix4.
221 tristate "IBM PPC 4xx on-chip I2C interface"
224 Say Y here if you want to use IIC peripheral found on
225 embedded IBM PPC 4xx based systems.
227 This driver can also be built as a module. If so, the module
228 will be called i2c-ibm_iic.
231 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
232 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
234 Say Y here if you want to use the IIC bus controller on
235 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
237 This driver can also be built as a module. If so, the module
238 will be called i2c-iop3xx.
244 tristate "IXP4xx GPIO-Based I2C Interface (DEPRECATED)"
245 depends on ARCH_IXP4XX
248 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
249 system and are using GPIO lines for an I2C bus.
251 This support is also available as a module. If so, the module
252 will be called i2c-ixp4xx.
254 This driver is deprecated and will be dropped soon. Use i2c-gpio
258 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
259 depends on ARCH_IXP2000
262 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
263 system and are using GPIO lines for an I2C bus.
265 This support is also available as a module. If so, the module
266 will be called i2c-ixp2000.
268 This driver is deprecated and will be dropped soon. Use i2c-gpio
272 tristate "Powermac I2C interface"
276 This exposes the various PowerMac i2c interfaces to the linux i2c
277 layer and to userland. It is used by various drivers on the powemac
278 platform, thus should generally be enabled.
280 This support is also available as a module. If so, the module
281 will be called i2c-powermac.
284 tristate "MPC107/824x/85xx/52xx/86xx"
287 If you say yes to this option, support will be included for the
288 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
289 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
290 family processors, though interrupts are known not to work.
292 This driver can also be built as a module. If so, the module
293 will be called i2c-mpc.
296 tristate "Nvidia nForce2, nForce3 and nForce4"
299 If you say yes to this option, support will be included for the Nvidia
300 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
302 This driver can also be built as a module. If so, the module
303 will be called i2c-nforce2.
306 tristate "OpenCores I2C Controller"
307 depends on EXPERIMENTAL
309 If you say yes to this option, support will be included for the
310 OpenCores I2C controller. For details see
311 http://www.opencores.org/projects.cgi/web/i2c/overview
313 This driver can also be built as a module. If so, the module
314 will be called i2c-ocores.
317 tristate "OMAP I2C adapter"
319 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
321 If you say yes to this option, support will be included for the
322 I2C interface on the Texas Instruments OMAP1/2 family of processors.
323 Like OMAP1510/1610/1710/5912 and OMAP242x.
324 For details see http://www.ti.com/omap.
327 tristate "Parallel port adapter"
331 This supports parallel port I2C adapters such as the ones made by
332 Philips or Velleman, Analog Devices evaluation boards, and more.
333 Basically any adapter using the parallel port as an I2C bus with
334 no extra chipset is supported by this driver, or could be.
336 This driver is a replacement for (and was inspired by) an older
337 driver named i2c-philips-par. The new driver supports more devices,
338 and makes it easier to add support for new devices.
340 An adapter type parameter is now mandatory. Please read the file
341 Documentation/i2c/busses/i2c-parport for details.
343 Another driver exists, named i2c-parport-light, which doesn't depend
344 on the parport driver. This is meant for embedded systems. Don't say
345 Y here if you intend to say Y or M there.
347 This support is also available as a module. If so, the module
348 will be called i2c-parport.
350 config I2C_PARPORT_LIGHT
351 tristate "Parallel port adapter (light)"
354 This supports parallel port I2C adapters such as the ones made by
355 Philips or Velleman, Analog Devices evaluation boards, and more.
356 Basically any adapter using the parallel port as an I2C bus with
357 no extra chipset is supported by this driver, or could be.
359 This driver is a light version of i2c-parport. It doesn't depend
360 on the parport driver, and uses direct I/O access instead. This
361 might be preferred on embedded systems where wasting memory for
362 the clean but heavy parport handling is not an option. The
363 drawback is a reduced portability and the impossibility to
364 daisy-chain other parallel port devices.
366 Don't say Y here if you said Y or M to i2c-parport. Saying M to
367 both is possible but both modules should not be loaded at the same
370 This support is also available as a module. If so, the module
371 will be called i2c-parport-light.
374 tristate "PA Semi SMBus interface"
375 depends on PPC_PASEMI && PCI
377 Supports the PA Semi PWRficient on-chip SMBus interfaces.
380 tristate "S3/VIA (Pro)Savage"
384 If you say yes to this option, support will be included for the
385 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
388 S3/VIA KM266/VT8375 aka ProSavage8
389 S3/VIA KM133/VT8365 aka Savage4
391 This support is also available as a module. If so, the module
392 will be called i2c-prosavage.
395 tristate "Embedded Planet RPX Lite/Classic support"
396 depends on RPXLITE || RPXCLASSIC
400 tristate "S3C2410 I2C Driver"
401 depends on ARCH_S3C2410
403 Say Y here to include support for I2C controller in the
404 Samsung S3C2410 based System-on-Chip devices.
407 tristate "S3 Savage 4"
408 depends on PCI && EXPERIMENTAL
411 If you say yes to this option, support will be included for the
412 S3 Savage 4 I2C interface.
414 This driver can also be built as a module. If so, the module
415 will be called i2c-savage4.
418 tristate "SiByte SMBus interface"
419 depends on SIBYTE_SB1xxx_SOC
421 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
424 tristate "Simtec Generic I2C interface"
427 If you say yes to this option, support will be inclyded for
428 the Simtec Generic I2C interface. This driver is for the
429 simple I2C bus used on newer Simtec products for general
430 I2C, such as DDC on the Simtec BBD2016A.
432 This driver can also be build as a module. If so, the module
433 will be called i2c-simtec.
436 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
437 depends on SCx200_GPIO
440 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
442 If you don't know what to do here, say N.
444 This support is also available as a module. If so, the module
445 will be called scx200_i2c.
447 This driver is deprecated and will be dropped soon. Use i2c-gpio
448 (or scx200_acb) instead.
450 config SCx200_I2C_SCL
451 int "GPIO pin used for SCL"
452 depends on SCx200_I2C
455 Enter the GPIO pin number used for the SCL signal. This value can
456 also be specified with a module parameter.
458 config SCx200_I2C_SDA
459 int "GPIO pin used for SDA"
460 depends on SCx200_I2C
463 Enter the GPIO pin number used for the SSA signal. This value can
464 also be specified with a module parameter.
467 tristate "Geode ACCESS.bus support"
468 depends on X86_32 && PCI
470 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
471 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
473 If you don't know what to do here, say N.
475 This support is also available as a module. If so, the module
476 will be called scx200_acb.
482 If you say yes to this option, support will be included for the
483 SiS5595 SMBus (a subset of I2C) interface.
485 This driver can also be built as a module. If so, the module
486 will be called i2c-sis5595.
489 tristate "SiS 630/730"
492 If you say yes to this option, support will be included for the
493 SiS630 and SiS730 SMBus (a subset of I2C) interface.
495 This driver can also be built as a module. If so, the module
496 will be called i2c-sis630.
502 If you say yes to this option, support will be included for the SiS
503 96x SMBus (a subset of I2C) interfaces. Specifically, the following
504 chipsets are supported:
513 This driver can also be built as a module. If so, the module
514 will be called i2c-sis96x.
517 tristate "I2C/SMBus Test Stub"
518 depends on EXPERIMENTAL && m
521 This module may be useful to developers of SMBus client drivers,
522 especially for certain kinds of sensor chips.
524 If you do build this module, be sure to read the notes and warnings
525 in <file:Documentation/i2c/i2c-stub>.
527 If you don't know what to do here, definitely say N.
530 tristate "I2C-Tiny-USB"
533 If you say yes to this option, support will be included for the
534 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
535 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
537 This driver can also be built as a module. If so, the module
538 will be called i2c-tiny-usb.
541 tristate "ARM Versatile/Realview I2C bus support"
542 depends on ARCH_VERSATILE || ARCH_REALVIEW
545 Say yes if you want to support the I2C serial bus on ARMs Versatile
548 This driver can also be built as a module. If so, the module
549 will be called i2c-versatile.
552 bool "Acorn IOC/IOMD I2C bus support"
553 depends on ARCH_ACORN
557 Say yes if you want to support the I2C bus on Acorn platforms.
559 If you don't know, say Y.
562 tristate "VIA 82C586B"
563 depends on PCI && EXPERIMENTAL
566 If you say yes to this option, support will be included for the VIA
567 82C586B I2C interface
569 This driver can also be built as a module. If so, the module
570 will be called i2c-via.
573 tristate "VIA VT82C596/82C686/82xx and CX700"
576 If you say yes to this option, support will be included for the VIA
577 VT82C596 and later SMBus interface. Specifically, the following
578 chipsets are supported:
588 This driver can also be built as a module. If so, the module
589 will be called i2c-viapro.
596 If you say yes to this option, support will be included for the
597 Voodoo 3 I2C interface.
599 This driver can also be built as a module. If so, the module
600 will be called i2c-voodoo3.
603 tristate "PCA9564 on an ISA bus"
608 This driver supports ISA boards using the Philips PCA 9564
609 Parallel bus to I2C bus controller
611 This driver can also be built as a module. If so, the module
612 will be called i2c-pca-isa.
614 This device is almost undetectable and using this driver on a
615 system which doesn't have this device will result in long
616 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
617 time). If unsure, say N.
620 tristate "Marvell mv64xxx I2C Controller"
621 depends on MV64X60 && EXPERIMENTAL
623 If you say yes to this option, support will be included for the
624 built-in I2C interface on the Marvell 64xxx line of host bridges.
626 This driver can also be built as a module. If so, the module
627 will be called i2c-mv64xxx.
630 tristate "I2C bus support for Philips PNX targets"
631 depends on ARCH_PNX4008
633 This driver supports the Philips IP3204 I2C IP block master and/or
636 This driver can also be built as a module. If so, the module
637 will be called i2c-pnx.