2 # Sensor device configuration
5 menu "I2C Hardware Bus support"
10 depends on I2C && PCI && EXPERIMENTAL
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.
34 depends on I2C && PCI && EXPERIMENTAL
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"
44 depends on I2C && PCI && EXPERIMENTAL
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.
69 depends on I2C && PCI && EXPERIMENTAL
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 && EXPERIMENTAL
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)
128 This driver can also be built as a module. If so, the module
129 will be called i2c-i801.
132 tristate "Intel 810/815"
133 depends on I2C && PCI && EXPERIMENTAL
136 If you say yes to this option, support will be included for the Intel
137 810/815 family of mainboard I2C interfaces. Specifically, the
138 following versions of the chipset is supported:
144 This driver can also be built as a module. If so, the module
145 will be called i2c-i810.
148 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
149 depends on I2C && EXPERIMENTAL && ARCH_PXA
151 If you have devices in the PXA I2C bus, say yes to this option.
152 This driver can also be built as a module. If so, the module
153 will be called i2c-pxa.
156 bool "Intel PXA2XX I2C Slave comms support"
159 Support I2C slave mode communications on the PXA I2C bus. This
160 is necessary for systems where the PXA may be a target on the
164 tristate "Intel PIIX4"
165 depends on I2C && PCI
167 If you say yes to this option, support will be included for the Intel
168 PIIX4 family of mainboard I2C interfaces. Specifically, the following
169 versions of the chipset are supported:
177 This driver can also be built as a module. If so, the module
178 will be called i2c-piix4.
181 tristate "IBM PPC 4xx on-chip I2C interface"
182 depends on IBM_OCP && I2C
184 Say Y here if you want to use IIC peripheral found on
185 embedded IBM PPC 4xx based systems.
187 This driver can also be built as a module. If so, the module
188 will be called i2c-ibm_iic.
191 tristate "Intel IOP3xx and IXP4xx on-chip I2C interface"
192 depends on (ARCH_IOP3XX || ARCH_IXP4XX) && I2C
194 Say Y here if you want to use the IIC bus controller on
195 the Intel IOP3xx I/O Processors or IXP4xx Network Processors.
197 This driver can also be built as a module. If so, the module
198 will be called i2c-iop3xx.
201 tristate "ISA Bus support"
202 depends on I2C && EXPERIMENTAL
204 If you say yes to this option, support will be included for i2c
205 interfaces that are on the ISA bus.
207 This driver can also be built as a module. If so, the module
208 will be called i2c-isa.
211 tristate "ITE I2C Adapter"
212 depends on I2C && MIPS_ITE8172
215 This supports the ITE8172 I2C peripheral found on some MIPS
216 systems. Say Y if you have one of these. You should also say Y for
217 the ITE I2C driver algorithm support above.
219 This support is also available as a module. If so, the module
220 will be called i2c-ite.
223 tristate "IXP4xx GPIO-Based I2C Interface"
224 depends on I2C && ARCH_IXP4XX
227 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
228 system and are using GPIO lines for an I2C bus.
230 This support is also available as a module. If so, the module
231 will be called i2c-ixp4xx.
234 tristate "IXP2000 GPIO-Based I2C Interface"
235 depends on I2C && ARCH_IXP2000
238 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
239 system and are using GPIO lines for an I2C bus.
241 This support is also available as a module. If so, the module
242 will be called i2c-ixp2000.
245 tristate "Powermac Keywest I2C interface"
246 depends on I2C && PPC_PMAC
248 This supports the use of the I2C interface in the combo-I/O
249 chip on recent Apple machines. Say Y if you have such a machine.
251 This support is also available as a module. If so, the module
252 will be called i2c-keywest.
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"
268 depends on I2C && PCI && EXPERIMENTAL
270 If you say yes to this option, support will be included for the Nvidia
271 Nforce2 family of mainboard I2C interfaces.
272 This driver also supports the nForce3 Pro 150 MCP.
274 This driver can also be built as a module. If so, the module
275 will be called i2c-nforce2.
278 tristate "Parallel port adapter"
279 depends on I2C && PARPORT
282 This supports parallel port I2C adapters such as the ones made by
283 Philips or Velleman, Analog Devices evaluation boards, and more.
284 Basically any adapter using the parallel port as an I2C bus with
285 no extra chipset is supported by this driver, or could be.
287 This driver is a replacement for (and was inspired by) an older
288 driver named i2c-philips-par. The new driver supports more devices,
289 and makes it easier to add support for new devices.
291 Another driver exists, named i2c-parport-light, which doesn't depend
292 on the parport driver. This is meant for embedded systems. Don't say
293 Y here if you intend to say Y or M there.
295 This support is also available as a module. If so, the module
296 will be called i2c-parport.
298 config I2C_PARPORT_LIGHT
299 tristate "Parallel port adapter (light)"
303 This supports parallel port I2C adapters such as the ones made by
304 Philips or Velleman, Analog Devices evaluation boards, and more.
305 Basically any adapter using the parallel port as an I2C bus with
306 no extra chipset is supported by this driver, or could be.
308 This driver is a light version of i2c-parport. It doesn't depend
309 on the parport driver, and uses direct I/O access instead. This
310 might be prefered on embedded systems where wasting memory for
311 the clean but heavy parport handling is not an option. The
312 drawback is a reduced portability and the impossibility to
313 dasiy-chain other parallel port devices.
315 Don't say Y here if you said Y or M to i2c-parport. Saying M to
316 both is possible but both modules should not be loaded at the same
319 This support is also available as a module. If so, the module
320 will be called i2c-parport-light.
323 tristate "S3/VIA (Pro)Savage"
324 depends on I2C && PCI && EXPERIMENTAL
327 If you say yes to this option, support will be included for the
328 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
331 S3/VIA KM266/VT8375 aka ProSavage8
332 S3/VIA KM133/VT8365 aka Savage4
334 This support is also available as a module. If so, the module
335 will be called i2c-prosavage.
338 tristate "Embedded Planet RPX Lite/Classic support"
339 depends on (RPXLITE || RPXCLASSIC) && I2C
343 tristate "S3C2410 I2C Driver"
344 depends on I2C && ARCH_S3C2410
346 Say Y here to include support for I2C controller in the
347 Samsung S3C2410 based System-on-Chip devices.
350 tristate "S3 Savage 4"
351 depends on I2C && PCI && EXPERIMENTAL
354 If you say yes to this option, support will be included for the
355 S3 Savage 4 I2C interface.
357 This driver can also be built as a module. If so, the module
358 will be called i2c-savage4.
361 tristate "SiByte SMBus interface"
362 depends on SIBYTE_SB1xxx_SOC && I2C
364 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
367 tristate "NatSemi SCx200 I2C using GPIO pins"
368 depends on SCx200_GPIO && I2C
371 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
373 If you don't know what to do here, say N.
375 This support is also available as a module. If so, the module
376 will be called scx200_i2c.
378 config SCx200_I2C_SCL
379 int "GPIO pin used for SCL"
380 depends on SCx200_I2C
383 Enter the GPIO pin number used for the SCL signal. This value can
384 also be specified with a module parameter.
386 config SCx200_I2C_SDA
387 int "GPIO pin used for SDA"
388 depends on SCx200_I2C
391 Enter the GPIO pin number used for the SSA signal. This value can
392 also be specified with a module parameter.
395 tristate "NatSemi SCx200 ACCESS.bus"
396 depends on I2C && PCI
398 Enable the use of the ACCESS.bus controllers of a SCx200 processor.
400 If you don't know what to do here, say N.
402 This support is also available as a module. If so, the module
403 will be called scx200_acb.
407 depends on I2C && PCI && EXPERIMENTAL
409 If you say yes to this option, support will be included for the
410 SiS5595 SMBus (a subset of I2C) interface.
412 This driver can also be built as a module. If so, the module
413 will be called i2c-sis5595.
416 tristate "SiS 630/730"
417 depends on I2C && PCI && EXPERIMENTAL
419 If you say yes to this option, support will be included for the
420 SiS630 and SiS730 SMBus (a subset of I2C) interface.
422 This driver can also be built as a module. If so, the module
423 will be called i2c-sis630.
427 depends on I2C && PCI && EXPERIMENTAL
429 If you say yes to this option, support will be included for the SiS
430 96x SMBus (a subset of I2C) interfaces. Specifically, the following
431 chipsets are supported:
439 This driver can also be built as a module. If so, the module
440 will be called i2c-sis96x.
443 tristate "I2C/SMBus Test Stub"
444 depends on I2C && EXPERIMENTAL && 'm'
447 This module may be useful to developers of SMBus client drivers,
448 especially for certain kinds of sensor chips.
450 If you do build this module, be sure to read the notes and warnings
451 in <file:Documentation/i2c/i2c-stub>.
453 If you don't know what to do here, definitely say N.
456 tristate "VIA 82C586B"
457 depends on I2C && PCI && EXPERIMENTAL
460 If you say yes to this option, support will be included for the VIA
461 82C586B I2C interface
463 This driver can also be built as a module. If so, the module
464 will be called i2c-via.
467 tristate "VIA 82C596/82C686/823x"
468 depends on I2C && PCI && EXPERIMENTAL
470 If you say yes to this option, support will be included for the VIA
471 82C596/82C686/823x I2C interfaces. Specifically, the following
472 chipsets are supported:
481 This driver can also be built as a module. If so, the module
482 will be called i2c-viapro.
486 depends on I2C && PCI && EXPERIMENTAL
489 If you say yes to this option, support will be included for the
490 Voodoo 3 I2C interface.
492 This driver can also be built as a module. If so, the module
493 will be called i2c-voodoo3.
496 tristate "PCA9564 on an ISA bus"
500 This driver supports ISA boards using the Philips PCA 9564
501 Parallel bus to I2C bus controller
503 This driver can also be built as a module. If so, the module
504 will be called i2c-pca-isa.
507 tristate "Marvell mv64xxx I2C Controller"
508 depends on I2C && MV64X60 && EXPERIMENTAL
510 If you say yes to this option, support will be included for the
511 built-in I2C interface on the Marvell 64xxx line of host bridges.
513 This driver can also be built as a module. If so, the module
514 will be called i2c-mv64xxx.