blob: 33a8a67f161b9b01bc324f7325b757ce71abc5d6 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Sensor device configuration
3#
4
5menu "I2C Hardware Bus support"
Linus Torvalds1da177e2005-04-16 15:20:36 -07006
7config I2C_ALI1535
8 tristate "ALI 1535"
Jan Engelhardt16538e62007-05-01 23:26:34 +02009 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070010 help
11 If you say yes to this option, support will be included for the SMB
12 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
13 controller is part of the 7101 device, which is an ACPI-compliant
14 Power Management Unit (PMU).
15
16 This driver can also be built as a module. If so, the module
17 will be called i2c-ali1535.
18
19config I2C_ALI1563
20 tristate "ALI 1563"
Jan Engelhardt16538e62007-05-01 23:26:34 +020021 depends on PCI && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -070022 help
23 If you say yes to this option, support will be included for the SMB
24 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
25 controller is part of the 7101 device, which is an ACPI-compliant
26 Power Management Unit (PMU).
27
28 This driver can also be built as a module. If so, the module
29 will be called i2c-ali1563.
30
31config I2C_ALI15X3
32 tristate "ALI 15x3"
Jan Engelhardt16538e62007-05-01 23:26:34 +020033 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070034 help
35 If you say yes to this option, support will be included for the
36 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
37
38 This driver can also be built as a module. If so, the module
39 will be called i2c-ali15x3.
40
41config I2C_AMD756
42 tristate "AMD 756/766/768/8111 and nVidia nForce"
Jan Engelhardt16538e62007-05-01 23:26:34 +020043 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070044 help
45 If you say yes to this option, support will be included for the AMD
46 756/766/768 mainboard I2C interfaces. The driver also includes
47 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
48 the nVidia nForce I2C interface.
49
50 This driver can also be built as a module. If so, the module
51 will be called i2c-amd756.
52
53config I2C_AMD756_S4882
54 tristate "SMBus multiplexing on the Tyan S4882"
55 depends on I2C_AMD756 && EXPERIMENTAL
56 help
57 Enabling this option will add specific SMBus support for the Tyan
58 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
59 over 8 different channels, where the various memory module EEPROMs
60 and temperature sensors live. Saying yes here will give you access
61 to these in addition to the trunk.
62
63 This driver can also be built as a module. If so, the module
64 will be called i2c-amd756-s4882.
65
66config I2C_AMD8111
67 tristate "AMD 8111"
Jan Engelhardt16538e62007-05-01 23:26:34 +020068 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070069 help
70 If you say yes to this option, support will be included for the
71 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
72
73 This driver can also be built as a module. If so, the module
74 will be called i2c-amd8111.
75
Andrew Victor813e30e2006-12-10 21:21:30 +010076config I2C_AT91
77 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
Jan Engelhardt16538e62007-05-01 23:26:34 +020078 depends on ARCH_AT91 && EXPERIMENTAL
Andrew Victor813e30e2006-12-10 21:21:30 +010079 help
80 This supports the use of the I2C interface on Atmel AT91
81 processors.
82
Linus Torvalds1da177e2005-04-16 15:20:36 -070083config I2C_AU1550
Domen Puncera294de42006-08-13 23:37:13 +020084 tristate "Au1550/Au1200 SMBus interface"
Jan Engelhardt16538e62007-05-01 23:26:34 +020085 depends on SOC_AU1550 || SOC_AU1200
Linus Torvalds1da177e2005-04-16 15:20:36 -070086 help
87 If you say yes to this option, support will be included for the
Domen Puncera294de42006-08-13 23:37:13 +020088 Au1550 and Au1200 SMBus interface.
Linus Torvalds1da177e2005-04-16 15:20:36 -070089
90 This driver can also be built as a module. If so, the module
91 will be called i2c-au1550.
92
Bryan Wud24ecfc2007-05-01 23:26:32 +020093config I2C_BLACKFIN_TWI
94 tristate "Blackfin TWI I2C support"
Jan Engelhardt16538e62007-05-01 23:26:34 +020095 depends on BF534 || BF536 || BF537
Bryan Wud24ecfc2007-05-01 23:26:32 +020096 help
97 This is the TWI I2C device driver for Blackfin 534/536/537.
98 This driver can also be built as a module. If so, the module
99 will be called i2c-bfin-twi.
100
101config I2C_BLACKFIN_TWI_CLK_KHZ
102 int "Blackfin TWI I2C clock (kHz)"
103 depends on I2C_BLACKFIN_TWI
104 range 10 400
105 default 50
106 help
107 The unit of the TWI clock is kHz.
108
Linus Torvalds1da177e2005-04-16 15:20:36 -0700109config I2C_ELEKTOR
110 tristate "Elektor ISA card"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200111 depends on ISA && BROKEN_ON_SMP
Linus Torvalds1da177e2005-04-16 15:20:36 -0700112 select I2C_ALGOPCF
113 help
114 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
115 such an adapter.
116
117 This support is also available as a module. If so, the module
118 will be called i2c-elektor.
119
Haavard Skinnemoen1c23af92007-05-01 23:26:34 +0200120config I2C_GPIO
121 tristate "GPIO-based bitbanging I2C"
122 depends on GENERIC_GPIO
123 select I2C_ALGOBIT
124 help
125 This is a very simple bitbanging I2C driver utilizing the
126 arch-neutral GPIO API to control the SCL and SDA lines.
127
Linus Torvalds1da177e2005-04-16 15:20:36 -0700128config I2C_HYDRA
129 tristate "CHRP Apple Hydra Mac I/O I2C interface"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200130 depends on PCI && PPC_CHRP && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700131 select I2C_ALGOBIT
132 help
133 This supports the use of the I2C interface in the Apple Hydra Mac
134 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
135 have such a machine.
136
137 This support is also available as a module. If so, the module
138 will be called i2c-hydra.
139
140config I2C_I801
141 tristate "Intel 82801 (ICH)"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200142 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700143 help
144 If you say yes to this option, support will be included for the Intel
145 801 family of mainboard I2C interfaces. Specifically, the following
146 versions of the chipset are supported:
147 82801AA
148 82801AB
149 82801BA
150 82801CA/CAM
151 82801DB
152 82801EB/ER (ICH5/ICH5R)
153 6300ESB
154 ICH6
155 ICH7
Jason Gastonb0a70b52005-04-16 15:24:45 -0700156 ESB2
Jason Gaston8254fc42006-01-09 10:58:08 -0800157 ICH8
Jason Gastonadbc2a12006-11-22 15:19:12 -0800158 ICH9
Linus Torvalds1da177e2005-04-16 15:20:36 -0700159
160 This driver can also be built as a module. If so, the module
161 will be called i2c-i801.
162
163config I2C_I810
164 tristate "Intel 810/815"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200165 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700166 select I2C_ALGOBIT
167 help
168 If you say yes to this option, support will be included for the Intel
169 810/815 family of mainboard I2C interfaces. Specifically, the
Jean Delvare142078f2005-10-26 21:21:50 +0200170 following versions of the chipset are supported:
Linus Torvalds1da177e2005-04-16 15:20:36 -0700171 i810AA
172 i810AB
173 i810E
174 i815
Jean Delvare142078f2005-10-26 21:21:50 +0200175 i845G
Linus Torvalds1da177e2005-04-16 15:20:36 -0700176
177 This driver can also be built as a module. If so, the module
178 will be called i2c-i810.
179
Russell Kingb652b432005-06-15 12:38:14 +0100180config I2C_PXA
181 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200182 depends on EXPERIMENTAL && ARCH_PXA
Russell Kingb652b432005-06-15 12:38:14 +0100183 help
184 If you have devices in the PXA I2C bus, say yes to this option.
185 This driver can also be built as a module. If so, the module
186 will be called i2c-pxa.
187
188config I2C_PXA_SLAVE
189 bool "Intel PXA2XX I2C Slave comms support"
190 depends on I2C_PXA
191 help
192 Support I2C slave mode communications on the PXA I2C bus. This
193 is necessary for systems where the PXA may be a target on the
194 I2C bus.
195
Linus Torvalds1da177e2005-04-16 15:20:36 -0700196config I2C_PIIX4
Rudolf Marek02e0c5d2006-03-23 16:48:09 +0100197 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200198 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700199 help
200 If you say yes to this option, support will be included for the Intel
201 PIIX4 family of mainboard I2C interfaces. Specifically, the following
Martin Devera5f7ea3c2006-02-27 23:11:45 +0100202 versions of the chipset are supported (note that Serverworks is part
203 of Broadcom):
Linus Torvalds1da177e2005-04-16 15:20:36 -0700204 Intel PIIX4
205 Intel 440MX
Rudolf Marek02e0c5d2006-03-23 16:48:09 +0100206 ATI IXP200
207 ATI IXP300
208 ATI IXP400
Jean Delvare4e6697f2007-02-13 22:08:59 +0100209 ATI SB600
Linus Torvalds1da177e2005-04-16 15:20:36 -0700210 Serverworks OSB4
211 Serverworks CSB5
212 Serverworks CSB6
Martin Devera5f7ea3c2006-02-27 23:11:45 +0100213 Serverworks HT-1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700214 SMSC Victory66
215
216 This driver can also be built as a module. If so, the module
217 will be called i2c-piix4.
218
219config I2C_IBM_IIC
220 tristate "IBM PPC 4xx on-chip I2C interface"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200221 depends on IBM_OCP
Linus Torvalds1da177e2005-04-16 15:20:36 -0700222 help
223 Say Y here if you want to use IIC peripheral found on
224 embedded IBM PPC 4xx based systems.
225
226 This driver can also be built as a module. If so, the module
227 will be called i2c-ibm_iic.
228
229config I2C_IOP3XX
Dan Williams285f5fa2006-12-07 02:59:39 +0100230 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200231 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700232 help
233 Say Y here if you want to use the IIC bus controller on
Dan Williams285f5fa2006-12-07 02:59:39 +0100234 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700235
236 This driver can also be built as a module. If so, the module
237 will be called i2c-iop3xx.
238
239config I2C_ISA
Jean Delvare5042c7d2005-07-19 23:53:07 +0200240 tristate
Linus Torvalds1da177e2005-04-16 15:20:36 -0700241
Linus Torvalds1da177e2005-04-16 15:20:36 -0700242config I2C_IXP4XX
243 tristate "IXP4xx GPIO-Based I2C Interface"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200244 depends on ARCH_IXP4XX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700245 select I2C_ALGOBIT
246 help
247 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
248 system and are using GPIO lines for an I2C bus.
249
250 This support is also available as a module. If so, the module
251 will be called i2c-ixp4xx.
252
253config I2C_IXP2000
254 tristate "IXP2000 GPIO-Based I2C Interface"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200255 depends on ARCH_IXP2000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700256 select I2C_ALGOBIT
257 help
258 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
259 system and are using GPIO lines for an I2C bus.
260
261 This support is also available as a module. If so, the module
262 will be called i2c-ixp2000.
263
Benjamin Herrenschmidta28d3af2006-01-07 11:35:26 +1100264config I2C_POWERMAC
265 tristate "Powermac I2C interface"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200266 depends on PPC_PMAC
Benjamin Herrenschmidta28d3af2006-01-07 11:35:26 +1100267 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -0700268 help
Benjamin Herrenschmidta28d3af2006-01-07 11:35:26 +1100269 This exposes the various PowerMac i2c interfaces to the linux i2c
270 layer and to userland. It is used by various drivers on the powemac
271 platform, thus should generally be enabled.
Benjamin Herrenschmidt0365ba72005-09-22 21:44:06 -0700272
273 This support is also available as a module. If so, the module
Benjamin Herrenschmidta28d3af2006-01-07 11:35:26 +1100274 will be called i2c-powermac.
Benjamin Herrenschmidt0365ba72005-09-22 21:44:06 -0700275
Linus Torvalds1da177e2005-04-16 15:20:36 -0700276config I2C_MPC
Jon Loeliger2097c7f2006-06-17 17:52:54 -0500277 tristate "MPC107/824x/85xx/52xx/86xx"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200278 depends on PPC32
Linus Torvalds1da177e2005-04-16 15:20:36 -0700279 help
280 If you say yes to this option, support will be included for the
281 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
Jon Loeliger2097c7f2006-06-17 17:52:54 -0500282 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
Linus Torvalds1da177e2005-04-16 15:20:36 -0700283 family processors, though interrupts are known not to work.
284
285 This driver can also be built as a module. If so, the module
286 will be called i2c-mpc.
287
288config I2C_NFORCE2
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000289 tristate "Nvidia nForce2, nForce3 and nForce4"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200290 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700291 help
292 If you say yes to this option, support will be included for the Nvidia
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000293 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700294
295 This driver can also be built as a module. If so, the module
296 will be called i2c-nforce2.
297
Peter Korsgaard18f98b12006-06-04 20:01:08 +0200298config I2C_OCORES
299 tristate "OpenCores I2C Controller"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200300 depends on EXPERIMENTAL
Peter Korsgaard18f98b12006-06-04 20:01:08 +0200301 help
302 If you say yes to this option, support will be included for the
303 OpenCores I2C controller. For details see
304 http://www.opencores.org/projects.cgi/web/i2c/overview
305
306 This driver can also be built as a module. If so, the module
307 will be called i2c-ocores.
308
Komal Shah010d442c42006-08-13 23:44:09 +0200309config I2C_OMAP
310 tristate "OMAP I2C adapter"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200311 depends on ARCH_OMAP
Komal Shah010d442c42006-08-13 23:44:09 +0200312 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
313 help
314 If you say yes to this option, support will be included for the
315 I2C interface on the Texas Instruments OMAP1/2 family of processors.
316 Like OMAP1510/1610/1710/5912 and OMAP242x.
317 For details see http://www.ti.com/omap.
318
Linus Torvalds1da177e2005-04-16 15:20:36 -0700319config I2C_PARPORT
320 tristate "Parallel port adapter"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200321 depends on PARPORT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700322 select I2C_ALGOBIT
323 help
324 This supports parallel port I2C adapters such as the ones made by
325 Philips or Velleman, Analog Devices evaluation boards, and more.
326 Basically any adapter using the parallel port as an I2C bus with
327 no extra chipset is supported by this driver, or could be.
328
329 This driver is a replacement for (and was inspired by) an older
330 driver named i2c-philips-par. The new driver supports more devices,
331 and makes it easier to add support for new devices.
Mark M. Hoffmane97b81d2006-03-23 16:50:25 +0100332
333 An adapter type parameter is now mandatory. Please read the file
334 Documentation/i2c/busses/i2c-parport for details.
335
Linus Torvalds1da177e2005-04-16 15:20:36 -0700336 Another driver exists, named i2c-parport-light, which doesn't depend
337 on the parport driver. This is meant for embedded systems. Don't say
338 Y here if you intend to say Y or M there.
339
340 This support is also available as a module. If so, the module
341 will be called i2c-parport.
342
343config I2C_PARPORT_LIGHT
344 tristate "Parallel port adapter (light)"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700345 select I2C_ALGOBIT
346 help
347 This supports parallel port I2C adapters such as the ones made by
348 Philips or Velleman, Analog Devices evaluation boards, and more.
349 Basically any adapter using the parallel port as an I2C bus with
350 no extra chipset is supported by this driver, or could be.
351
352 This driver is a light version of i2c-parport. It doesn't depend
353 on the parport driver, and uses direct I/O access instead. This
Matt LaPlante09509602006-10-03 22:31:37 +0200354 might be preferred on embedded systems where wasting memory for
Linus Torvalds1da177e2005-04-16 15:20:36 -0700355 the clean but heavy parport handling is not an option. The
356 drawback is a reduced portability and the impossibility to
Matt LaPlante09509602006-10-03 22:31:37 +0200357 daisy-chain other parallel port devices.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700358
359 Don't say Y here if you said Y or M to i2c-parport. Saying M to
360 both is possible but both modules should not be loaded at the same
361 time.
362
363 This support is also available as a module. If so, the module
364 will be called i2c-parport-light.
365
Olof Johanssonbeb58aa2007-02-13 22:09:03 +0100366config I2C_PASEMI
367 tristate "PA Semi SMBus interface"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200368 depends on PPC_PASEMI && PCI
Olof Johanssonbeb58aa2007-02-13 22:09:03 +0100369 help
370 Supports the PA Semi PWRficient on-chip SMBus interfaces.
371
Linus Torvalds1da177e2005-04-16 15:20:36 -0700372config I2C_PROSAVAGE
373 tristate "S3/VIA (Pro)Savage"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200374 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700375 select I2C_ALGOBIT
376 help
377 If you say yes to this option, support will be included for the
378 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
379 graphics processors.
380 chipsets supported:
381 S3/VIA KM266/VT8375 aka ProSavage8
382 S3/VIA KM133/VT8365 aka Savage4
383
384 This support is also available as a module. If so, the module
385 will be called i2c-prosavage.
386
387config I2C_RPXLITE
388 tristate "Embedded Planet RPX Lite/Classic support"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200389 depends on RPXLITE || RPXCLASSIC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700390 select I2C_ALGO8XX
391
392config I2C_S3C2410
393 tristate "S3C2410 I2C Driver"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200394 depends on ARCH_S3C2410
Linus Torvalds1da177e2005-04-16 15:20:36 -0700395 help
396 Say Y here to include support for I2C controller in the
397 Samsung S3C2410 based System-on-Chip devices.
398
399config I2C_SAVAGE4
400 tristate "S3 Savage 4"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200401 depends on PCI && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700402 select I2C_ALGOBIT
403 help
404 If you say yes to this option, support will be included for the
405 S3 Savage 4 I2C interface.
406
407 This driver can also be built as a module. If so, the module
408 will be called i2c-savage4.
409
410config I2C_SIBYTE
411 tristate "SiByte SMBus interface"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200412 depends on SIBYTE_SB1xxx_SOC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700413 help
414 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
415
416config SCx200_I2C
417 tristate "NatSemi SCx200 I2C using GPIO pins"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200418 depends on SCx200_GPIO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700419 select I2C_ALGOBIT
420 help
421 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
422
423 If you don't know what to do here, say N.
424
425 This support is also available as a module. If so, the module
426 will be called scx200_i2c.
427
428config SCx200_I2C_SCL
429 int "GPIO pin used for SCL"
430 depends on SCx200_I2C
431 default "12"
432 help
433 Enter the GPIO pin number used for the SCL signal. This value can
434 also be specified with a module parameter.
435
436config SCx200_I2C_SDA
437 int "GPIO pin used for SDA"
438 depends on SCx200_I2C
439 default "13"
440 help
441 Enter the GPIO pin number used for the SSA signal. This value can
442 also be specified with a module parameter.
443
444config SCx200_ACB
Ben Gardnera417bbd2006-01-18 22:53:09 +0100445 tristate "Geode ACCESS.bus support"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200446 depends on X86_32 && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700447 help
Ben Gardnera417bbd2006-01-18 22:53:09 +0100448 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
449 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700450
451 If you don't know what to do here, say N.
452
453 This support is also available as a module. If so, the module
454 will be called scx200_acb.
455
456config I2C_SIS5595
457 tristate "SiS 5595"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200458 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700459 help
460 If you say yes to this option, support will be included for the
461 SiS5595 SMBus (a subset of I2C) interface.
462
463 This driver can also be built as a module. If so, the module
464 will be called i2c-sis5595.
465
466config I2C_SIS630
467 tristate "SiS 630/730"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200468 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700469 help
470 If you say yes to this option, support will be included for the
471 SiS630 and SiS730 SMBus (a subset of I2C) interface.
472
473 This driver can also be built as a module. If so, the module
474 will be called i2c-sis630.
475
476config I2C_SIS96X
477 tristate "SiS 96x"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200478 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700479 help
480 If you say yes to this option, support will be included for the SiS
481 96x SMBus (a subset of I2C) interfaces. Specifically, the following
482 chipsets are supported:
483 645/961
484 645DX/961
485 645DX/962
486 648/961
487 650/961
488 735
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000489 745
Linus Torvalds1da177e2005-04-16 15:20:36 -0700490
491 This driver can also be built as a module. If so, the module
492 will be called i2c-sis96x.
493
494config I2C_STUB
495 tristate "I2C/SMBus Test Stub"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200496 depends on EXPERIMENTAL && m
Linus Torvalds1da177e2005-04-16 15:20:36 -0700497 default 'n'
498 help
499 This module may be useful to developers of SMBus client drivers,
500 especially for certain kinds of sensor chips.
501
502 If you do build this module, be sure to read the notes and warnings
503 in <file:Documentation/i2c/i2c-stub>.
504
505 If you don't know what to do here, definitely say N.
506
Russell King6b65cd72006-12-10 21:21:32 +0100507config I2C_VERSATILE
508 tristate "ARM Versatile/Realview I2C bus support"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200509 depends on ARCH_VERSATILE || ARCH_REALVIEW
Russell King6b65cd72006-12-10 21:21:32 +0100510 select I2C_ALGOBIT
511 help
512 Say yes if you want to support the I2C serial bus on ARMs Versatile
513 range of platforms.
514
515 This driver can also be built as a module. If so, the module
516 will be called i2c-versatile.
517
Russell King8d91cba2007-03-04 20:40:50 +0000518config I2C_ACORN
519 bool "Acorn IOC/IOMD I2C bus support"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200520 depends on ARCH_ACORN
Russell King8d91cba2007-03-04 20:40:50 +0000521 default y
522 select I2C_ALGOBIT
523 help
524 Say yes if you want to support the I2C bus on Acorn platforms.
525
526 If you don't know, say Y.
527
Linus Torvalds1da177e2005-04-16 15:20:36 -0700528config I2C_VIA
529 tristate "VIA 82C586B"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200530 depends on PCI && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700531 select I2C_ALGOBIT
532 help
533 If you say yes to this option, support will be included for the VIA
534 82C586B I2C interface
535
536 This driver can also be built as a module. If so, the module
537 will be called i2c-via.
538
539config I2C_VIAPRO
Jean Delvareab6a6ed2007-02-13 22:09:02 +0100540 tristate "VIA VT82C596/82C686/82xx and CX700"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200541 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700542 help
543 If you say yes to this option, support will be included for the VIA
Jean Delvareab6a6ed2007-02-13 22:09:02 +0100544 VT82C596 and later SMBus interface. Specifically, the following
Linus Torvalds1da177e2005-04-16 15:20:36 -0700545 chipsets are supported:
Rudolf Marekc2433532006-09-03 22:35:21 +0200546 VT82C596A/B
547 VT82C686A/B
548 VT8231
549 VT8233/A
550 VT8235
551 VT8237R/A
552 VT8251
Jean Delvareab6a6ed2007-02-13 22:09:02 +0100553 CX700
Linus Torvalds1da177e2005-04-16 15:20:36 -0700554
555 This driver can also be built as a module. If so, the module
556 will be called i2c-viapro.
557
558config I2C_VOODOO3
559 tristate "Voodoo 3"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200560 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700561 select I2C_ALGOBIT
562 help
563 If you say yes to this option, support will be included for the
564 Voodoo 3 I2C interface.
565
566 This driver can also be built as a module. If so, the module
567 will be called i2c-voodoo3.
568
569config I2C_PCA_ISA
570 tristate "PCA9564 on an ISA bus"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200571 depends on ISA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700572 select I2C_ALGOPCA
Jean Delvareaee62302006-06-04 19:59:57 +0200573 default n
Linus Torvalds1da177e2005-04-16 15:20:36 -0700574 help
575 This driver supports ISA boards using the Philips PCA 9564
576 Parallel bus to I2C bus controller
577
578 This driver can also be built as a module. If so, the module
579 will be called i2c-pca-isa.
580
Jean Delvareaee62302006-06-04 19:59:57 +0200581 This device is almost undetectable and using this driver on a
582 system which doesn't have this device will result in long
583 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
584 time). If unsure, say N.
585
Linus Torvalds1da177e2005-04-16 15:20:36 -0700586config I2C_MV64XXX
587 tristate "Marvell mv64xxx I2C Controller"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200588 depends on MV64X60 && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700589 help
590 If you say yes to this option, support will be included for the
591 built-in I2C interface on the Marvell 64xxx line of host bridges.
592
593 This driver can also be built as a module. If so, the module
594 will be called i2c-mv64xxx.
595
Vitaly Wool41561f22006-12-10 21:21:29 +0100596config I2C_PNX
597 tristate "I2C bus support for Philips PNX targets"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200598 depends on ARCH_PNX4008
Vitaly Wool41561f22006-12-10 21:21:29 +0100599 help
600 This driver supports the Philips IP3204 I2C IP block master and/or
601 slave controller
602
603 This driver can also be built as a module. If so, the module
604 will be called i2c-pnx.
605
Linus Torvalds1da177e2005-04-16 15:20:36 -0700606endmenu