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 SMBus interface"
79 depends on I2C && SOC_AU1550
81 If you say yes to this option, support will be included for the
82 Au1550 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_IOP3XX || 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 "MPC107/824x/85xx/52xx"
259 depends on I2C && PPC32
261 If you say yes to this option, support will be included for the
262 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
263 MPC85xx family processors. The driver may also work on 52xx
264 family processors, though interrupts are known not to work.
266 This driver can also be built as a module. If so, the module
267 will be called i2c-mpc.
270 tristate "Nvidia nForce2, nForce3 and nForce4"
271 depends on I2C && PCI
273 If you say yes to this option, support will be included for the Nvidia
274 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
276 This driver can also be built as a module. If so, the module
277 will be called i2c-nforce2.
280 tristate "Parallel port adapter"
281 depends on I2C && PARPORT
284 This supports parallel port I2C adapters such as the ones made by
285 Philips or Velleman, Analog Devices evaluation boards, and more.
286 Basically any adapter using the parallel port as an I2C bus with
287 no extra chipset is supported by this driver, or could be.
289 This driver is a replacement for (and was inspired by) an older
290 driver named i2c-philips-par. The new driver supports more devices,
291 and makes it easier to add support for new devices.
293 An adapter type parameter is now mandatory. Please read the file
294 Documentation/i2c/busses/i2c-parport for details.
296 Another driver exists, named i2c-parport-light, which doesn't depend
297 on the parport driver. This is meant for embedded systems. Don't say
298 Y here if you intend to say Y or M there.
300 This support is also available as a module. If so, the module
301 will be called i2c-parport.
303 config I2C_PARPORT_LIGHT
304 tristate "Parallel port adapter (light)"
308 This supports parallel port I2C adapters such as the ones made by
309 Philips or Velleman, Analog Devices evaluation boards, and more.
310 Basically any adapter using the parallel port as an I2C bus with
311 no extra chipset is supported by this driver, or could be.
313 This driver is a light version of i2c-parport. It doesn't depend
314 on the parport driver, and uses direct I/O access instead. This
315 might be prefered on embedded systems where wasting memory for
316 the clean but heavy parport handling is not an option. The
317 drawback is a reduced portability and the impossibility to
318 dasiy-chain other parallel port devices.
320 Don't say Y here if you said Y or M to i2c-parport. Saying M to
321 both is possible but both modules should not be loaded at the same
324 This support is also available as a module. If so, the module
325 will be called i2c-parport-light.
328 tristate "S3/VIA (Pro)Savage"
329 depends on I2C && PCI
332 If you say yes to this option, support will be included for the
333 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
336 S3/VIA KM266/VT8375 aka ProSavage8
337 S3/VIA KM133/VT8365 aka Savage4
339 This support is also available as a module. If so, the module
340 will be called i2c-prosavage.
343 tristate "Embedded Planet RPX Lite/Classic support"
344 depends on (RPXLITE || RPXCLASSIC) && I2C
348 tristate "S3C2410 I2C Driver"
349 depends on I2C && ARCH_S3C2410
351 Say Y here to include support for I2C controller in the
352 Samsung S3C2410 based System-on-Chip devices.
355 tristate "S3 Savage 4"
356 depends on I2C && PCI && EXPERIMENTAL
359 If you say yes to this option, support will be included for the
360 S3 Savage 4 I2C interface.
362 This driver can also be built as a module. If so, the module
363 will be called i2c-savage4.
366 tristate "SiByte SMBus interface"
367 depends on SIBYTE_SB1xxx_SOC && I2C
369 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
372 tristate "NatSemi SCx200 I2C using GPIO pins"
373 depends on SCx200_GPIO && I2C
376 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
378 If you don't know what to do here, say N.
380 This support is also available as a module. If so, the module
381 will be called scx200_i2c.
383 config SCx200_I2C_SCL
384 int "GPIO pin used for SCL"
385 depends on SCx200_I2C
388 Enter the GPIO pin number used for the SCL signal. This value can
389 also be specified with a module parameter.
391 config SCx200_I2C_SDA
392 int "GPIO pin used for SDA"
393 depends on SCx200_I2C
396 Enter the GPIO pin number used for the SSA signal. This value can
397 also be specified with a module parameter.
400 tristate "Geode ACCESS.bus support"
401 depends on X86_32 && I2C && PCI
403 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
404 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
406 If you don't know what to do here, say N.
408 This support is also available as a module. If so, the module
409 will be called scx200_acb.
413 depends on I2C && PCI
415 If you say yes to this option, support will be included for the
416 SiS5595 SMBus (a subset of I2C) interface.
418 This driver can also be built as a module. If so, the module
419 will be called i2c-sis5595.
422 tristate "SiS 630/730"
423 depends on I2C && PCI
425 If you say yes to this option, support will be included for the
426 SiS630 and SiS730 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-sis630.
433 depends on I2C && PCI
435 If you say yes to this option, support will be included for the SiS
436 96x SMBus (a subset of I2C) interfaces. Specifically, the following
437 chipsets are supported:
446 This driver can also be built as a module. If so, the module
447 will be called i2c-sis96x.
450 tristate "I2C/SMBus Test Stub"
451 depends on I2C && EXPERIMENTAL && 'm'
454 This module may be useful to developers of SMBus client drivers,
455 especially for certain kinds of sensor chips.
457 If you do build this module, be sure to read the notes and warnings
458 in <file:Documentation/i2c/i2c-stub>.
460 If you don't know what to do here, definitely say N.
463 tristate "VIA 82C586B"
464 depends on I2C && PCI && EXPERIMENTAL
467 If you say yes to this option, support will be included for the VIA
468 82C586B I2C interface
470 This driver can also be built as a module. If so, the module
471 will be called i2c-via.
474 tristate "VIA 82C596/82C686/823x"
475 depends on I2C && PCI
477 If you say yes to this option, support will be included for the VIA
478 82C596/82C686/823x I2C interfaces. Specifically, the following
479 chipsets are supported:
488 This driver can also be built as a module. If so, the module
489 will be called i2c-viapro.
493 depends on I2C && PCI
496 If you say yes to this option, support will be included for the
497 Voodoo 3 I2C interface.
499 This driver can also be built as a module. If so, the module
500 will be called i2c-voodoo3.
503 tristate "PCA9564 on an ISA bus"
508 This driver supports ISA boards using the Philips PCA 9564
509 Parallel bus to I2C bus controller
511 This driver can also be built as a module. If so, the module
512 will be called i2c-pca-isa.
514 This device is almost undetectable and using this driver on a
515 system which doesn't have this device will result in long
516 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
517 time). If unsure, say N.
520 tristate "Marvell mv64xxx I2C Controller"
521 depends on I2C && MV64X60 && EXPERIMENTAL
523 If you say yes to this option, support will be included for the
524 built-in I2C interface on the Marvell 64xxx line of host bridges.
526 This driver can also be built as a module. If so, the module
527 will be called i2c-mv64xxx.