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 "Elektor ISA card"
79 depends on I2C && ISA && BROKEN_ON_SMP
82 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
85 This support is also available as a module. If so, the module
86 will be called i2c-elektor.
89 tristate "CHRP Apple Hydra Mac I/O I2C interface"
90 depends on I2C && PCI && PPC_CHRP && EXPERIMENTAL
93 This supports the use of the I2C interface in the Apple Hydra Mac
94 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
97 This support is also available as a module. If so, the module
98 will be called i2c-hydra.
102 depends on I2C && PCI && EXPERIMENTAL
104 If you say yes to this option, support will be included for the Intel
105 801 family of mainboard I2C interfaces. Specifically, the following
106 versions of the chipset are supported:
117 This driver can also be built as a module. If so, the module
118 will be called i2c-i801.
121 tristate "Intel 810/815"
122 depends on I2C && PCI && EXPERIMENTAL
125 If you say yes to this option, support will be included for the Intel
126 810/815 family of mainboard I2C interfaces. Specifically, the
127 following versions of the chipset is supported:
133 This driver can also be built as a module. If so, the module
134 will be called i2c-i810.
137 tristate "IBM PPC 4xx on-chip I2C interface"
138 depends on IBM_OCP && I2C
140 Say Y here if you want to use IIC peripheral found on
141 embedded IBM PPC 4xx based systems.
143 This driver can also be built as a module. If so, the module
144 will be called i2c-ibm_iic.
147 tristate "Intel XScale IOP3xx on-chip I2C interface"
148 depends on ARCH_IOP3XX && I2C
151 tristate "ISA Bus support"
152 depends on I2C && EXPERIMENTAL
154 If you say yes to this option, support will be included for i2c
155 interfaces that are on the ISA bus.
157 This driver can also be built as a module. If so, the module
158 will be called i2c-isa.
161 tristate "ITE I2C Adapter"
162 depends on I2C && MIPS_ITE8172
165 This supports the ITE8172 I2C peripheral found on some MIPS
166 systems. Say Y if you have one of these. You should also say Y for
167 the ITE I2C driver algorithm support above.
169 This support is also available as a module. If so, the module
170 will be called i2c-ite.
173 tristate "IXP4xx GPIO-Based I2C Interface"
174 depends on I2C && ARCH_IXP4XX
177 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
178 system and are using GPIO lines for an I2C bus.
180 This support is also available as a module. If so, the module
181 will be called i2c-ixp4xx.
184 tristate "IXP2000 GPIO-Based I2C Interface"
185 depends on I2C && ARCH_IXP2000
188 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
189 system and are using GPIO lines for an I2C bus.
191 This support is also available as a module. If so, the module
192 will be called i2c-ixp2000.
195 tristate "Powermac Keywest I2C interface"
196 depends on I2C && PPC_PMAC
198 This supports the use of the I2C interface in the combo-I/O
199 chip on recent Apple machines. Say Y if you have such a machine.
201 This support is also available as a module. If so, the module
202 will be called i2c-keywest.
205 tristate "MPC107/824x/85xx/52xx"
206 depends on I2C && FSL_OCP
208 If you say yes to this option, support will be included for the
209 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
210 MPC85xx family processors. The driver may also work on 52xx
211 family processors, though interrupts are known not to work.
213 This driver can also be built as a module. If so, the module
214 will be called i2c-mpc.
217 tristate "Nvidia Nforce2"
218 depends on I2C && PCI && EXPERIMENTAL
220 If you say yes to this option, support will be included for the Nvidia
221 Nforce2 family of mainboard I2C interfaces.
222 This driver also supports the nForce3 Pro 150 MCP.
224 This driver can also be built as a module. If so, the module
225 will be called i2c-nforce2.
228 tristate "Parallel port adapter"
229 depends on I2C && PARPORT
232 This supports parallel port I2C adapters such as the ones made by
233 Philips or Velleman, Analog Devices evaluation boards, and more.
234 Basically any adapter using the parallel port as an I2C bus with
235 no extra chipset is supported by this driver, or could be.
237 This driver is a replacement for (and was inspired by) an older
238 driver named i2c-philips-par. The new driver supports more devices,
239 and makes it easier to add support for new devices.
241 Another driver exists, named i2c-parport-light, which doesn't depend
242 on the parport driver. This is meant for embedded systems. Don't say
243 Y here if you intend to say Y or M there.
245 This support is also available as a module. If so, the module
246 will be called i2c-parport.
248 config I2C_PARPORT_LIGHT
249 tristate "Parallel port adapter (light)"
253 This supports parallel port I2C adapters such as the ones made by
254 Philips or Velleman, Analog Devices evaluation boards, and more.
255 Basically any adapter using the parallel port as an I2C bus with
256 no extra chipset is supported by this driver, or could be.
258 This driver is a light version of i2c-parport. It doesn't depend
259 on the parport driver, and uses direct I/O access instead. This
260 might be prefered on embedded systems where wasting memory for
261 the clean but heavy parport handling is not an option. The
262 drawback is a reduced portability and the impossibility to
263 dasiy-chain other parallel port devices.
265 Don't say Y here if you said Y or M to i2c-parport. Saying M to
266 both is possible but both modules should not be loaded at the same
269 This support is also available as a module. If so, the module
270 will be called i2c-parport-light.
273 tristate "Intel PIIX4"
274 depends on I2C && PCI && EXPERIMENTAL && !64BIT
276 If you say yes to this option, support will be included for the Intel
277 PIIX4 family of mainboard I2C interfaces. Specifically, the following
278 versions of the chipset are supported:
286 This driver can also be built as a module. If so, the module
287 will be called i2c-piix4.
290 tristate "S3/VIA (Pro)Savage"
291 depends on I2C && PCI && EXPERIMENTAL
294 If you say yes to this option, support will be included for the
295 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
298 S3/VIA KM266/VT8375 aka ProSavage8
299 S3/VIA KM133/VT8365 aka Savage4
301 This support is also available as a module. If so, the module
302 will be called i2c-prosavage.
305 tristate "Embedded Planet RPX Lite/Classic support"
306 depends on (RPXLITE || RPXCLASSIC) && I2C
310 tristate "S3C2410 I2C Driver"
311 depends on I2C && ARCH_S3C2410
313 Say Y here to include support for I2C controller in the
314 Samsung S3C2410 based System-on-Chip devices.
317 tristate "S3 Savage 4"
318 depends on I2C && PCI && EXPERIMENTAL
321 If you say yes to this option, support will be included for the
322 S3 Savage 4 I2C interface.
324 This driver can also be built as a module. If so, the module
325 will be called i2c-savage4.
328 tristate "NatSemi SCx200 I2C using GPIO pins"
329 depends on SCx200_GPIO && I2C
332 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
334 If you don't know what to do here, say N.
336 This support is also available as a module. If so, the module
337 will be called scx200_i2c.
339 config SCx200_I2C_SCL
340 int "GPIO pin used for SCL"
341 depends on SCx200_I2C
344 Enter the GPIO pin number used for the SCL signal. This value can
345 also be specified with a module parameter.
347 config SCx200_I2C_SDA
348 int "GPIO pin used for SDA"
349 depends on SCx200_I2C
352 Enter the GPIO pin number used for the SSA signal. This value can
353 also be specified with a module parameter.
356 tristate "NatSemi SCx200 ACCESS.bus"
357 depends on I2C && PCI
359 Enable the use of the ACCESS.bus controllers of a SCx200 processor.
361 If you don't know what to do here, say N.
363 This support is also available as a module. If so, the module
364 will be called scx200_acb.
368 depends on I2C && PCI && EXPERIMENTAL
370 If you say yes to this option, support will be included for the
371 SiS5595 SMBus (a subset of I2C) interface.
373 This driver can also be built as a module. If so, the module
374 will be called i2c-sis5595.
377 tristate "SiS 630/730"
378 depends on I2C && PCI && EXPERIMENTAL
380 If you say yes to this option, support will be included for the
381 SiS630 and SiS730 SMBus (a subset of I2C) interface.
383 This driver can also be built as a module. If so, the module
384 will be called i2c-sis630.
388 depends on I2C && PCI && EXPERIMENTAL
390 If you say yes to this option, support will be included for the SiS
391 96x SMBus (a subset of I2C) interfaces. Specifically, the following
392 chipsets are supported:
400 This driver can also be built as a module. If so, the module
401 will be called i2c-sis96x.
404 tristate "I2C/SMBus Test Stub"
405 depends on I2C && EXPERIMENTAL && 'm'
408 This module may be useful to developers of SMBus client drivers,
409 especially for certain kinds of sensor chips.
411 If you do build this module, be sure to read the notes and warnings
412 in Documentation/i2c/i2c-stub.
414 If you don't know what to do here, definitely say N.
417 tristate "VIA 82C586B"
418 depends on I2C && PCI && EXPERIMENTAL
422 If you say yes to this option, support will be included for the VIA
423 82C586B I2C interface
425 This driver can also be built as a module. If so, the module
426 will be called i2c-via.
429 tristate "VIA 82C596/82C686/823x"
430 depends on I2C && PCI && EXPERIMENTAL
433 If you say yes to this option, support will be included for the VIA
434 82C596/82C686/823x I2C interfaces. Specifically, the following
435 chipsets are supported:
444 This driver can also be built as a module. If so, the module
445 will be called i2c-viapro.
449 depends on I2C && PCI && EXPERIMENTAL
453 If you say yes to this option, support will be included for the
454 Voodoo 3 I2C interface.
456 This driver can also be built as a module. If so, the module
457 will be called i2c-voodoo3.
460 tristate "PCA9564 on an ISA bus"
464 This driver supports ISA boards using the Philips PCA 9564
465 Parallel bus to I2C bus controller
467 This driver can also be built as a module. If so, the module
468 will be called i2c-pca-isa.