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 "Powermac Keywest I2C interface"
169 depends on I2C && PPC_PMAC
171 This supports the use of the I2C interface in the combo-I/O
172 chip on recent Apple machines. Say Y if you have such a machine.
174 This support is also available as a module. If so, the module
175 will be called i2c-keywest.
178 tristate "Nvidia Nforce2"
179 depends on I2C && PCI && EXPERIMENTAL
181 If you say yes to this option, support will be included for the Nvidia
182 Nforce2 family of mainboard I2C interfaces.
184 This driver can also be built as a module. If so, the module
185 will be called i2c-nforce2.
188 tristate "Parallel port adapter"
189 depends on I2C && PARPORT
192 This supports parallel port I2C adapters such as the ones made by
193 Philips or Velleman, Analog Devices evaluation boards, and more.
194 Basically any adapter using the parallel port as an I2C bus with
195 no extra chipset is supported by this driver, or could be.
197 This driver is a replacement for (and was inspired by) an older
198 driver named i2c-philips-par. The new driver supports more devices,
199 and makes it easier to add support for new devices.
201 Another driver exists, named i2c-parport-light, which doesn't depend
202 on the parport driver. This is meant for embedded systems. Don't say
203 Y here if you intend to say Y or M there.
205 This support is also available as a module. If so, the module
206 will be called i2c-parport.
208 config I2C_PARPORT_LIGHT
209 tristate "Parallel port adapter (light)"
213 This supports parallel port I2C adapters such as the ones made by
214 Philips or Velleman, Analog Devices evaluation boards, and more.
215 Basically any adapter using the parallel port as an I2C bus with
216 no extra chipset is supported by this driver, or could be.
218 This driver is a light version of i2c-parport. It doesn't depend
219 on the parport driver, and uses direct I/O access instead. This
220 might be prefered on embedded systems where wasting memory for
221 the clean but heavy parport handling is not an option. The
222 drawback is a reduced portability and the impossibility to
223 dasiy-chain other parallel port devices.
225 Don't say Y here if you said Y or M to i2c-parport. Saying M to
226 both is possible but both modules should not be loaded at the same
229 This support is also available as a module. If so, the module
230 will be called i2c-parport-light.
233 tristate "Intel PIIX4"
234 depends on I2C && PCI && EXPERIMENTAL && !64BIT
236 If you say yes to this option, support will be included for the Intel
237 PIIX4 family of mainboard I2C interfaces. Specifically, the following
238 versions of the chipset are supported:
246 This driver can also be built as a module. If so, the module
247 will be called i2c-piix4.
250 tristate "S3/VIA (Pro)Savage"
251 depends on I2C && PCI && EXPERIMENTAL
254 If you say yes to this option, support will be included for the
255 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
258 S3/VIA KM266/VT8375 aka ProSavage8
259 S3/VIA KM133/VT8365 aka Savage4
261 This support is also available as a module. If so, the module
262 will be called i2c-prosavage.
265 tristate "Embedded Planet RPX Lite/Classic support"
266 depends on (RPXLITE || RPXCLASSIC) && I2C
270 tristate "S3 Savage 4"
271 depends on I2C && PCI && EXPERIMENTAL
274 If you say yes to this option, support will be included for the
275 S3 Savage 4 I2C interface.
277 This driver can also be built as a module. If so, the module
278 will be called i2c-savage4.
281 tristate "NatSemi SCx200 I2C using GPIO pins"
282 depends on SCx200_GPIO && I2C
285 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
287 If you don't know what to do here, say N.
289 This support is also available as a module. If so, the module
290 will be called scx200_i2c.
292 config SCx200_I2C_SCL
293 int "GPIO pin used for SCL"
294 depends on SCx200_I2C
297 Enter the GPIO pin number used for the SCL signal. This value can
298 also be specified with a module parameter.
300 config SCx200_I2C_SDA
301 int "GPIO pin used for SDA"
302 depends on SCx200_I2C
305 Enter the GPIO pin number used for the SSA signal. This value can
306 also be specified with a module parameter.
309 tristate "NatSemi SCx200 ACCESS.bus"
312 Enable the use of the ACCESS.bus controllers of a SCx200 processor.
314 If you don't know what to do here, say N.
316 This support is also available as a module. If so, the module
317 will be called scx200_acb.
321 depends on I2C && PCI && EXPERIMENTAL
323 If you say yes to this option, support will be included for the
324 SiS5595 SMBus (a subset of I2C) interface.
326 This driver can also be built as a module. If so, the module
327 will be called i2c-sis5595.
330 tristate "SiS 630/730"
331 depends on I2C && PCI && EXPERIMENTAL
333 If you say yes to this option, support will be included for the
334 SiS630 and SiS730 SMBus (a subset of I2C) interface.
336 This driver can also be built as a module. If so, the module
337 will be called i2c-sis630.
341 depends on I2C && PCI && EXPERIMENTAL
343 If you say yes to this option, support will be included for the SiS
344 96x SMBus (a subset of I2C) interfaces. Specifically, the following
345 chipsets are supported:
353 This driver can also be built as a module. If so, the module
354 will be called i2c-sis96x.
357 tristate "VIA 82C586B"
358 depends on I2C && PCI && EXPERIMENTAL
362 If you say yes to this option, support will be included for the VIA
363 82C586B I2C interface
365 This driver can also be built as a module. If so, the module
366 will be called i2c-via.
369 tristate "VIA 82C596/82C686/823x"
370 depends on I2C && PCI && EXPERIMENTAL
373 If you say yes to this option, support will be included for the VIA
374 82C596/82C686/823x I2C interfaces. Specifically, the following
375 chipsets are supported:
384 This driver can also be built as a module. If so, the module
385 will be called i2c-viapro.
389 depends on I2C && PCI && EXPERIMENTAL
393 If you say yes to this option, support will be included for the
394 Voodoo 3 I2C interface.
396 This driver can also be built as a module. If so, the module
397 will be called i2c-voodoo3.