blob: 510816c16da3b4e73193e4b632174442bc6413bf [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"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +000010 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070011 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"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +000034 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070035 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"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +000044 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070045 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"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +000069 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070070 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
Domen Puncera294de42006-08-13 23:37:13 +020078 tristate "Au1550/Au1200 SMBus interface"
79 depends on I2C && (SOC_AU1550 || SOC_AU1200)
Linus Torvalds1da177e2005-04-16 15:20:36 -070080 help
81 If you say yes to this option, support will be included for the
Domen Puncera294de42006-08-13 23:37:13 +020082 Au1550 and Au1200 SMBus interface.
Linus Torvalds1da177e2005-04-16 15:20:36 -070083
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)"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000112 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700113 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
Jason Gaston8254fc42006-01-09 10:58:08 -0800127 ICH8
Linus Torvalds1da177e2005-04-16 15:20:36 -0700128
129 This driver can also be built as a module. If so, the module
130 will be called i2c-i801.
131
132config I2C_I810
133 tristate "Intel 810/815"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000134 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700135 select I2C_ALGOBIT
136 help
137 If you say yes to this option, support will be included for the Intel
138 810/815 family of mainboard I2C interfaces. Specifically, the
Jean Delvare142078f2005-10-26 21:21:50 +0200139 following versions of the chipset are supported:
Linus Torvalds1da177e2005-04-16 15:20:36 -0700140 i810AA
141 i810AB
142 i810E
143 i815
Jean Delvare142078f2005-10-26 21:21:50 +0200144 i845G
Linus Torvalds1da177e2005-04-16 15:20:36 -0700145
146 This driver can also be built as a module. If so, the module
147 will be called i2c-i810.
148
Russell Kingb652b432005-06-15 12:38:14 +0100149config I2C_PXA
150 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
151 depends on I2C && EXPERIMENTAL && ARCH_PXA
152 help
153 If you have devices in the PXA I2C bus, say yes to this option.
154 This driver can also be built as a module. If so, the module
155 will be called i2c-pxa.
156
157config I2C_PXA_SLAVE
158 bool "Intel PXA2XX I2C Slave comms support"
159 depends on I2C_PXA
160 help
161 Support I2C slave mode communications on the PXA I2C bus. This
162 is necessary for systems where the PXA may be a target on the
163 I2C bus.
164
Linus Torvalds1da177e2005-04-16 15:20:36 -0700165config I2C_PIIX4
Rudolf Marek02e0c5d2006-03-23 16:48:09 +0100166 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700167 depends on I2C && PCI
168 help
169 If you say yes to this option, support will be included for the Intel
170 PIIX4 family of mainboard I2C interfaces. Specifically, the following
Martin Devera5f7ea3c2006-02-27 23:11:45 +0100171 versions of the chipset are supported (note that Serverworks is part
172 of Broadcom):
Linus Torvalds1da177e2005-04-16 15:20:36 -0700173 Intel PIIX4
174 Intel 440MX
Rudolf Marek02e0c5d2006-03-23 16:48:09 +0100175 ATI IXP200
176 ATI IXP300
177 ATI IXP400
Linus Torvalds1da177e2005-04-16 15:20:36 -0700178 Serverworks OSB4
179 Serverworks CSB5
180 Serverworks CSB6
Martin Devera5f7ea3c2006-02-27 23:11:45 +0100181 Serverworks HT-1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700182 SMSC Victory66
183
184 This driver can also be built as a module. If so, the module
185 will be called i2c-piix4.
186
187config I2C_IBM_IIC
188 tristate "IBM PPC 4xx on-chip I2C interface"
189 depends on IBM_OCP && I2C
190 help
191 Say Y here if you want to use IIC peripheral found on
192 embedded IBM PPC 4xx based systems.
193
194 This driver can also be built as a module. If so, the module
195 will be called i2c-ibm_iic.
196
197config I2C_IOP3XX
198 tristate "Intel IOP3xx and IXP4xx on-chip I2C interface"
Lennert Buytenhek3f7e5812006-09-18 23:10:26 +0100199 depends on (ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX) && I2C
Linus Torvalds1da177e2005-04-16 15:20:36 -0700200 help
201 Say Y here if you want to use the IIC bus controller on
202 the Intel IOP3xx I/O Processors or IXP4xx Network Processors.
203
204 This driver can also be built as a module. If so, the module
205 will be called i2c-iop3xx.
206
207config I2C_ISA
Jean Delvare5042c7d2005-07-19 23:53:07 +0200208 tristate
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000209 depends on I2C
Linus Torvalds1da177e2005-04-16 15:20:36 -0700210
211config I2C_ITE
212 tristate "ITE I2C Adapter"
213 depends on I2C && MIPS_ITE8172
214 select I2C_ALGOITE
215 help
216 This supports the ITE8172 I2C peripheral found on some MIPS
217 systems. Say Y if you have one of these. You should also say Y for
218 the ITE I2C driver algorithm support above.
219
220 This support is also available as a module. If so, the module
221 will be called i2c-ite.
222
223config I2C_IXP4XX
224 tristate "IXP4xx GPIO-Based I2C Interface"
225 depends on I2C && ARCH_IXP4XX
226 select I2C_ALGOBIT
227 help
228 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
229 system and are using GPIO lines for an I2C bus.
230
231 This support is also available as a module. If so, the module
232 will be called i2c-ixp4xx.
233
234config I2C_IXP2000
235 tristate "IXP2000 GPIO-Based I2C Interface"
236 depends on I2C && ARCH_IXP2000
237 select I2C_ALGOBIT
238 help
239 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
240 system and are using GPIO lines for an I2C bus.
241
242 This support is also available as a module. If so, the module
243 will be called i2c-ixp2000.
244
Benjamin Herrenschmidta28d3af2006-01-07 11:35:26 +1100245config I2C_POWERMAC
246 tristate "Powermac I2C interface"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700247 depends on I2C && PPC_PMAC
Benjamin Herrenschmidta28d3af2006-01-07 11:35:26 +1100248 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -0700249 help
Benjamin Herrenschmidta28d3af2006-01-07 11:35:26 +1100250 This exposes the various PowerMac i2c interfaces to the linux i2c
251 layer and to userland. It is used by various drivers on the powemac
252 platform, thus should generally be enabled.
Benjamin Herrenschmidt0365ba72005-09-22 21:44:06 -0700253
254 This support is also available as a module. If so, the module
Benjamin Herrenschmidta28d3af2006-01-07 11:35:26 +1100255 will be called i2c-powermac.
Benjamin Herrenschmidt0365ba72005-09-22 21:44:06 -0700256
Linus Torvalds1da177e2005-04-16 15:20:36 -0700257config I2C_MPC
Jon Loeliger2097c7f2006-06-17 17:52:54 -0500258 tristate "MPC107/824x/85xx/52xx/86xx"
Al Virob5a48da2005-04-24 12:28:35 -0700259 depends on I2C && PPC32
Linus Torvalds1da177e2005-04-16 15:20:36 -0700260 help
261 If you say yes to this option, support will be included for the
262 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
Jon Loeliger2097c7f2006-06-17 17:52:54 -0500263 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
Linus Torvalds1da177e2005-04-16 15:20:36 -0700264 family processors, though interrupts are known not to work.
265
266 This driver can also be built as a module. If so, the module
267 will be called i2c-mpc.
268
269config I2C_NFORCE2
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000270 tristate "Nvidia nForce2, nForce3 and nForce4"
271 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700272 help
273 If you say yes to this option, support will be included for the Nvidia
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000274 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700275
276 This driver can also be built as a module. If so, the module
277 will be called i2c-nforce2.
278
Peter Korsgaard18f98b12006-06-04 20:01:08 +0200279config I2C_OCORES
280 tristate "OpenCores I2C Controller"
281 depends on I2C && EXPERIMENTAL
282 help
283 If you say yes to this option, support will be included for the
284 OpenCores I2C controller. For details see
285 http://www.opencores.org/projects.cgi/web/i2c/overview
286
287 This driver can also be built as a module. If so, the module
288 will be called i2c-ocores.
289
Komal Shah010d442c42006-08-13 23:44:09 +0200290config I2C_OMAP
291 tristate "OMAP I2C adapter"
292 depends on I2C && ARCH_OMAP
293 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
294 help
295 If you say yes to this option, support will be included for the
296 I2C interface on the Texas Instruments OMAP1/2 family of processors.
297 Like OMAP1510/1610/1710/5912 and OMAP242x.
298 For details see http://www.ti.com/omap.
299
Linus Torvalds1da177e2005-04-16 15:20:36 -0700300config I2C_PARPORT
301 tristate "Parallel port adapter"
302 depends on I2C && PARPORT
303 select I2C_ALGOBIT
304 help
305 This supports parallel port I2C adapters such as the ones made by
306 Philips or Velleman, Analog Devices evaluation boards, and more.
307 Basically any adapter using the parallel port as an I2C bus with
308 no extra chipset is supported by this driver, or could be.
309
310 This driver is a replacement for (and was inspired by) an older
311 driver named i2c-philips-par. The new driver supports more devices,
312 and makes it easier to add support for new devices.
Mark M. Hoffmane97b81d2006-03-23 16:50:25 +0100313
314 An adapter type parameter is now mandatory. Please read the file
315 Documentation/i2c/busses/i2c-parport for details.
316
Linus Torvalds1da177e2005-04-16 15:20:36 -0700317 Another driver exists, named i2c-parport-light, which doesn't depend
318 on the parport driver. This is meant for embedded systems. Don't say
319 Y here if you intend to say Y or M there.
320
321 This support is also available as a module. If so, the module
322 will be called i2c-parport.
323
324config I2C_PARPORT_LIGHT
325 tristate "Parallel port adapter (light)"
326 depends on I2C
327 select I2C_ALGOBIT
328 help
329 This supports parallel port I2C adapters such as the ones made by
330 Philips or Velleman, Analog Devices evaluation boards, and more.
331 Basically any adapter using the parallel port as an I2C bus with
332 no extra chipset is supported by this driver, or could be.
333
334 This driver is a light version of i2c-parport. It doesn't depend
335 on the parport driver, and uses direct I/O access instead. This
Matt LaPlante09509602006-10-03 22:31:37 +0200336 might be preferred on embedded systems where wasting memory for
Linus Torvalds1da177e2005-04-16 15:20:36 -0700337 the clean but heavy parport handling is not an option. The
338 drawback is a reduced portability and the impossibility to
Matt LaPlante09509602006-10-03 22:31:37 +0200339 daisy-chain other parallel port devices.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700340
341 Don't say Y here if you said Y or M to i2c-parport. Saying M to
342 both is possible but both modules should not be loaded at the same
343 time.
344
345 This support is also available as a module. If so, the module
346 will be called i2c-parport-light.
347
348config I2C_PROSAVAGE
349 tristate "S3/VIA (Pro)Savage"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000350 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700351 select I2C_ALGOBIT
352 help
353 If you say yes to this option, support will be included for the
354 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
355 graphics processors.
356 chipsets supported:
357 S3/VIA KM266/VT8375 aka ProSavage8
358 S3/VIA KM133/VT8365 aka Savage4
359
360 This support is also available as a module. If so, the module
361 will be called i2c-prosavage.
362
363config I2C_RPXLITE
364 tristate "Embedded Planet RPX Lite/Classic support"
365 depends on (RPXLITE || RPXCLASSIC) && I2C
366 select I2C_ALGO8XX
367
368config I2C_S3C2410
369 tristate "S3C2410 I2C Driver"
370 depends on I2C && ARCH_S3C2410
371 help
372 Say Y here to include support for I2C controller in the
373 Samsung S3C2410 based System-on-Chip devices.
374
375config I2C_SAVAGE4
376 tristate "S3 Savage 4"
377 depends on I2C && PCI && EXPERIMENTAL
378 select I2C_ALGOBIT
379 help
380 If you say yes to this option, support will be included for the
381 S3 Savage 4 I2C interface.
382
383 This driver can also be built as a module. If so, the module
384 will be called i2c-savage4.
385
386config I2C_SIBYTE
387 tristate "SiByte SMBus interface"
388 depends on SIBYTE_SB1xxx_SOC && I2C
389 help
390 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
391
392config SCx200_I2C
393 tristate "NatSemi SCx200 I2C using GPIO pins"
394 depends on SCx200_GPIO && I2C
395 select I2C_ALGOBIT
396 help
397 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
398
399 If you don't know what to do here, say N.
400
401 This support is also available as a module. If so, the module
402 will be called scx200_i2c.
403
404config SCx200_I2C_SCL
405 int "GPIO pin used for SCL"
406 depends on SCx200_I2C
407 default "12"
408 help
409 Enter the GPIO pin number used for the SCL signal. This value can
410 also be specified with a module parameter.
411
412config SCx200_I2C_SDA
413 int "GPIO pin used for SDA"
414 depends on SCx200_I2C
415 default "13"
416 help
417 Enter the GPIO pin number used for the SSA signal. This value can
418 also be specified with a module parameter.
419
420config SCx200_ACB
Ben Gardnera417bbd2006-01-18 22:53:09 +0100421 tristate "Geode ACCESS.bus support"
Jean Delvarecdf263f2006-01-22 12:28:57 +0100422 depends on X86_32 && I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700423 help
Ben Gardnera417bbd2006-01-18 22:53:09 +0100424 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
425 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700426
427 If you don't know what to do here, say N.
428
429 This support is also available as a module. If so, the module
430 will be called scx200_acb.
431
432config I2C_SIS5595
433 tristate "SiS 5595"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000434 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700435 help
436 If you say yes to this option, support will be included for the
437 SiS5595 SMBus (a subset of I2C) interface.
438
439 This driver can also be built as a module. If so, the module
440 will be called i2c-sis5595.
441
442config I2C_SIS630
443 tristate "SiS 630/730"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000444 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700445 help
446 If you say yes to this option, support will be included for the
447 SiS630 and SiS730 SMBus (a subset of I2C) interface.
448
449 This driver can also be built as a module. If so, the module
450 will be called i2c-sis630.
451
452config I2C_SIS96X
453 tristate "SiS 96x"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000454 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700455 help
456 If you say yes to this option, support will be included for the SiS
457 96x SMBus (a subset of I2C) interfaces. Specifically, the following
458 chipsets are supported:
459 645/961
460 645DX/961
461 645DX/962
462 648/961
463 650/961
464 735
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000465 745
Linus Torvalds1da177e2005-04-16 15:20:36 -0700466
467 This driver can also be built as a module. If so, the module
468 will be called i2c-sis96x.
469
470config I2C_STUB
471 tristate "I2C/SMBus Test Stub"
472 depends on I2C && EXPERIMENTAL && 'm'
473 default 'n'
474 help
475 This module may be useful to developers of SMBus client drivers,
476 especially for certain kinds of sensor chips.
477
478 If you do build this module, be sure to read the notes and warnings
479 in <file:Documentation/i2c/i2c-stub>.
480
481 If you don't know what to do here, definitely say N.
482
483config I2C_VIA
484 tristate "VIA 82C586B"
485 depends on I2C && PCI && EXPERIMENTAL
486 select I2C_ALGOBIT
487 help
488 If you say yes to this option, support will be included for the VIA
489 82C586B I2C interface
490
491 This driver can also be built as a module. If so, the module
492 will be called i2c-via.
493
494config I2C_VIAPRO
Rudolf Marekc2433532006-09-03 22:35:21 +0200495 tristate "VIA 82C596/82C686/82xx"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000496 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700497 help
498 If you say yes to this option, support will be included for the VIA
Rudolf Marekc2433532006-09-03 22:35:21 +0200499 82C596/82C686/82xx I2C interfaces. Specifically, the following
Linus Torvalds1da177e2005-04-16 15:20:36 -0700500 chipsets are supported:
Rudolf Marekc2433532006-09-03 22:35:21 +0200501 VT82C596A/B
502 VT82C686A/B
503 VT8231
504 VT8233/A
505 VT8235
506 VT8237R/A
507 VT8251
Linus Torvalds1da177e2005-04-16 15:20:36 -0700508
509 This driver can also be built as a module. If so, the module
510 will be called i2c-viapro.
511
512config I2C_VOODOO3
513 tristate "Voodoo 3"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000514 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700515 select I2C_ALGOBIT
516 help
517 If you say yes to this option, support will be included for the
518 Voodoo 3 I2C interface.
519
520 This driver can also be built as a module. If so, the module
521 will be called i2c-voodoo3.
522
523config I2C_PCA_ISA
524 tristate "PCA9564 on an ISA bus"
525 depends on I2C
526 select I2C_ALGOPCA
Jean Delvareaee62302006-06-04 19:59:57 +0200527 default n
Linus Torvalds1da177e2005-04-16 15:20:36 -0700528 help
529 This driver supports ISA boards using the Philips PCA 9564
530 Parallel bus to I2C bus controller
531
532 This driver can also be built as a module. If so, the module
533 will be called i2c-pca-isa.
534
Jean Delvareaee62302006-06-04 19:59:57 +0200535 This device is almost undetectable and using this driver on a
536 system which doesn't have this device will result in long
537 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
538 time). If unsure, say N.
539
Linus Torvalds1da177e2005-04-16 15:20:36 -0700540config I2C_MV64XXX
541 tristate "Marvell mv64xxx I2C Controller"
542 depends on I2C && MV64X60 && EXPERIMENTAL
543 help
544 If you say yes to this option, support will be included for the
545 built-in I2C interface on the Marvell 64xxx line of host bridges.
546
547 This driver can also be built as a module. If so, the module
548 will be called i2c-mv64xxx.
549
550endmenu