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)
130 This driver can also be built as a module. If so, the module
131 will be called i2c-i801.
134 tristate "Intel 810/815"
135 depends on I2C && PCI
138 If you say yes to this option, support will be included for the Intel
139 810/815 family of mainboard I2C interfaces. Specifically, the
140 following versions of the chipset are supported:
147 This driver can also be built as a module. If so, the module
148 will be called i2c-i810.
151 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
152 depends on I2C && EXPERIMENTAL && ARCH_PXA
154 If you have devices in the PXA I2C bus, say yes to this option.
155 This driver can also be built as a module. If so, the module
156 will be called i2c-pxa.
159 bool "Intel PXA2XX I2C Slave comms support"
162 Support I2C slave mode communications on the PXA I2C bus. This
163 is necessary for systems where the PXA may be a target on the
167 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
168 depends on I2C && PCI
170 If you say yes to this option, support will be included for the Intel
171 PIIX4 family of mainboard I2C interfaces. Specifically, the following
172 versions of the chipset are supported (note that Serverworks is part
185 This driver can also be built as a module. If so, the module
186 will be called i2c-piix4.
189 tristate "IBM PPC 4xx on-chip I2C interface"
190 depends on IBM_OCP && I2C
192 Say Y here if you want to use IIC peripheral found on
193 embedded IBM PPC 4xx based systems.
195 This driver can also be built as a module. If so, the module
196 will be called i2c-ibm_iic.
199 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
200 depends on (ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX) && I2C
202 Say Y here if you want to use the IIC bus controller on
203 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
205 This driver can also be built as a module. If so, the module
206 will be called i2c-iop3xx.
213 tristate "IXP4xx GPIO-Based I2C Interface"
214 depends on I2C && ARCH_IXP4XX
217 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
218 system and are using GPIO lines for an I2C bus.
220 This support is also available as a module. If so, the module
221 will be called i2c-ixp4xx.
224 tristate "IXP2000 GPIO-Based I2C Interface"
225 depends on I2C && ARCH_IXP2000
228 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) 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-ixp2000.
235 tristate "Powermac I2C interface"
236 depends on I2C && PPC_PMAC
239 This exposes the various PowerMac i2c interfaces to the linux i2c
240 layer and to userland. It is used by various drivers on the powemac
241 platform, thus should generally be enabled.
243 This support is also available as a module. If so, the module
244 will be called i2c-powermac.
247 tristate "MPC107/824x/85xx/52xx/86xx"
248 depends on I2C && PPC32
250 If you say yes to this option, support will be included for the
251 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
252 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
253 family processors, though interrupts are known not to work.
255 This driver can also be built as a module. If so, the module
256 will be called i2c-mpc.
259 tristate "Nvidia nForce2, nForce3 and nForce4"
260 depends on I2C && PCI
262 If you say yes to this option, support will be included for the Nvidia
263 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
265 This driver can also be built as a module. If so, the module
266 will be called i2c-nforce2.
269 tristate "OpenCores I2C Controller"
270 depends on I2C && EXPERIMENTAL
272 If you say yes to this option, support will be included for the
273 OpenCores I2C controller. For details see
274 http://www.opencores.org/projects.cgi/web/i2c/overview
276 This driver can also be built as a module. If so, the module
277 will be called i2c-ocores.
280 tristate "OMAP I2C adapter"
281 depends on I2C && ARCH_OMAP
282 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
284 If you say yes to this option, support will be included for the
285 I2C interface on the Texas Instruments OMAP1/2 family of processors.
286 Like OMAP1510/1610/1710/5912 and OMAP242x.
287 For details see http://www.ti.com/omap.
290 tristate "Parallel port adapter"
291 depends on I2C && PARPORT
294 This supports parallel port I2C adapters such as the ones made by
295 Philips or Velleman, Analog Devices evaluation boards, and more.
296 Basically any adapter using the parallel port as an I2C bus with
297 no extra chipset is supported by this driver, or could be.
299 This driver is a replacement for (and was inspired by) an older
300 driver named i2c-philips-par. The new driver supports more devices,
301 and makes it easier to add support for new devices.
303 An adapter type parameter is now mandatory. Please read the file
304 Documentation/i2c/busses/i2c-parport for details.
306 Another driver exists, named i2c-parport-light, which doesn't depend
307 on the parport driver. This is meant for embedded systems. Don't say
308 Y here if you intend to say Y or M there.
310 This support is also available as a module. If so, the module
311 will be called i2c-parport.
313 config I2C_PARPORT_LIGHT
314 tristate "Parallel port adapter (light)"
318 This supports parallel port I2C adapters such as the ones made by
319 Philips or Velleman, Analog Devices evaluation boards, and more.
320 Basically any adapter using the parallel port as an I2C bus with
321 no extra chipset is supported by this driver, or could be.
323 This driver is a light version of i2c-parport. It doesn't depend
324 on the parport driver, and uses direct I/O access instead. This
325 might be preferred on embedded systems where wasting memory for
326 the clean but heavy parport handling is not an option. The
327 drawback is a reduced portability and the impossibility to
328 daisy-chain other parallel port devices.
330 Don't say Y here if you said Y or M to i2c-parport. Saying M to
331 both is possible but both modules should not be loaded at the same
334 This support is also available as a module. If so, the module
335 will be called i2c-parport-light.
338 tristate "S3/VIA (Pro)Savage"
339 depends on I2C && PCI
342 If you say yes to this option, support will be included for the
343 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
346 S3/VIA KM266/VT8375 aka ProSavage8
347 S3/VIA KM133/VT8365 aka Savage4
349 This support is also available as a module. If so, the module
350 will be called i2c-prosavage.
353 tristate "Embedded Planet RPX Lite/Classic support"
354 depends on (RPXLITE || RPXCLASSIC) && I2C
358 tristate "S3C2410 I2C Driver"
359 depends on I2C && ARCH_S3C2410
361 Say Y here to include support for I2C controller in the
362 Samsung S3C2410 based System-on-Chip devices.
365 tristate "S3 Savage 4"
366 depends on I2C && PCI && EXPERIMENTAL
369 If you say yes to this option, support will be included for the
370 S3 Savage 4 I2C interface.
372 This driver can also be built as a module. If so, the module
373 will be called i2c-savage4.
376 tristate "SiByte SMBus interface"
377 depends on SIBYTE_SB1xxx_SOC && I2C
379 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
382 tristate "NatSemi SCx200 I2C using GPIO pins"
383 depends on SCx200_GPIO && I2C
386 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
388 If you don't know what to do here, say N.
390 This support is also available as a module. If so, the module
391 will be called scx200_i2c.
393 config SCx200_I2C_SCL
394 int "GPIO pin used for SCL"
395 depends on SCx200_I2C
398 Enter the GPIO pin number used for the SCL signal. This value can
399 also be specified with a module parameter.
401 config SCx200_I2C_SDA
402 int "GPIO pin used for SDA"
403 depends on SCx200_I2C
406 Enter the GPIO pin number used for the SSA signal. This value can
407 also be specified with a module parameter.
410 tristate "Geode ACCESS.bus support"
411 depends on X86_32 && I2C && PCI
413 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
414 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
416 If you don't know what to do here, say N.
418 This support is also available as a module. If so, the module
419 will be called scx200_acb.
423 depends on I2C && PCI
425 If you say yes to this option, support will be included for the
426 SiS5595 SMBus (a subset of I2C) interface.
428 This driver can also be built as a module. If so, the module
429 will be called i2c-sis5595.
432 tristate "SiS 630/730"
433 depends on I2C && PCI
435 If you say yes to this option, support will be included for the
436 SiS630 and SiS730 SMBus (a subset of I2C) interface.
438 This driver can also be built as a module. If so, the module
439 will be called i2c-sis630.
443 depends on I2C && PCI
445 If you say yes to this option, support will be included for the SiS
446 96x SMBus (a subset of I2C) interfaces. Specifically, the following
447 chipsets are supported:
456 This driver can also be built as a module. If so, the module
457 will be called i2c-sis96x.
460 tristate "I2C/SMBus Test Stub"
461 depends on I2C && EXPERIMENTAL && 'm'
464 This module may be useful to developers of SMBus client drivers,
465 especially for certain kinds of sensor chips.
467 If you do build this module, be sure to read the notes and warnings
468 in <file:Documentation/i2c/i2c-stub>.
470 If you don't know what to do here, definitely say N.
473 tristate "VIA 82C586B"
474 depends on I2C && PCI && EXPERIMENTAL
477 If you say yes to this option, support will be included for the VIA
478 82C586B I2C interface
480 This driver can also be built as a module. If so, the module
481 will be called i2c-via.
484 tristate "VIA 82C596/82C686/82xx"
485 depends on I2C && PCI
487 If you say yes to this option, support will be included for the VIA
488 82C596/82C686/82xx I2C interfaces. Specifically, the following
489 chipsets are supported:
498 This driver can also be built as a module. If so, the module
499 will be called i2c-viapro.
503 depends on I2C && PCI
506 If you say yes to this option, support will be included for the
507 Voodoo 3 I2C interface.
509 This driver can also be built as a module. If so, the module
510 will be called i2c-voodoo3.
513 tristate "PCA9564 on an ISA bus"
518 This driver supports ISA boards using the Philips PCA 9564
519 Parallel bus to I2C bus controller
521 This driver can also be built as a module. If so, the module
522 will be called i2c-pca-isa.
524 This device is almost undetectable and using this driver on a
525 system which doesn't have this device will result in long
526 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
527 time). If unsure, say N.
530 tristate "Marvell mv64xxx I2C Controller"
531 depends on I2C && MV64X60 && EXPERIMENTAL
533 If you say yes to this option, support will be included for the
534 built-in I2C interface on the Marvell 64xxx line of host bridges.
536 This driver can also be built as a module. If so, the module
537 will be called i2c-mv64xxx.
540 tristate "I2C bus support for Philips PNX targets"
541 depends on ARCH_PNX4008 && I2C
543 This driver supports the Philips IP3204 I2C IP block master and/or
546 This driver can also be built as a module. If so, the module
547 will be called i2c-pnx.
550 bool "Early initialization for I2C on PNXxxxx"
553 Under certain circumstances one may need to make sure I2C on PNXxxxx
554 is initialized earlier than some other driver that depends on it
555 (for instance, that might be USB in case of PNX4008). With this
556 option turned on you can guarantee that.