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)
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"
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:
180 This driver can also be built as a module. If so, the module
181 will be called i2c-piix4.
184 tristate "IBM PPC 4xx on-chip I2C interface"
185 depends on IBM_OCP && I2C
187 Say Y here if you want to use IIC peripheral found on
188 embedded IBM PPC 4xx based systems.
190 This driver can also be built as a module. If so, the module
191 will be called i2c-ibm_iic.
194 tristate "Intel IOP3xx and IXP4xx on-chip I2C interface"
195 depends on (ARCH_IOP3XX || ARCH_IXP4XX) && I2C
197 Say Y here if you want to use the IIC bus controller on
198 the Intel IOP3xx I/O Processors or IXP4xx Network Processors.
200 This driver can also be built as a module. If so, the module
201 will be called i2c-iop3xx.
208 tristate "ITE I2C Adapter"
209 depends on I2C && MIPS_ITE8172
212 This supports the ITE8172 I2C peripheral found on some MIPS
213 systems. Say Y if you have one of these. You should also say Y for
214 the ITE I2C driver algorithm support above.
216 This support is also available as a module. If so, the module
217 will be called i2c-ite.
220 tristate "IXP4xx GPIO-Based I2C Interface"
221 depends on I2C && ARCH_IXP4XX
224 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
225 system and are using GPIO lines for an I2C bus.
227 This support is also available as a module. If so, the module
228 will be called i2c-ixp4xx.
231 tristate "IXP2000 GPIO-Based I2C Interface"
232 depends on I2C && ARCH_IXP2000
235 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
236 system and are using GPIO lines for an I2C bus.
238 This support is also available as a module. If so, the module
239 will be called i2c-ixp2000.
242 tristate "Powermac I2C interface"
243 depends on I2C && PPC_PMAC
246 This exposes the various PowerMac i2c interfaces to the linux i2c
247 layer and to userland. It is used by various drivers on the powemac
248 platform, thus should generally be enabled.
250 This support is also available as a module. If so, the module
251 will be called i2c-powermac.
254 tristate "MPC107/824x/85xx/52xx"
255 depends on I2C && PPC32
257 If you say yes to this option, support will be included for the
258 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
259 MPC85xx family processors. The driver may also work on 52xx
260 family processors, though interrupts are known not to work.
262 This driver can also be built as a module. If so, the module
263 will be called i2c-mpc.
266 tristate "Nvidia nForce2, nForce3 and nForce4"
267 depends on I2C && PCI
269 If you say yes to this option, support will be included for the Nvidia
270 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
272 This driver can also be built as a module. If so, the module
273 will be called i2c-nforce2.
276 tristate "Parallel port adapter"
277 depends on I2C && PARPORT
280 This supports parallel port I2C adapters such as the ones made by
281 Philips or Velleman, Analog Devices evaluation boards, and more.
282 Basically any adapter using the parallel port as an I2C bus with
283 no extra chipset is supported by this driver, or could be.
285 This driver is a replacement for (and was inspired by) an older
286 driver named i2c-philips-par. The new driver supports more devices,
287 and makes it easier to add support for new devices.
289 Another driver exists, named i2c-parport-light, which doesn't depend
290 on the parport driver. This is meant for embedded systems. Don't say
291 Y here if you intend to say Y or M there.
293 This support is also available as a module. If so, the module
294 will be called i2c-parport.
296 config I2C_PARPORT_LIGHT
297 tristate "Parallel port adapter (light)"
301 This supports parallel port I2C adapters such as the ones made by
302 Philips or Velleman, Analog Devices evaluation boards, and more.
303 Basically any adapter using the parallel port as an I2C bus with
304 no extra chipset is supported by this driver, or could be.
306 This driver is a light version of i2c-parport. It doesn't depend
307 on the parport driver, and uses direct I/O access instead. This
308 might be prefered on embedded systems where wasting memory for
309 the clean but heavy parport handling is not an option. The
310 drawback is a reduced portability and the impossibility to
311 dasiy-chain other parallel port devices.
313 Don't say Y here if you said Y or M to i2c-parport. Saying M to
314 both is possible but both modules should not be loaded at the same
317 This support is also available as a module. If so, the module
318 will be called i2c-parport-light.
321 tristate "S3/VIA (Pro)Savage"
322 depends on I2C && PCI
325 If you say yes to this option, support will be included for the
326 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
329 S3/VIA KM266/VT8375 aka ProSavage8
330 S3/VIA KM133/VT8365 aka Savage4
332 This support is also available as a module. If so, the module
333 will be called i2c-prosavage.
336 tristate "Embedded Planet RPX Lite/Classic support"
337 depends on (RPXLITE || RPXCLASSIC) && I2C
341 tristate "S3C2410 I2C Driver"
342 depends on I2C && ARCH_S3C2410
344 Say Y here to include support for I2C controller in the
345 Samsung S3C2410 based System-on-Chip devices.
348 tristate "S3 Savage 4"
349 depends on I2C && PCI && EXPERIMENTAL
352 If you say yes to this option, support will be included for the
353 S3 Savage 4 I2C interface.
355 This driver can also be built as a module. If so, the module
356 will be called i2c-savage4.
359 tristate "SiByte SMBus interface"
360 depends on SIBYTE_SB1xxx_SOC && I2C
362 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
365 tristate "NatSemi SCx200 I2C using GPIO pins"
366 depends on SCx200_GPIO && I2C
369 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
371 If you don't know what to do here, say N.
373 This support is also available as a module. If so, the module
374 will be called scx200_i2c.
376 config SCx200_I2C_SCL
377 int "GPIO pin used for SCL"
378 depends on SCx200_I2C
381 Enter the GPIO pin number used for the SCL signal. This value can
382 also be specified with a module parameter.
384 config SCx200_I2C_SDA
385 int "GPIO pin used for SDA"
386 depends on SCx200_I2C
389 Enter the GPIO pin number used for the SSA signal. This value can
390 also be specified with a module parameter.
393 tristate "NatSemi SCx200 ACCESS.bus"
394 depends on I2C && PCI
396 Enable the use of the ACCESS.bus controllers of a SCx200 processor.
398 If you don't know what to do here, say N.
400 This support is also available as a module. If so, the module
401 will be called scx200_acb.
405 depends on I2C && PCI
407 If you say yes to this option, support will be included for the
408 SiS5595 SMBus (a subset of I2C) interface.
410 This driver can also be built as a module. If so, the module
411 will be called i2c-sis5595.
414 tristate "SiS 630/730"
415 depends on I2C && PCI
417 If you say yes to this option, support will be included for the
418 SiS630 and SiS730 SMBus (a subset of I2C) interface.
420 This driver can also be built as a module. If so, the module
421 will be called i2c-sis630.
425 depends on I2C && PCI
427 If you say yes to this option, support will be included for the SiS
428 96x SMBus (a subset of I2C) interfaces. Specifically, the following
429 chipsets are supported:
438 This driver can also be built as a module. If so, the module
439 will be called i2c-sis96x.
442 tristate "I2C/SMBus Test Stub"
443 depends on I2C && EXPERIMENTAL && 'm'
446 This module may be useful to developers of SMBus client drivers,
447 especially for certain kinds of sensor chips.
449 If you do build this module, be sure to read the notes and warnings
450 in <file:Documentation/i2c/i2c-stub>.
452 If you don't know what to do here, definitely say N.
455 tristate "VIA 82C586B"
456 depends on I2C && PCI && EXPERIMENTAL
459 If you say yes to this option, support will be included for the VIA
460 82C586B I2C interface
462 This driver can also be built as a module. If so, the module
463 will be called i2c-via.
466 tristate "VIA 82C596/82C686/82xx"
467 depends on I2C && PCI
469 If you say yes to this option, support will be included for the VIA
470 82C596/82C686/82xx I2C interfaces. Specifically, the following
471 chipsets are supported:
480 This driver can also be built as a module. If so, the module
481 will be called i2c-viapro.
485 depends on I2C && PCI
488 If you say yes to this option, support will be included for the
489 Voodoo 3 I2C interface.
491 This driver can also be built as a module. If so, the module
492 will be called i2c-voodoo3.
495 tristate "PCA9564 on an ISA bus"
499 This driver supports ISA boards using the Philips PCA 9564
500 Parallel bus to I2C bus controller
502 This driver can also be built as a module. If so, the module
503 will be called i2c-pca-isa.
506 tristate "Marvell mv64xxx I2C Controller"
507 depends on I2C && MV64X60 && EXPERIMENTAL
509 If you say yes to this option, support will be included for the
510 built-in I2C interface on the Marvell 64xxx line of host bridges.
512 This driver can also be built as a module. If so, the module
513 will be called i2c-mv64xxx.