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.
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:
127 This driver can also be built as a module. If so, the module
128 will be called i2c-i801.
131 tristate "Intel 810/815"
132 depends on I2C && PCI && EXPERIMENTAL
135 If you say yes to this option, support will be included for the Intel
136 810/815 family of mainboard I2C interfaces. Specifically, the
137 following versions of the chipset is supported:
143 This driver can also be built as a module. If so, the module
144 will be called i2c-i810.
147 tristate "IBM PPC 4xx on-chip I2C interface"
148 depends on IBM_OCP && I2C
150 Say Y here if you want to use IIC peripheral found on
151 embedded IBM PPC 4xx based systems.
153 This driver can also be built as a module. If so, the module
154 will be called i2c-ibm_iic.
157 tristate "Intel IOP3xx and IXP4xx on-chip I2C interface"
158 depends on (ARCH_IOP3XX || ARCH_IXP4XX) && I2C
160 Say Y here if you want to use the IIC bus controller on
161 the Intel IOP3xx I/O Processors or IXP4xx Network Processors.
163 This driver can also be built as a module. If so, the module
164 will be called i2c-iop3xx.
167 tristate "ISA Bus support"
168 depends on I2C && EXPERIMENTAL
170 If you say yes to this option, support will be included for i2c
171 interfaces that are on the ISA bus.
173 This driver can also be built as a module. If so, the module
174 will be called i2c-isa.
177 tristate "ITE I2C Adapter"
178 depends on I2C && MIPS_ITE8172
181 This supports the ITE8172 I2C peripheral found on some MIPS
182 systems. Say Y if you have one of these. You should also say Y for
183 the ITE I2C driver algorithm support above.
185 This support is also available as a module. If so, the module
186 will be called i2c-ite.
189 tristate "IXP4xx GPIO-Based I2C Interface"
190 depends on I2C && ARCH_IXP4XX
193 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
194 system and are using GPIO lines for an I2C bus.
196 This support is also available as a module. If so, the module
197 will be called i2c-ixp4xx.
200 tristate "IXP2000 GPIO-Based I2C Interface"
201 depends on I2C && ARCH_IXP2000
204 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
205 system and are using GPIO lines for an I2C bus.
207 This support is also available as a module. If so, the module
208 will be called i2c-ixp2000.
211 tristate "Powermac Keywest I2C interface"
212 depends on I2C && PPC_PMAC
214 This supports the use of the I2C interface in the combo-I/O
215 chip on recent Apple machines. Say Y if you have such a machine.
217 This support is also available as a module. If so, the module
218 will be called i2c-keywest.
221 tristate "MPC107/824x/85xx/52xx"
222 depends on I2C && PPC
224 If you say yes to this option, support will be included for the
225 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
226 MPC85xx family processors. The driver may also work on 52xx
227 family processors, though interrupts are known not to work.
229 This driver can also be built as a module. If so, the module
230 will be called i2c-mpc.
233 tristate "Nvidia Nforce2"
234 depends on I2C && PCI && EXPERIMENTAL
236 If you say yes to this option, support will be included for the Nvidia
237 Nforce2 family of mainboard I2C interfaces.
238 This driver also supports the nForce3 Pro 150 MCP.
240 This driver can also be built as a module. If so, the module
241 will be called i2c-nforce2.
244 tristate "Parallel port adapter"
245 depends on I2C && PARPORT
248 This supports parallel port I2C adapters such as the ones made by
249 Philips or Velleman, Analog Devices evaluation boards, and more.
250 Basically any adapter using the parallel port as an I2C bus with
251 no extra chipset is supported by this driver, or could be.
253 This driver is a replacement for (and was inspired by) an older
254 driver named i2c-philips-par. The new driver supports more devices,
255 and makes it easier to add support for new devices.
257 Another driver exists, named i2c-parport-light, which doesn't depend
258 on the parport driver. This is meant for embedded systems. Don't say
259 Y here if you intend to say Y or M there.
261 This support is also available as a module. If so, the module
262 will be called i2c-parport.
264 config I2C_PARPORT_LIGHT
265 tristate "Parallel port adapter (light)"
269 This supports parallel port I2C adapters such as the ones made by
270 Philips or Velleman, Analog Devices evaluation boards, and more.
271 Basically any adapter using the parallel port as an I2C bus with
272 no extra chipset is supported by this driver, or could be.
274 This driver is a light version of i2c-parport. It doesn't depend
275 on the parport driver, and uses direct I/O access instead. This
276 might be prefered on embedded systems where wasting memory for
277 the clean but heavy parport handling is not an option. The
278 drawback is a reduced portability and the impossibility to
279 dasiy-chain other parallel port devices.
281 Don't say Y here if you said Y or M to i2c-parport. Saying M to
282 both is possible but both modules should not be loaded at the same
285 This support is also available as a module. If so, the module
286 will be called i2c-parport-light.
289 tristate "Intel PIIX4"
290 depends on I2C && PCI && EXPERIMENTAL && !64BIT
292 If you say yes to this option, support will be included for the Intel
293 PIIX4 family of mainboard I2C interfaces. Specifically, the following
294 versions of the chipset are supported:
302 This driver can also be built as a module. If so, the module
303 will be called i2c-piix4.
306 tristate "S3/VIA (Pro)Savage"
307 depends on I2C && PCI && EXPERIMENTAL
310 If you say yes to this option, support will be included for the
311 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
314 S3/VIA KM266/VT8375 aka ProSavage8
315 S3/VIA KM133/VT8365 aka Savage4
317 This support is also available as a module. If so, the module
318 will be called i2c-prosavage.
321 tristate "Embedded Planet RPX Lite/Classic support"
322 depends on (RPXLITE || RPXCLASSIC) && I2C
326 tristate "S3C2410 I2C Driver"
327 depends on I2C && ARCH_S3C2410
329 Say Y here to include support for I2C controller in the
330 Samsung S3C2410 based System-on-Chip devices.
333 tristate "S3 Savage 4"
334 depends on I2C && PCI && EXPERIMENTAL
337 If you say yes to this option, support will be included for the
338 S3 Savage 4 I2C interface.
340 This driver can also be built as a module. If so, the module
341 will be called i2c-savage4.
344 tristate "SiByte SMBus interface"
345 depends on SIBYTE_SB1xxx_SOC && I2C
347 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
350 tristate "NatSemi SCx200 I2C using GPIO pins"
351 depends on SCx200_GPIO && I2C
354 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
356 If you don't know what to do here, say N.
358 This support is also available as a module. If so, the module
359 will be called scx200_i2c.
361 config SCx200_I2C_SCL
362 int "GPIO pin used for SCL"
363 depends on SCx200_I2C
366 Enter the GPIO pin number used for the SCL signal. This value can
367 also be specified with a module parameter.
369 config SCx200_I2C_SDA
370 int "GPIO pin used for SDA"
371 depends on SCx200_I2C
374 Enter the GPIO pin number used for the SSA signal. This value can
375 also be specified with a module parameter.
378 tristate "NatSemi SCx200 ACCESS.bus"
379 depends on I2C && PCI
381 Enable the use of the ACCESS.bus controllers of a SCx200 processor.
383 If you don't know what to do here, say N.
385 This support is also available as a module. If so, the module
386 will be called scx200_acb.
390 depends on I2C && PCI && EXPERIMENTAL
392 If you say yes to this option, support will be included for the
393 SiS5595 SMBus (a subset of I2C) interface.
395 This driver can also be built as a module. If so, the module
396 will be called i2c-sis5595.
399 tristate "SiS 630/730"
400 depends on I2C && PCI && EXPERIMENTAL
402 If you say yes to this option, support will be included for the
403 SiS630 and SiS730 SMBus (a subset of I2C) interface.
405 This driver can also be built as a module. If so, the module
406 will be called i2c-sis630.
410 depends on I2C && PCI && EXPERIMENTAL
412 If you say yes to this option, support will be included for the SiS
413 96x SMBus (a subset of I2C) interfaces. Specifically, the following
414 chipsets are supported:
422 This driver can also be built as a module. If so, the module
423 will be called i2c-sis96x.
426 tristate "I2C/SMBus Test Stub"
427 depends on I2C && EXPERIMENTAL && 'm'
430 This module may be useful to developers of SMBus client drivers,
431 especially for certain kinds of sensor chips.
433 If you do build this module, be sure to read the notes and warnings
434 in <file:Documentation/i2c/i2c-stub>.
436 If you don't know what to do here, definitely say N.
439 tristate "VIA 82C586B"
440 depends on I2C && PCI && EXPERIMENTAL
443 If you say yes to this option, support will be included for the VIA
444 82C586B I2C interface
446 This driver can also be built as a module. If so, the module
447 will be called i2c-via.
450 tristate "VIA 82C596/82C686/823x"
451 depends on I2C && PCI && EXPERIMENTAL
453 If you say yes to this option, support will be included for the VIA
454 82C596/82C686/823x I2C interfaces. Specifically, the following
455 chipsets are supported:
464 This driver can also be built as a module. If so, the module
465 will be called i2c-viapro.
469 depends on I2C && PCI && EXPERIMENTAL
472 If you say yes to this option, support will be included for the
473 Voodoo 3 I2C interface.
475 This driver can also be built as a module. If so, the module
476 will be called i2c-voodoo3.
479 tristate "PCA9564 on an ISA bus"
483 This driver supports ISA boards using the Philips PCA 9564
484 Parallel bus to I2C bus controller
486 This driver can also be built as a module. If so, the module
487 will be called i2c-pca-isa.