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"
44 depends on I2C && EXPERIMENTAL
46 If you say yes to this option, support will be included for the AMD
47 756/766/768 mainboard I2C interfaces.
49 This driver can also be built as a module. If so, the module
50 will be called i2c-amd756.
54 depends on I2C && EXPERIMENTAL
56 If you say yes to this option, support will be included for the AMD
57 8111 mainboard I2C interfaces.
59 This driver can also be built as a module. If so, the module
60 will be called i2c-amd8111.
63 tristate "Elektor ISA card"
64 depends on I2C && ISA && BROKEN_ON_SMP
67 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
70 This support is also available as a module. If so, the module
71 will be called i2c-elektor.
74 tristate "CHRP Apple Hydra Mac I/O I2C interface"
75 depends on I2C && PCI && PPC_CHRP && EXPERIMENTAL
78 This supports the use of the I2C interface in the Apple Hydra Mac
79 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
82 This support is also available as a module. If so, the module
83 will be called i2c-hydra.
87 depends on I2C && PCI && EXPERIMENTAL
89 If you say yes to this option, support will be included for the Intel
90 801 family of mainboard I2C interfaces. Specifically, the following
91 versions of the chipset are supported:
101 This driver can also be built as a module. If so, the module
102 will be called i2c-i801.
105 tristate "Intel 810/815"
106 depends on I2C && PCI && EXPERIMENTAL
109 If you say yes to this option, support will be included for the Intel
110 810/815 family of mainboard I2C interfaces. Specifically, the
111 following versions of the chipset is supported:
117 This driver can also be built as a module. If so, the module
118 will be called i2c-i810.
121 tristate "IBM PPC 4xx on-chip I2C interface"
122 depends on IBM_OCP && I2C
124 Say Y here if you want to use IIC peripheral found on
125 embedded IBM PPC 4xx based systems.
127 This driver can also be built as a module. If so, the module
128 will be called i2c-ibm_iic.
131 tristate "Intel XScale IOP3xx on-chip I2C interface"
132 depends on ARCH_IOP3XX && I2C
135 tristate "ISA Bus support"
136 depends on I2C && EXPERIMENTAL
138 If you say yes to this option, support will be included for i2c
139 interfaces that are on the ISA bus.
141 This driver can also be built as a module. If so, the module
142 will be called i2c-isa.
145 tristate "ITE I2C Adapter"
146 depends on I2C && MIPS_ITE8172
149 This supports the ITE8172 I2C peripheral found on some MIPS
150 systems. Say Y if you have one of these. You should also say Y for
151 the ITE I2C driver algorithm support above.
153 This support is also available as a module. If so, the module
154 will be called i2c-ite.
157 tristate "IXP4xx GPIO-Based I2C Interface"
158 depends on I2C && ARCH_IXP4XX
161 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
162 system and are using GPIO lines for an I2C bus.
164 This support is also available as a module. If so, the module
165 will be called i2c-ixp4xx.
168 tristate "IXP2000 GPIO-Based I2C Interface"
169 depends on I2C && ARCH_IXP2000
172 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
173 system and are using GPIO lines for an I2C bus.
175 This support is also available as a module. If so, the module
176 will be called i2c-ixp2000.
179 tristate "Powermac Keywest I2C interface"
180 depends on I2C && PPC_PMAC
182 This supports the use of the I2C interface in the combo-I/O
183 chip on recent Apple machines. Say Y if you have such a machine.
185 This support is also available as a module. If so, the module
186 will be called i2c-keywest.
189 tristate "MPC107/824x/85xx/52xx"
190 depends on I2C && FSL_OCP
192 If you say yes to this option, support will be included for the
193 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
194 MPC85xx family processors. The driver may also work on 52xx
195 family processors, though interrupts are known not to work.
197 This driver can also be built as a module. If so, the module
198 will be called i2c-mpc.
201 tristate "Nvidia Nforce2"
202 depends on I2C && PCI && EXPERIMENTAL
204 If you say yes to this option, support will be included for the Nvidia
205 Nforce2 family of mainboard I2C interfaces.
207 This driver can also be built as a module. If so, the module
208 will be called i2c-nforce2.
211 tristate "Parallel port adapter"
212 depends on I2C && PARPORT
215 This supports parallel port I2C adapters such as the ones made by
216 Philips or Velleman, Analog Devices evaluation boards, and more.
217 Basically any adapter using the parallel port as an I2C bus with
218 no extra chipset is supported by this driver, or could be.
220 This driver is a replacement for (and was inspired by) an older
221 driver named i2c-philips-par. The new driver supports more devices,
222 and makes it easier to add support for new devices.
224 Another driver exists, named i2c-parport-light, which doesn't depend
225 on the parport driver. This is meant for embedded systems. Don't say
226 Y here if you intend to say Y or M there.
228 This support is also available as a module. If so, the module
229 will be called i2c-parport.
231 config I2C_PARPORT_LIGHT
232 tristate "Parallel port adapter (light)"
236 This supports parallel port I2C adapters such as the ones made by
237 Philips or Velleman, Analog Devices evaluation boards, and more.
238 Basically any adapter using the parallel port as an I2C bus with
239 no extra chipset is supported by this driver, or could be.
241 This driver is a light version of i2c-parport. It doesn't depend
242 on the parport driver, and uses direct I/O access instead. This
243 might be prefered on embedded systems where wasting memory for
244 the clean but heavy parport handling is not an option. The
245 drawback is a reduced portability and the impossibility to
246 dasiy-chain other parallel port devices.
248 Don't say Y here if you said Y or M to i2c-parport. Saying M to
249 both is possible but both modules should not be loaded at the same
252 This support is also available as a module. If so, the module
253 will be called i2c-parport-light.
256 tristate "Intel PIIX4"
257 depends on I2C && PCI && EXPERIMENTAL && !64BIT
259 If you say yes to this option, support will be included for the Intel
260 PIIX4 family of mainboard I2C interfaces. Specifically, the following
261 versions of the chipset are supported:
269 This driver can also be built as a module. If so, the module
270 will be called i2c-piix4.
273 tristate "S3/VIA (Pro)Savage"
274 depends on I2C && PCI && EXPERIMENTAL
277 If you say yes to this option, support will be included for the
278 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
281 S3/VIA KM266/VT8375 aka ProSavage8
282 S3/VIA KM133/VT8365 aka Savage4
284 This support is also available as a module. If so, the module
285 will be called i2c-prosavage.
288 tristate "Embedded Planet RPX Lite/Classic support"
289 depends on (RPXLITE || RPXCLASSIC) && I2C
293 tristate "S3 Savage 4"
294 depends on I2C && PCI && EXPERIMENTAL
297 If you say yes to this option, support will be included for the
298 S3 Savage 4 I2C interface.
300 This driver can also be built as a module. If so, the module
301 will be called i2c-savage4.
304 tristate "NatSemi SCx200 I2C using GPIO pins"
305 depends on SCx200_GPIO && I2C
308 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
310 If you don't know what to do here, say N.
312 This support is also available as a module. If so, the module
313 will be called scx200_i2c.
315 config SCx200_I2C_SCL
316 int "GPIO pin used for SCL"
317 depends on SCx200_I2C
320 Enter the GPIO pin number used for the SCL signal. This value can
321 also be specified with a module parameter.
323 config SCx200_I2C_SDA
324 int "GPIO pin used for SDA"
325 depends on SCx200_I2C
328 Enter the GPIO pin number used for the SSA signal. This value can
329 also be specified with a module parameter.
332 tristate "NatSemi SCx200 ACCESS.bus"
335 Enable the use of the ACCESS.bus controllers of a SCx200 processor.
337 If you don't know what to do here, say N.
339 This support is also available as a module. If so, the module
340 will be called scx200_acb.
344 depends on I2C && PCI && EXPERIMENTAL
346 If you say yes to this option, support will be included for the
347 SiS5595 SMBus (a subset of I2C) interface.
349 This driver can also be built as a module. If so, the module
350 will be called i2c-sis5595.
353 tristate "SiS 630/730"
354 depends on I2C && PCI && EXPERIMENTAL
356 If you say yes to this option, support will be included for the
357 SiS630 and SiS730 SMBus (a subset of I2C) interface.
359 This driver can also be built as a module. If so, the module
360 will be called i2c-sis630.
364 depends on I2C && PCI && EXPERIMENTAL
366 If you say yes to this option, support will be included for the SiS
367 96x SMBus (a subset of I2C) interfaces. Specifically, the following
368 chipsets are supported:
376 This driver can also be built as a module. If so, the module
377 will be called i2c-sis96x.
380 tristate "VIA 82C586B"
381 depends on I2C && PCI && EXPERIMENTAL
385 If you say yes to this option, support will be included for the VIA
386 82C586B I2C interface
388 This driver can also be built as a module. If so, the module
389 will be called i2c-via.
392 tristate "VIA 82C596/82C686/823x"
393 depends on I2C && PCI && EXPERIMENTAL
396 If you say yes to this option, support will be included for the VIA
397 82C596/82C686/823x I2C interfaces. Specifically, the following
398 chipsets are supported:
407 This driver can also be built as a module. If so, the module
408 will be called i2c-viapro.
412 depends on I2C && PCI && EXPERIMENTAL
416 If you say yes to this option, support will be included for the
417 Voodoo 3 I2C interface.
419 This driver can also be built as a module. If so, the module
420 will be called i2c-voodoo3.
423 tristate "PCA9564 on an ISA bus"
427 This driver supports ISA boards using the Philips PCA 9564
428 Parallel bus to I2C bus controller
430 This driver can also be built as a module. If so, the module
431 will be called i2c-pca-isa.