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:
99 This driver can also be built as a module. If so, the module
100 will be called i2c-i801.
103 tristate "Intel 810/815"
104 depends on I2C && PCI && EXPERIMENTAL
107 If you say yes to this option, support will be included for the Intel
108 810/815 family of mainboard I2C interfaces. Specifically, the
109 following versions of the chipset is supported:
115 This driver can also be built as a module. If so, the module
116 will be called i2c-i810.
119 tristate "IBM IIC I2C"
120 depends on IBM_OCP && I2C
123 tristate "Intel XScale IOP3xx on-chip I2C interface"
124 depends on ARCH_IOP3XX && I2C
127 tristate "ISA Bus support"
128 depends on I2C && EXPERIMENTAL
130 If you say yes to this option, support will be included for i2c
131 interfaces that are on the ISA bus.
133 This driver can also be built as a module. If so, the module
134 will be called i2c-isa.
137 tristate "ITE I2C Adapter"
138 depends on I2C && MIPS_ITE8172
141 This supports the ITE8172 I2C peripheral found on some MIPS
142 systems. Say Y if you have one of these. You should also say Y for
143 the ITE I2C driver algorithm support above.
145 This support is also available as a module. If so, the module
146 will be called i2c-ite.
149 tristate "IXP42x GPIO-Based I2C Interface"
150 depends on I2C && ARCH_IXP425
153 Say Y here if you have an Intel IXP42x(420,421,422,425) based
154 system and are using GPIO lines for an I2C bus.
156 This support is also available as a module. If so, the module
157 will be called i2c-ixp42x.
160 tristate "Powermac Keywest I2C interface"
161 depends on I2C && PPC_PMAC
163 This supports the use of the I2C interface in the combo-I/O
164 chip on recent Apple machines. Say Y if you have such a machine.
166 This support is also available as a module. If so, the module
167 will be called i2c-keywest.
170 tristate "Nvidia Nforce2"
171 depends on I2C && PCI && EXPERIMENTAL
173 If you say yes to this option, support will be included for the Nvidia
174 Nforce2 family of mainboard I2C interfaces.
176 This driver can also be built as a module. If so, the module
177 will be called i2c-nforce2.
180 tristate "Parallel port adapter"
181 depends on I2C && PARPORT
184 This supports parallel port I2C adapters such as the ones made by
185 Philips or Velleman, Analog Devices evaluation boards, and more.
186 Basically any adapter using the parallel port as an I2C bus with
187 no extra chipset is supported by this driver, or could be.
189 This driver is a replacement for (and was inspired by) an older
190 driver named i2c-philips-par. The new driver supports more devices,
191 and makes it easier to add support for new devices.
193 Another driver exists, named i2c-parport-light, which doesn't depend
194 on the parport driver. This is meant for embedded systems. Don't say
195 Y here if you intend to say Y or M there.
197 This support is also available as a module. If so, the module
198 will be called i2c-parport.
200 config I2C_PARPORT_LIGHT
201 tristate "Parallel port adapter (light)"
205 This supports parallel port I2C adapters such as the ones made by
206 Philips or Velleman, Analog Devices evaluation boards, and more.
207 Basically any adapter using the parallel port as an I2C bus with
208 no extra chipset is supported by this driver, or could be.
210 This driver is a light version of i2c-parport. It doesn't depend
211 on the parport driver, and uses direct I/O access instead. This
212 might be prefered on embedded systems where wasting memory for
213 the clean but heavy parport handling is not an option. The
214 drawback is a reduced portability and the impossibility to
215 dasiy-chain other parallel port devices.
217 Don't say Y here if you said Y or M to i2c-parport. Saying M to
218 both is possible but both modules should not be loaded at the same
221 This support is also available as a module. If so, the module
222 will be called i2c-parport-light.
225 tristate "Intel PIIX4"
226 depends on I2C && PCI && EXPERIMENTAL && !64BIT
228 If you say yes to this option, support will be included for the Intel
229 PIIX4 family of mainboard I2C interfaces. Specifically, the following
230 versions of the chipset are supported:
238 This driver can also be built as a module. If so, the module
239 will be called i2c-piix4.
242 tristate "S3/VIA (Pro)Savage"
243 depends on I2C && PCI && EXPERIMENTAL
246 If you say yes to this option, support will be included for the
247 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
250 S3/VIA KM266/VT8375 aka ProSavage8
251 S3/VIA KM133/VT8365 aka Savage4
253 This support is also available as a module. If so, the module
254 will be called i2c-prosavage.
257 tristate "Embedded Planet RPX Lite/Classic support"
258 depends on (RPXLITE || RPXCLASSIC) && I2C
262 tristate "S3 Savage 4"
263 depends on I2C && PCI && EXPERIMENTAL
266 If you say yes to this option, support will be included for the
267 S3 Savage 4 I2C interface.
269 This driver can also be built as a module. If so, the module
270 will be called i2c-savage4.
273 tristate "NatSemi SCx200 I2C using GPIO pins"
274 depends on SCx200_GPIO && I2C
277 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
279 If you don't know what to do here, say N.
281 This support is also available as a module. If so, the module
282 will be called scx200_i2c.
284 config SCx200_I2C_SCL
285 int "GPIO pin used for SCL"
286 depends on SCx200_I2C
289 Enter the GPIO pin number used for the SCL signal. This value can
290 also be specified with a module parameter.
292 config SCx200_I2C_SDA
293 int "GPIO pin used for SDA"
294 depends on SCx200_I2C
297 Enter the GPIO pin number used for the SSA signal. This value can
298 also be specified with a module parameter.
301 tristate "NatSemi SCx200 ACCESS.bus"
304 Enable the use of the ACCESS.bus controllers of a SCx200 processor.
306 If you don't know what to do here, say N.
308 This support is also available as a module. If so, the module
309 will be called scx200_acb.
313 depends on I2C && PCI && EXPERIMENTAL
315 If you say yes to this option, support will be included for the
316 SiS5595 SMBus (a subset of I2C) interface.
318 This driver can also be built as a module. If so, the module
319 will be called i2c-sis5595.
322 tristate "SiS 630/730"
323 depends on I2C && PCI && EXPERIMENTAL
325 If you say yes to this option, support will be included for the
326 SiS630 and SiS730 SMBus (a subset of I2C) interface.
328 This driver can also be built as a module. If so, the module
329 will be called i2c-sis630.
333 depends on I2C && PCI && EXPERIMENTAL
335 If you say yes to this option, support will be included for the SiS
336 96x SMBus (a subset of I2C) interfaces. Specifically, the following
337 chipsets are supported:
345 This driver can also be built as a module. If so, the module
346 will be called i2c-sis96x.
349 tristate "VIA 82C586B"
350 depends on I2C && PCI && EXPERIMENTAL
354 If you say yes to this option, support will be included for the VIA
355 82C586B I2C interface
357 This driver can also be built as a module. If so, the module
358 will be called i2c-via.
361 tristate "VIA 82C596/82C686/823x"
362 depends on I2C && PCI && EXPERIMENTAL
365 If you say yes to this option, support will be included for the VIA
366 82C596/82C686/823x I2C interfaces. Specifically, the following
367 chipsets are supported:
376 This driver can also be built as a module. If so, the module
377 will be called i2c-viapro.
381 depends on I2C && PCI && EXPERIMENTAL
385 If you say yes to this option, support will be included for the
386 Voodoo 3 I2C interface.
388 This driver can also be built as a module. If so, the module
389 will be called i2c-voodoo3.