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 "Au1550/Au1200 SMBus interface"
79 depends on I2C && (SOC_AU1550 || SOC_AU1200)
81 If you say yes to this option, support will be included for the
82 Au1550 and Au1200 SMBus interface.
84 This driver can also be built as a module. If so, the module
85 will be called i2c-au1550.
88 tristate "Elektor ISA card"
89 depends on I2C && ISA && BROKEN_ON_SMP
92 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
95 This support is also available as a module. If so, the module
96 will be called i2c-elektor.
99 tristate "CHRP Apple Hydra Mac I/O I2C interface"
100 depends on I2C && PCI && PPC_CHRP && EXPERIMENTAL
103 This supports the use of the I2C interface in the Apple Hydra Mac
104 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
107 This support is also available as a module. If so, the module
108 will be called i2c-hydra.
111 tristate "Intel 82801 (ICH)"
112 depends on I2C && PCI
114 If you say yes to this option, support will be included for the Intel
115 801 family of mainboard I2C interfaces. Specifically, the following
116 versions of the chipset are supported:
122 82801EB/ER (ICH5/ICH5R)
129 This driver can also be built as a module. If so, the module
130 will be called i2c-i801.
133 tristate "Intel 810/815"
134 depends on I2C && PCI
137 If you say yes to this option, support will be included for the Intel
138 810/815 family of mainboard I2C interfaces. Specifically, the
139 following versions of the chipset are supported:
146 This driver can also be built as a module. If so, the module
147 will be called i2c-i810.
150 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
151 depends on I2C && EXPERIMENTAL && ARCH_PXA
153 If you have devices in the PXA I2C bus, say yes to this option.
154 This driver can also be built as a module. If so, the module
155 will be called i2c-pxa.
158 bool "Intel PXA2XX I2C Slave comms support"
161 Support I2C slave mode communications on the PXA I2C bus. This
162 is necessary for systems where the PXA may be a target on the
166 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
167 depends on I2C && PCI
169 If you say yes to this option, support will be included for the Intel
170 PIIX4 family of mainboard I2C interfaces. Specifically, the following
171 versions of the chipset are supported (note that Serverworks is part
184 This driver can also be built as a module. If so, the module
185 will be called i2c-piix4.
188 tristate "IBM PPC 4xx on-chip I2C interface"
189 depends on IBM_OCP && I2C
191 Say Y here if you want to use IIC peripheral found on
192 embedded IBM PPC 4xx based systems.
194 This driver can also be built as a module. If so, the module
195 will be called i2c-ibm_iic.
198 tristate "Intel IOP3xx and IXP4xx on-chip I2C interface"
199 depends on (ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX) && I2C
201 Say Y here if you want to use the IIC bus controller on
202 the Intel IOP3xx I/O Processors or IXP4xx Network Processors.
204 This driver can also be built as a module. If so, the module
205 will be called i2c-iop3xx.
212 tristate "ITE I2C Adapter"
213 depends on I2C && MIPS_ITE8172
216 This supports the ITE8172 I2C peripheral found on some MIPS
217 systems. Say Y if you have one of these. You should also say Y for
218 the ITE I2C driver algorithm support above.
220 This support is also available as a module. If so, the module
221 will be called i2c-ite.
224 tristate "IXP4xx GPIO-Based I2C Interface"
225 depends on I2C && ARCH_IXP4XX
228 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
229 system and are using GPIO lines for an I2C bus.
231 This support is also available as a module. If so, the module
232 will be called i2c-ixp4xx.
235 tristate "IXP2000 GPIO-Based I2C Interface"
236 depends on I2C && ARCH_IXP2000
239 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
240 system and are using GPIO lines for an I2C bus.
242 This support is also available as a module. If so, the module
243 will be called i2c-ixp2000.
246 tristate "Powermac I2C interface"
247 depends on I2C && PPC_PMAC
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 powemac
252 platform, thus should generally be enabled.
254 This support is also available as a module. If so, the module
255 will be called i2c-powermac.
258 tristate "MCF ColdFire"
259 depends on I2C && EXPERIMENTAL
261 If you say yes to this option, support will be included for the
262 I2C on most ColdFire CPUs
264 This driver can also be built as a module. If so, the module
265 will be called i2c-mcf.
268 tristate "MPC107/824x/85xx/52xx/86xx"
269 depends on I2C && PPC32
271 If you say yes to this option, support will be included for the
272 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
273 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
274 family processors, though interrupts are known not to work.
276 This driver can also be built as a module. If so, the module
277 will be called i2c-mpc.
280 tristate "Nvidia nForce2, nForce3 and nForce4"
281 depends on I2C && PCI
283 If you say yes to this option, support will be included for the Nvidia
284 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
286 This driver can also be built as a module. If so, the module
287 will be called i2c-nforce2.
290 tristate "OpenCores I2C Controller"
291 depends on I2C && EXPERIMENTAL
293 If you say yes to this option, support will be included for the
294 OpenCores I2C controller. For details see
295 http://www.opencores.org/projects.cgi/web/i2c/overview
297 This driver can also be built as a module. If so, the module
298 will be called i2c-ocores.
301 tristate "OMAP I2C adapter"
302 depends on I2C && ARCH_OMAP
303 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
305 If you say yes to this option, support will be included for the
306 I2C interface on the Texas Instruments OMAP1/2 family of processors.
307 Like OMAP1510/1610/1710/5912 and OMAP242x.
308 For details see http://www.ti.com/omap.
311 tristate "Parallel port adapter"
312 depends on I2C && PARPORT
315 This supports parallel port I2C adapters such as the ones made by
316 Philips or Velleman, Analog Devices evaluation boards, and more.
317 Basically any adapter using the parallel port as an I2C bus with
318 no extra chipset is supported by this driver, or could be.
320 This driver is a replacement for (and was inspired by) an older
321 driver named i2c-philips-par. The new driver supports more devices,
322 and makes it easier to add support for new devices.
324 An adapter type parameter is now mandatory. Please read the file
325 Documentation/i2c/busses/i2c-parport for details.
327 Another driver exists, named i2c-parport-light, which doesn't depend
328 on the parport driver. This is meant for embedded systems. Don't say
329 Y here if you intend to say Y or M there.
331 This support is also available as a module. If so, the module
332 will be called i2c-parport.
334 config I2C_PARPORT_LIGHT
335 tristate "Parallel port adapter (light)"
339 This supports parallel port I2C adapters such as the ones made by
340 Philips or Velleman, Analog Devices evaluation boards, and more.
341 Basically any adapter using the parallel port as an I2C bus with
342 no extra chipset is supported by this driver, or could be.
344 This driver is a light version of i2c-parport. It doesn't depend
345 on the parport driver, and uses direct I/O access instead. This
346 might be preferred on embedded systems where wasting memory for
347 the clean but heavy parport handling is not an option. The
348 drawback is a reduced portability and the impossibility to
349 daisy-chain other parallel port devices.
351 Don't say Y here if you said Y or M to i2c-parport. Saying M to
352 both is possible but both modules should not be loaded at the same
355 This support is also available as a module. If so, the module
356 will be called i2c-parport-light.
359 tristate "S3/VIA (Pro)Savage"
360 depends on I2C && PCI
363 If you say yes to this option, support will be included for the
364 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
367 S3/VIA KM266/VT8375 aka ProSavage8
368 S3/VIA KM133/VT8365 aka Savage4
370 This support is also available as a module. If so, the module
371 will be called i2c-prosavage.
374 tristate "Embedded Planet RPX Lite/Classic support"
375 depends on (RPXLITE || RPXCLASSIC) && I2C
379 tristate "S3C2410 I2C Driver"
380 depends on I2C && ARCH_S3C2410
382 Say Y here to include support for I2C controller in the
383 Samsung S3C2410 based System-on-Chip devices.
386 tristate "S3 Savage 4"
387 depends on I2C && PCI && EXPERIMENTAL
390 If you say yes to this option, support will be included for the
391 S3 Savage 4 I2C interface.
393 This driver can also be built as a module. If so, the module
394 will be called i2c-savage4.
397 tristate "SiByte SMBus interface"
398 depends on SIBYTE_SB1xxx_SOC && I2C
400 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
403 tristate "NatSemi SCx200 I2C using GPIO pins"
404 depends on SCx200_GPIO && I2C
407 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
409 If you don't know what to do here, say N.
411 This support is also available as a module. If so, the module
412 will be called scx200_i2c.
414 config SCx200_I2C_SCL
415 int "GPIO pin used for SCL"
416 depends on SCx200_I2C
419 Enter the GPIO pin number used for the SCL signal. This value can
420 also be specified with a module parameter.
422 config SCx200_I2C_SDA
423 int "GPIO pin used for SDA"
424 depends on SCx200_I2C
427 Enter the GPIO pin number used for the SSA signal. This value can
428 also be specified with a module parameter.
431 tristate "Geode ACCESS.bus support"
432 depends on X86_32 && I2C && PCI
434 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
435 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
437 If you don't know what to do here, say N.
439 This support is also available as a module. If so, the module
440 will be called scx200_acb.
444 depends on I2C && PCI
446 If you say yes to this option, support will be included for the
447 SiS5595 SMBus (a subset of I2C) interface.
449 This driver can also be built as a module. If so, the module
450 will be called i2c-sis5595.
453 tristate "SiS 630/730"
454 depends on I2C && PCI
456 If you say yes to this option, support will be included for the
457 SiS630 and SiS730 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-sis630.
464 depends on I2C && PCI
466 If you say yes to this option, support will be included for the SiS
467 96x SMBus (a subset of I2C) interfaces. Specifically, the following
468 chipsets are supported:
477 This driver can also be built as a module. If so, the module
478 will be called i2c-sis96x.
481 tristate "I2C/SMBus Test Stub"
482 depends on I2C && EXPERIMENTAL && 'm'
485 This module may be useful to developers of SMBus client drivers,
486 especially for certain kinds of sensor chips.
488 If you do build this module, be sure to read the notes and warnings
489 in <file:Documentation/i2c/i2c-stub>.
491 If you don't know what to do here, definitely say N.
494 tristate "VIA 82C586B"
495 depends on I2C && PCI && EXPERIMENTAL
498 If you say yes to this option, support will be included for the VIA
499 82C586B I2C interface
501 This driver can also be built as a module. If so, the module
502 will be called i2c-via.
505 tristate "VIA 82C596/82C686/82xx"
506 depends on I2C && PCI
508 If you say yes to this option, support will be included for the VIA
509 82C596/82C686/82xx I2C interfaces. Specifically, the following
510 chipsets are supported:
519 This driver can also be built as a module. If so, the module
520 will be called i2c-viapro.
524 depends on I2C && PCI
527 If you say yes to this option, support will be included for the
528 Voodoo 3 I2C interface.
530 This driver can also be built as a module. If so, the module
531 will be called i2c-voodoo3.
534 tristate "PCA9564 on an ISA bus"
539 This driver supports ISA boards using the Philips PCA 9564
540 Parallel bus to I2C bus controller
542 This driver can also be built as a module. If so, the module
543 will be called i2c-pca-isa.
545 This device is almost undetectable and using this driver on a
546 system which doesn't have this device will result in long
547 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
548 time). If unsure, say N.
551 tristate "Marvell mv64xxx I2C Controller"
552 depends on I2C && MV64X60 && EXPERIMENTAL
554 If you say yes to this option, support will be included for the
555 built-in I2C interface on the Marvell 64xxx line of host bridges.
557 This driver can also be built as a module. If so, the module
558 will be called i2c-mv64xxx.