blob: a0018de3bef499f5485049c53ebe3196b786299c [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Sensor device configuration
3#
4
5menu "I2C Hardware Bus support"
6 depends on I2C
7
8config I2C_ALI1535
9 tristate "ALI 1535"
10 depends on I2C && PCI && EXPERIMENTAL
11 help
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).
16
17 This driver can also be built as a module. If so, the module
18 will be called i2c-ali1535.
19
20config I2C_ALI1563
21 tristate "ALI 1563"
22 depends on I2C && PCI && EXPERIMENTAL
23 help
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).
28
29 This driver can also be built as a module. If so, the module
30 will be called i2c-ali1563.
31
32config I2C_ALI15X3
33 tristate "ALI 15x3"
34 depends on I2C && PCI && EXPERIMENTAL
35 help
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.
38
39 This driver can also be built as a module. If so, the module
40 will be called i2c-ali15x3.
41
42config I2C_AMD756
43 tristate "AMD 756/766/768/8111 and nVidia nForce"
44 depends on I2C && PCI && EXPERIMENTAL
45 help
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.
50
51 This driver can also be built as a module. If so, the module
52 will be called i2c-amd756.
53
54config I2C_AMD756_S4882
55 tristate "SMBus multiplexing on the Tyan S4882"
56 depends on I2C_AMD756 && EXPERIMENTAL
57 help
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.
63
64 This driver can also be built as a module. If so, the module
65 will be called i2c-amd756-s4882.
66
67config I2C_AMD8111
68 tristate "AMD 8111"
69 depends on I2C && PCI && EXPERIMENTAL
70 help
71 If you say yes to this option, support will be included for the
72 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
73
74 This driver can also be built as a module. If so, the module
75 will be called i2c-amd8111.
76
77config I2C_AU1550
78 tristate "Au1550 SMBus interface"
79 depends on I2C && SOC_AU1550
80 help
81 If you say yes to this option, support will be included for the
82 Au1550 SMBus interface.
83
84 This driver can also be built as a module. If so, the module
85 will be called i2c-au1550.
86
87config I2C_ELEKTOR
88 tristate "Elektor ISA card"
89 depends on I2C && ISA && BROKEN_ON_SMP
90 select I2C_ALGOPCF
91 help
92 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
93 such an adapter.
94
95 This support is also available as a module. If so, the module
96 will be called i2c-elektor.
97
98config I2C_HYDRA
99 tristate "CHRP Apple Hydra Mac I/O I2C interface"
100 depends on I2C && PCI && PPC_CHRP && EXPERIMENTAL
101 select I2C_ALGOBIT
102 help
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
105 have such a machine.
106
107 This support is also available as a module. If so, the module
108 will be called i2c-hydra.
109
110config I2C_I801
111 tristate "Intel 82801 (ICH)"
112 depends on I2C && PCI && EXPERIMENTAL
113 help
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:
117 82801AA
118 82801AB
119 82801BA
120 82801CA/CAM
121 82801DB
122 82801EB/ER (ICH5/ICH5R)
123 6300ESB
124 ICH6
125 ICH7
Jason Gastonb0a70b52005-04-16 15:24:45 -0700126 ESB2
Linus Torvalds1da177e2005-04-16 15:20:36 -0700127
128 This driver can also be built as a module. If so, the module
129 will be called i2c-i801.
130
131config I2C_I810
132 tristate "Intel 810/815"
133 depends on I2C && PCI && EXPERIMENTAL
134 select I2C_ALGOBIT
135 help
136 If you say yes to this option, support will be included for the Intel
137 810/815 family of mainboard I2C interfaces. Specifically, the
138 following versions of the chipset is supported:
139 i810AA
140 i810AB
141 i810E
142 i815
143
144 This driver can also be built as a module. If so, the module
145 will be called i2c-i810.
146
147config I2C_PIIX4
148 tristate "Intel PIIX4"
149 depends on I2C && PCI
150 help
151 If you say yes to this option, support will be included for the Intel
152 PIIX4 family of mainboard I2C interfaces. Specifically, the following
153 versions of the chipset are supported:
154 Intel PIIX4
155 Intel 440MX
156 Serverworks OSB4
157 Serverworks CSB5
158 Serverworks CSB6
159 SMSC Victory66
160
161 This driver can also be built as a module. If so, the module
162 will be called i2c-piix4.
163
164config I2C_IBM_IIC
165 tristate "IBM PPC 4xx on-chip I2C interface"
166 depends on IBM_OCP && I2C
167 help
168 Say Y here if you want to use IIC peripheral found on
169 embedded IBM PPC 4xx based systems.
170
171 This driver can also be built as a module. If so, the module
172 will be called i2c-ibm_iic.
173
174config I2C_IOP3XX
175 tristate "Intel IOP3xx and IXP4xx on-chip I2C interface"
176 depends on (ARCH_IOP3XX || ARCH_IXP4XX) && I2C
177 help
178 Say Y here if you want to use the IIC bus controller on
179 the Intel IOP3xx I/O Processors or IXP4xx Network Processors.
180
181 This driver can also be built as a module. If so, the module
182 will be called i2c-iop3xx.
183
184config I2C_ISA
185 tristate "ISA Bus support"
186 depends on I2C && EXPERIMENTAL
187 help
188 If you say yes to this option, support will be included for i2c
189 interfaces that are on the ISA bus.
190
191 This driver can also be built as a module. If so, the module
192 will be called i2c-isa.
193
194config I2C_ITE
195 tristate "ITE I2C Adapter"
196 depends on I2C && MIPS_ITE8172
197 select I2C_ALGOITE
198 help
199 This supports the ITE8172 I2C peripheral found on some MIPS
200 systems. Say Y if you have one of these. You should also say Y for
201 the ITE I2C driver algorithm support above.
202
203 This support is also available as a module. If so, the module
204 will be called i2c-ite.
205
206config I2C_IXP4XX
207 tristate "IXP4xx GPIO-Based I2C Interface"
208 depends on I2C && ARCH_IXP4XX
209 select I2C_ALGOBIT
210 help
211 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
212 system and are using GPIO lines for an I2C bus.
213
214 This support is also available as a module. If so, the module
215 will be called i2c-ixp4xx.
216
217config I2C_IXP2000
218 tristate "IXP2000 GPIO-Based I2C Interface"
219 depends on I2C && ARCH_IXP2000
220 select I2C_ALGOBIT
221 help
222 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
223 system and are using GPIO lines for an I2C bus.
224
225 This support is also available as a module. If so, the module
226 will be called i2c-ixp2000.
227
228config I2C_KEYWEST
229 tristate "Powermac Keywest I2C interface"
230 depends on I2C && PPC_PMAC
231 help
232 This supports the use of the I2C interface in the combo-I/O
233 chip on recent Apple machines. Say Y if you have such a machine.
234
235 This support is also available as a module. If so, the module
236 will be called i2c-keywest.
237
238config I2C_MPC
239 tristate "MPC107/824x/85xx/52xx"
Al Virob5a48da2005-04-24 12:28:35 -0700240 depends on I2C && PPC32
Linus Torvalds1da177e2005-04-16 15:20:36 -0700241 help
242 If you say yes to this option, support will be included for the
243 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
244 MPC85xx family processors. The driver may also work on 52xx
245 family processors, though interrupts are known not to work.
246
247 This driver can also be built as a module. If so, the module
248 will be called i2c-mpc.
249
250config I2C_NFORCE2
251 tristate "Nvidia Nforce2"
252 depends on I2C && PCI && EXPERIMENTAL
253 help
254 If you say yes to this option, support will be included for the Nvidia
255 Nforce2 family of mainboard I2C interfaces.
256 This driver also supports the nForce3 Pro 150 MCP.
257
258 This driver can also be built as a module. If so, the module
259 will be called i2c-nforce2.
260
261config I2C_PARPORT
262 tristate "Parallel port adapter"
263 depends on I2C && PARPORT
264 select I2C_ALGOBIT
265 help
266 This supports parallel port I2C adapters such as the ones made by
267 Philips or Velleman, Analog Devices evaluation boards, and more.
268 Basically any adapter using the parallel port as an I2C bus with
269 no extra chipset is supported by this driver, or could be.
270
271 This driver is a replacement for (and was inspired by) an older
272 driver named i2c-philips-par. The new driver supports more devices,
273 and makes it easier to add support for new devices.
274
275 Another driver exists, named i2c-parport-light, which doesn't depend
276 on the parport driver. This is meant for embedded systems. Don't say
277 Y here if you intend to say Y or M there.
278
279 This support is also available as a module. If so, the module
280 will be called i2c-parport.
281
282config I2C_PARPORT_LIGHT
283 tristate "Parallel port adapter (light)"
284 depends on I2C
285 select I2C_ALGOBIT
286 help
287 This supports parallel port I2C adapters such as the ones made by
288 Philips or Velleman, Analog Devices evaluation boards, and more.
289 Basically any adapter using the parallel port as an I2C bus with
290 no extra chipset is supported by this driver, or could be.
291
292 This driver is a light version of i2c-parport. It doesn't depend
293 on the parport driver, and uses direct I/O access instead. This
294 might be prefered on embedded systems where wasting memory for
295 the clean but heavy parport handling is not an option. The
296 drawback is a reduced portability and the impossibility to
297 dasiy-chain other parallel port devices.
298
299 Don't say Y here if you said Y or M to i2c-parport. Saying M to
300 both is possible but both modules should not be loaded at the same
301 time.
302
303 This support is also available as a module. If so, the module
304 will be called i2c-parport-light.
305
306config I2C_PROSAVAGE
307 tristate "S3/VIA (Pro)Savage"
308 depends on I2C && PCI && EXPERIMENTAL
309 select I2C_ALGOBIT
310 help
311 If you say yes to this option, support will be included for the
312 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
313 graphics processors.
314 chipsets supported:
315 S3/VIA KM266/VT8375 aka ProSavage8
316 S3/VIA KM133/VT8365 aka Savage4
317
318 This support is also available as a module. If so, the module
319 will be called i2c-prosavage.
320
321config I2C_RPXLITE
322 tristate "Embedded Planet RPX Lite/Classic support"
323 depends on (RPXLITE || RPXCLASSIC) && I2C
324 select I2C_ALGO8XX
325
326config I2C_S3C2410
327 tristate "S3C2410 I2C Driver"
328 depends on I2C && ARCH_S3C2410
329 help
330 Say Y here to include support for I2C controller in the
331 Samsung S3C2410 based System-on-Chip devices.
332
333config I2C_SAVAGE4
334 tristate "S3 Savage 4"
335 depends on I2C && PCI && EXPERIMENTAL
336 select I2C_ALGOBIT
337 help
338 If you say yes to this option, support will be included for the
339 S3 Savage 4 I2C interface.
340
341 This driver can also be built as a module. If so, the module
342 will be called i2c-savage4.
343
344config I2C_SIBYTE
345 tristate "SiByte SMBus interface"
346 depends on SIBYTE_SB1xxx_SOC && I2C
347 help
348 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
349
350config SCx200_I2C
351 tristate "NatSemi SCx200 I2C using GPIO pins"
352 depends on SCx200_GPIO && I2C
353 select I2C_ALGOBIT
354 help
355 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
356
357 If you don't know what to do here, say N.
358
359 This support is also available as a module. If so, the module
360 will be called scx200_i2c.
361
362config SCx200_I2C_SCL
363 int "GPIO pin used for SCL"
364 depends on SCx200_I2C
365 default "12"
366 help
367 Enter the GPIO pin number used for the SCL signal. This value can
368 also be specified with a module parameter.
369
370config SCx200_I2C_SDA
371 int "GPIO pin used for SDA"
372 depends on SCx200_I2C
373 default "13"
374 help
375 Enter the GPIO pin number used for the SSA signal. This value can
376 also be specified with a module parameter.
377
378config SCx200_ACB
379 tristate "NatSemi SCx200 ACCESS.bus"
380 depends on I2C && PCI
381 help
382 Enable the use of the ACCESS.bus controllers of a SCx200 processor.
383
384 If you don't know what to do here, say N.
385
386 This support is also available as a module. If so, the module
387 will be called scx200_acb.
388
389config I2C_SIS5595
390 tristate "SiS 5595"
391 depends on I2C && PCI && EXPERIMENTAL
392 help
393 If you say yes to this option, support will be included for the
394 SiS5595 SMBus (a subset of I2C) interface.
395
396 This driver can also be built as a module. If so, the module
397 will be called i2c-sis5595.
398
399config I2C_SIS630
400 tristate "SiS 630/730"
401 depends on I2C && PCI && EXPERIMENTAL
402 help
403 If you say yes to this option, support will be included for the
404 SiS630 and SiS730 SMBus (a subset of I2C) interface.
405
406 This driver can also be built as a module. If so, the module
407 will be called i2c-sis630.
408
409config I2C_SIS96X
410 tristate "SiS 96x"
411 depends on I2C && PCI && EXPERIMENTAL
412 help
413 If you say yes to this option, support will be included for the SiS
414 96x SMBus (a subset of I2C) interfaces. Specifically, the following
415 chipsets are supported:
416 645/961
417 645DX/961
418 645DX/962
419 648/961
420 650/961
421 735
422
423 This driver can also be built as a module. If so, the module
424 will be called i2c-sis96x.
425
426config I2C_STUB
427 tristate "I2C/SMBus Test Stub"
428 depends on I2C && EXPERIMENTAL && 'm'
429 default 'n'
430 help
431 This module may be useful to developers of SMBus client drivers,
432 especially for certain kinds of sensor chips.
433
434 If you do build this module, be sure to read the notes and warnings
435 in <file:Documentation/i2c/i2c-stub>.
436
437 If you don't know what to do here, definitely say N.
438
439config I2C_VIA
440 tristate "VIA 82C586B"
441 depends on I2C && PCI && EXPERIMENTAL
442 select I2C_ALGOBIT
443 help
444 If you say yes to this option, support will be included for the VIA
445 82C586B I2C interface
446
447 This driver can also be built as a module. If so, the module
448 will be called i2c-via.
449
450config I2C_VIAPRO
451 tristate "VIA 82C596/82C686/823x"
452 depends on I2C && PCI && EXPERIMENTAL
453 help
454 If you say yes to this option, support will be included for the VIA
455 82C596/82C686/823x I2C interfaces. Specifically, the following
456 chipsets are supported:
457 82C596A/B
458 82C686A/B
459 8231
460 8233
461 8233A
462 8235
463 8237
464
465 This driver can also be built as a module. If so, the module
466 will be called i2c-viapro.
467
468config I2C_VOODOO3
469 tristate "Voodoo 3"
470 depends on I2C && PCI && EXPERIMENTAL
471 select I2C_ALGOBIT
472 help
473 If you say yes to this option, support will be included for the
474 Voodoo 3 I2C interface.
475
476 This driver can also be built as a module. If so, the module
477 will be called i2c-voodoo3.
478
479config I2C_PCA_ISA
480 tristate "PCA9564 on an ISA bus"
481 depends on I2C
482 select I2C_ALGOPCA
483 help
484 This driver supports ISA boards using the Philips PCA 9564
485 Parallel bus to I2C bus controller
486
487 This driver can also be built as a module. If so, the module
488 will be called i2c-pca-isa.
489
490config I2C_MV64XXX
491 tristate "Marvell mv64xxx I2C Controller"
492 depends on I2C && MV64X60 && EXPERIMENTAL
493 help
494 If you say yes to this option, support will be included for the
495 built-in I2C interface on the Marvell 64xxx line of host bridges.
496
497 This driver can also be built as a module. If so, the module
498 will be called i2c-mv64xxx.
499
500endmenu