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"
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
181 This driver can also be built as a module. If so, the module
182 will be called i2c-piix4.
185 tristate "IBM PPC 4xx on-chip I2C interface"
186 depends on IBM_OCP && I2C
188 Say Y here if you want to use IIC peripheral found on
189 embedded IBM PPC 4xx based systems.
191 This driver can also be built as a module. If so, the module
192 will be called i2c-ibm_iic.
195 tristate "Intel IOP3xx and IXP4xx on-chip I2C interface"
196 depends on (ARCH_IOP3XX || ARCH_IXP4XX) && I2C
198 Say Y here if you want to use the IIC bus controller on
199 the Intel IOP3xx I/O Processors or IXP4xx Network Processors.
201 This driver can also be built as a module. If so, the module
202 will be called i2c-iop3xx.
209 tristate "ITE I2C Adapter"
210 depends on I2C && MIPS_ITE8172
213 This supports the ITE8172 I2C peripheral found on some MIPS
214 systems. Say Y if you have one of these. You should also say Y for
215 the ITE I2C driver algorithm support above.
217 This support is also available as a module. If so, the module
218 will be called i2c-ite.
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"
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 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 "Parallel port adapter"
278 depends on I2C && PARPORT
281 This supports parallel port I2C adapters such as the ones made by
282 Philips or Velleman, Analog Devices evaluation boards, and more.
283 Basically any adapter using the parallel port as an I2C bus with
284 no extra chipset is supported by this driver, or could be.
286 This driver is a replacement for (and was inspired by) an older
287 driver named i2c-philips-par. The new driver supports more devices,
288 and makes it easier to add support for new devices.
290 An adapter type parameter is now mandatory. Please read the file
291 Documentation/i2c/busses/i2c-parport for details.
293 Another driver exists, named i2c-parport-light, which doesn't depend
294 on the parport driver. This is meant for embedded systems. Don't say
295 Y here if you intend to say Y or M there.
297 This support is also available as a module. If so, the module
298 will be called i2c-parport.
300 config I2C_PARPORT_LIGHT
301 tristate "Parallel port adapter (light)"
305 This supports parallel port I2C adapters such as the ones made by
306 Philips or Velleman, Analog Devices evaluation boards, and more.
307 Basically any adapter using the parallel port as an I2C bus with
308 no extra chipset is supported by this driver, or could be.
310 This driver is a light version of i2c-parport. It doesn't depend
311 on the parport driver, and uses direct I/O access instead. This
312 might be prefered on embedded systems where wasting memory for
313 the clean but heavy parport handling is not an option. The
314 drawback is a reduced portability and the impossibility to
315 dasiy-chain other parallel port devices.
317 Don't say Y here if you said Y or M to i2c-parport. Saying M to
318 both is possible but both modules should not be loaded at the same
321 This support is also available as a module. If so, the module
322 will be called i2c-parport-light.
325 tristate "S3/VIA (Pro)Savage"
326 depends on I2C && PCI
329 If you say yes to this option, support will be included for the
330 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
333 S3/VIA KM266/VT8375 aka ProSavage8
334 S3/VIA KM133/VT8365 aka Savage4
336 This support is also available as a module. If so, the module
337 will be called i2c-prosavage.
340 tristate "Embedded Planet RPX Lite/Classic support"
341 depends on (RPXLITE || RPXCLASSIC) && I2C
345 tristate "S3C2410 I2C Driver"
346 depends on I2C && ARCH_S3C2410
348 Say Y here to include support for I2C controller in the
349 Samsung S3C2410 based System-on-Chip devices.
352 tristate "S3 Savage 4"
353 depends on I2C && PCI && EXPERIMENTAL
356 If you say yes to this option, support will be included for the
357 S3 Savage 4 I2C interface.
359 This driver can also be built as a module. If so, the module
360 will be called i2c-savage4.
363 tristate "SiByte SMBus interface"
364 depends on SIBYTE_SB1xxx_SOC && I2C
366 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
369 tristate "NatSemi SCx200 I2C using GPIO pins"
370 depends on SCx200_GPIO && I2C
373 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
375 If you don't know what to do here, say N.
377 This support is also available as a module. If so, the module
378 will be called scx200_i2c.
380 config SCx200_I2C_SCL
381 int "GPIO pin used for SCL"
382 depends on SCx200_I2C
385 Enter the GPIO pin number used for the SCL signal. This value can
386 also be specified with a module parameter.
388 config SCx200_I2C_SDA
389 int "GPIO pin used for SDA"
390 depends on SCx200_I2C
393 Enter the GPIO pin number used for the SSA signal. This value can
394 also be specified with a module parameter.
397 tristate "Geode ACCESS.bus support"
398 depends on X86_32 && I2C && PCI
400 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
401 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
403 If you don't know what to do here, say N.
405 This support is also available as a module. If so, the module
406 will be called scx200_acb.
410 depends on I2C && PCI
412 If you say yes to this option, support will be included for the
413 SiS5595 SMBus (a subset of I2C) interface.
415 This driver can also be built as a module. If so, the module
416 will be called i2c-sis5595.
419 tristate "SiS 630/730"
420 depends on I2C && PCI
422 If you say yes to this option, support will be included for the
423 SiS630 and SiS730 SMBus (a subset of I2C) interface.
425 This driver can also be built as a module. If so, the module
426 will be called i2c-sis630.
430 depends on I2C && PCI
432 If you say yes to this option, support will be included for the SiS
433 96x SMBus (a subset of I2C) interfaces. Specifically, the following
434 chipsets are supported:
443 This driver can also be built as a module. If so, the module
444 will be called i2c-sis96x.
447 tristate "I2C/SMBus Test Stub"
448 depends on I2C && EXPERIMENTAL && 'm'
451 This module may be useful to developers of SMBus client drivers,
452 especially for certain kinds of sensor chips.
454 If you do build this module, be sure to read the notes and warnings
455 in <file:Documentation/i2c/i2c-stub>.
457 If you don't know what to do here, definitely say N.
460 tristate "VIA 82C586B"
461 depends on I2C && PCI && EXPERIMENTAL
464 If you say yes to this option, support will be included for the VIA
465 82C586B I2C interface
467 This driver can also be built as a module. If so, the module
468 will be called i2c-via.
471 tristate "VIA 82C596/82C686/823x"
472 depends on I2C && PCI
474 If you say yes to this option, support will be included for the VIA
475 82C596/82C686/823x I2C interfaces. Specifically, the following
476 chipsets are supported:
485 This driver can also be built as a module. If so, the module
486 will be called i2c-viapro.
490 depends on I2C && PCI
493 If you say yes to this option, support will be included for the
494 Voodoo 3 I2C interface.
496 This driver can also be built as a module. If so, the module
497 will be called i2c-voodoo3.
500 tristate "PCA9564 on an ISA bus"
504 This driver supports ISA boards using the Philips PCA 9564
505 Parallel bus to I2C bus controller
507 This driver can also be built as a module. If so, the module
508 will be called i2c-pca-isa.
511 tristate "Marvell mv64xxx I2C Controller"
512 depends on I2C && MV64X60 && EXPERIMENTAL
514 If you say yes to this option, support will be included for the
515 built-in I2C interface on the Marvell 64xxx line of host bridges.
517 This driver can also be built as a module. If so, the module
518 will be called i2c-mv64xxx.