2 # Sensor device configuration
5 menu "I2C Hardware Bus support"
12 If you say yes to this option, support will be included for the SMB
13 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
14 controller is part of the 7101 device, which is an ACPI-compliant
15 Power Management Unit (PMU).
17 This driver can also be built as a module. If so, the module
18 will be called i2c-ali1535.
22 depends on I2C && PCI && EXPERIMENTAL
24 If you say yes to this option, support will be included for the SMB
25 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
26 controller is part of the 7101 device, which is an ACPI-compliant
27 Power Management Unit (PMU).
29 This driver can also be built as a module. If so, the module
30 will be called i2c-ali1563.
36 If you say yes to this option, support will be included for the
37 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
39 This driver can also be built as a module. If so, the module
40 will be called i2c-ali15x3.
43 tristate "AMD 756/766/768/8111 and nVidia nForce"
46 If you say yes to this option, support will be included for the AMD
47 756/766/768 mainboard I2C interfaces. The driver also includes
48 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
49 the nVidia nForce I2C interface.
51 This driver can also be built as a module. If so, the module
52 will be called i2c-amd756.
54 config I2C_AMD756_S4882
55 tristate "SMBus multiplexing on the Tyan S4882"
56 depends on I2C_AMD756 && EXPERIMENTAL
58 Enabling this option will add specific SMBus support for the Tyan
59 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
60 over 8 different channels, where the various memory module EEPROMs
61 and temperature sensors live. Saying yes here will give you access
62 to these in addition to the trunk.
64 This driver can also be built as a module. If so, the module
65 will be called i2c-amd756-s4882.
71 If you say yes to this option, support will be included for the
72 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
74 This driver can also be built as a module. If so, the module
75 will be called i2c-amd8111.
78 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
79 depends on I2C && ARCH_AT91 && EXPERIMENTAL
81 This supports the use of the I2C interface on Atmel AT91
85 tristate "Au1550/Au1200 SMBus interface"
86 depends on I2C && (SOC_AU1550 || SOC_AU1200)
88 If you say yes to this option, support will be included for the
89 Au1550 and Au1200 SMBus interface.
91 This driver can also be built as a module. If so, the module
92 will be called i2c-au1550.
95 tristate "Elektor ISA card"
96 depends on I2C && ISA && BROKEN_ON_SMP
99 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
102 This support is also available as a module. If so, the module
103 will be called i2c-elektor.
106 tristate "CHRP Apple Hydra Mac I/O I2C interface"
107 depends on I2C && PCI && PPC_CHRP && EXPERIMENTAL
110 This supports the use of the I2C interface in the Apple Hydra Mac
111 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
114 This support is also available as a module. If so, the module
115 will be called i2c-hydra.
118 tristate "Intel 82801 (ICH)"
119 depends on I2C && PCI
121 If you say yes to this option, support will be included for the Intel
122 801 family of mainboard I2C interfaces. Specifically, the following
123 versions of the chipset are supported:
129 82801EB/ER (ICH5/ICH5R)
137 This driver can also be built as a module. If so, the module
138 will be called i2c-i801.
141 tristate "Intel 810/815"
142 depends on I2C && PCI
145 If you say yes to this option, support will be included for the Intel
146 810/815 family of mainboard I2C interfaces. Specifically, the
147 following versions of the chipset are supported:
154 This driver can also be built as a module. If so, the module
155 will be called i2c-i810.
158 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
159 depends on I2C && EXPERIMENTAL && ARCH_PXA
161 If you have devices in the PXA I2C bus, say yes to this option.
162 This driver can also be built as a module. If so, the module
163 will be called i2c-pxa.
166 bool "Intel PXA2XX I2C Slave comms support"
169 Support I2C slave mode communications on the PXA I2C bus. This
170 is necessary for systems where the PXA may be a target on the
174 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
175 depends on I2C && PCI
177 If you say yes to this option, support will be included for the Intel
178 PIIX4 family of mainboard I2C interfaces. Specifically, the following
179 versions of the chipset are supported (note that Serverworks is part
193 This driver can also be built as a module. If so, the module
194 will be called i2c-piix4.
197 tristate "IBM PPC 4xx on-chip I2C interface"
198 depends on IBM_OCP && I2C
200 Say Y here if you want to use IIC peripheral found on
201 embedded IBM PPC 4xx based systems.
203 This driver can also be built as a module. If so, the module
204 will be called i2c-ibm_iic.
207 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
208 depends on (ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX) && I2C
210 Say Y here if you want to use the IIC bus controller on
211 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
213 This driver can also be built as a module. If so, the module
214 will be called i2c-iop3xx.
221 tristate "IXP4xx GPIO-Based I2C Interface"
222 depends on I2C && ARCH_IXP4XX
225 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
226 system and are using GPIO lines for an I2C bus.
228 This support is also available as a module. If so, the module
229 will be called i2c-ixp4xx.
232 tristate "IXP2000 GPIO-Based I2C Interface"
233 depends on I2C && ARCH_IXP2000
236 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
237 system and are using GPIO lines for an I2C bus.
239 This support is also available as a module. If so, the module
240 will be called i2c-ixp2000.
243 tristate "Powermac I2C interface"
244 depends on I2C && PPC_PMAC
247 This exposes the various PowerMac i2c interfaces to the linux i2c
248 layer and to userland. It is used by various drivers on the powemac
249 platform, thus should generally be enabled.
251 This support is also available as a module. If so, the module
252 will be called i2c-powermac.
255 tristate "MPC107/824x/85xx/52xx/86xx"
256 depends on I2C && PPC32
258 If you say yes to this option, support will be included for the
259 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
260 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
261 family processors, though interrupts are known not to work.
263 This driver can also be built as a module. If so, the module
264 will be called i2c-mpc.
267 tristate "Nvidia nForce2, nForce3 and nForce4"
268 depends on I2C && PCI
270 If you say yes to this option, support will be included for the Nvidia
271 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
273 This driver can also be built as a module. If so, the module
274 will be called i2c-nforce2.
277 tristate "OpenCores I2C Controller"
278 depends on I2C && EXPERIMENTAL
280 If you say yes to this option, support will be included for the
281 OpenCores I2C controller. For details see
282 http://www.opencores.org/projects.cgi/web/i2c/overview
284 This driver can also be built as a module. If so, the module
285 will be called i2c-ocores.
288 tristate "OMAP I2C adapter"
289 depends on I2C && ARCH_OMAP
290 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
292 If you say yes to this option, support will be included for the
293 I2C interface on the Texas Instruments OMAP1/2 family of processors.
294 Like OMAP1510/1610/1710/5912 and OMAP242x.
295 For details see http://www.ti.com/omap.
298 tristate "Parallel port adapter"
299 depends on I2C && PARPORT
302 This supports parallel port I2C adapters such as the ones made by
303 Philips or Velleman, Analog Devices evaluation boards, and more.
304 Basically any adapter using the parallel port as an I2C bus with
305 no extra chipset is supported by this driver, or could be.
307 This driver is a replacement for (and was inspired by) an older
308 driver named i2c-philips-par. The new driver supports more devices,
309 and makes it easier to add support for new devices.
311 An adapter type parameter is now mandatory. Please read the file
312 Documentation/i2c/busses/i2c-parport for details.
314 Another driver exists, named i2c-parport-light, which doesn't depend
315 on the parport driver. This is meant for embedded systems. Don't say
316 Y here if you intend to say Y or M there.
318 This support is also available as a module. If so, the module
319 will be called i2c-parport.
321 config I2C_PARPORT_LIGHT
322 tristate "Parallel port adapter (light)"
326 This supports parallel port I2C adapters such as the ones made by
327 Philips or Velleman, Analog Devices evaluation boards, and more.
328 Basically any adapter using the parallel port as an I2C bus with
329 no extra chipset is supported by this driver, or could be.
331 This driver is a light version of i2c-parport. It doesn't depend
332 on the parport driver, and uses direct I/O access instead. This
333 might be preferred on embedded systems where wasting memory for
334 the clean but heavy parport handling is not an option. The
335 drawback is a reduced portability and the impossibility to
336 daisy-chain other parallel port devices.
338 Don't say Y here if you said Y or M to i2c-parport. Saying M to
339 both is possible but both modules should not be loaded at the same
342 This support is also available as a module. If so, the module
343 will be called i2c-parport-light.
346 tristate "S3/VIA (Pro)Savage"
347 depends on I2C && PCI
350 If you say yes to this option, support will be included for the
351 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
354 S3/VIA KM266/VT8375 aka ProSavage8
355 S3/VIA KM133/VT8365 aka Savage4
357 This support is also available as a module. If so, the module
358 will be called i2c-prosavage.
361 tristate "Embedded Planet RPX Lite/Classic support"
362 depends on (RPXLITE || RPXCLASSIC) && I2C
366 tristate "S3C2410 I2C Driver"
367 depends on I2C && ARCH_S3C2410
369 Say Y here to include support for I2C controller in the
370 Samsung S3C2410 based System-on-Chip devices.
373 tristate "S3 Savage 4"
374 depends on I2C && PCI && EXPERIMENTAL
377 If you say yes to this option, support will be included for the
378 S3 Savage 4 I2C interface.
380 This driver can also be built as a module. If so, the module
381 will be called i2c-savage4.
384 tristate "SiByte SMBus interface"
385 depends on SIBYTE_SB1xxx_SOC && I2C
387 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
390 tristate "NatSemi SCx200 I2C using GPIO pins"
391 depends on SCx200_GPIO && I2C
394 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
396 If you don't know what to do here, say N.
398 This support is also available as a module. If so, the module
399 will be called scx200_i2c.
401 config SCx200_I2C_SCL
402 int "GPIO pin used for SCL"
403 depends on SCx200_I2C
406 Enter the GPIO pin number used for the SCL signal. This value can
407 also be specified with a module parameter.
409 config SCx200_I2C_SDA
410 int "GPIO pin used for SDA"
411 depends on SCx200_I2C
414 Enter the GPIO pin number used for the SSA signal. This value can
415 also be specified with a module parameter.
418 tristate "Geode ACCESS.bus support"
419 depends on X86_32 && I2C && PCI
421 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
422 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
424 If you don't know what to do here, say N.
426 This support is also available as a module. If so, the module
427 will be called scx200_acb.
431 depends on I2C && PCI
433 If you say yes to this option, support will be included for the
434 SiS5595 SMBus (a subset of I2C) interface.
436 This driver can also be built as a module. If so, the module
437 will be called i2c-sis5595.
440 tristate "SiS 630/730"
441 depends on I2C && PCI
443 If you say yes to this option, support will be included for the
444 SiS630 and SiS730 SMBus (a subset of I2C) interface.
446 This driver can also be built as a module. If so, the module
447 will be called i2c-sis630.
451 depends on I2C && PCI
453 If you say yes to this option, support will be included for the SiS
454 96x SMBus (a subset of I2C) interfaces. Specifically, the following
455 chipsets are supported:
464 This driver can also be built as a module. If so, the module
465 will be called i2c-sis96x.
468 tristate "I2C/SMBus Test Stub"
469 depends on I2C && EXPERIMENTAL && 'm'
472 This module may be useful to developers of SMBus client drivers,
473 especially for certain kinds of sensor chips.
475 If you do build this module, be sure to read the notes and warnings
476 in <file:Documentation/i2c/i2c-stub>.
478 If you don't know what to do here, definitely say N.
481 tristate "ARM Versatile/Realview I2C bus support"
482 depends on I2C && (ARCH_VERSATILE || ARCH_REALVIEW)
485 Say yes if you want to support the I2C serial bus on ARMs Versatile
488 This driver can also be built as a module. If so, the module
489 will be called i2c-versatile.
492 tristate "VIA 82C586B"
493 depends on I2C && PCI && EXPERIMENTAL
496 If you say yes to this option, support will be included for the VIA
497 82C586B I2C interface
499 This driver can also be built as a module. If so, the module
500 will be called i2c-via.
503 tristate "VIA VT82C596/82C686/82xx and CX700"
504 depends on I2C && PCI
506 If you say yes to this option, support will be included for the VIA
507 VT82C596 and later SMBus interface. Specifically, the following
508 chipsets are supported:
518 This driver can also be built as a module. If so, the module
519 will be called i2c-viapro.
523 depends on I2C && PCI
526 If you say yes to this option, support will be included for the
527 Voodoo 3 I2C interface.
529 This driver can also be built as a module. If so, the module
530 will be called i2c-voodoo3.
533 tristate "PCA9564 on an ISA bus"
538 This driver supports ISA boards using the Philips PCA 9564
539 Parallel bus to I2C bus controller
541 This driver can also be built as a module. If so, the module
542 will be called i2c-pca-isa.
544 This device is almost undetectable and using this driver on a
545 system which doesn't have this device will result in long
546 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
547 time). If unsure, say N.
550 tristate "Marvell mv64xxx I2C Controller"
551 depends on I2C && MV64X60 && EXPERIMENTAL
553 If you say yes to this option, support will be included for the
554 built-in I2C interface on the Marvell 64xxx line of host bridges.
556 This driver can also be built as a module. If so, the module
557 will be called i2c-mv64xxx.
560 tristate "I2C bus support for Philips PNX targets"
561 depends on ARCH_PNX4008 && I2C
563 This driver supports the Philips IP3204 I2C IP block master and/or
566 This driver can also be built as a module. If so, the module
567 will be called i2c-pnx.