blob: 5d4aa5e873cac53075248c283a411523ab37d9ac [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
Jean Delvaref5b728a2008-07-14 22:38:23 +02007comment "PC SMBus host controller drivers"
8 depends on PCI
9
Linus Torvalds1da177e2005-04-16 15:20:36 -070010config I2C_ALI1535
11 tristate "ALI 1535"
Jan Engelhardt16538e62007-05-01 23:26:34 +020012 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070013 help
14 If you say yes to this option, support will be included for the SMB
15 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
16 controller is part of the 7101 device, which is an ACPI-compliant
17 Power Management Unit (PMU).
18
19 This driver can also be built as a module. If so, the module
20 will be called i2c-ali1535.
21
22config I2C_ALI1563
23 tristate "ALI 1563"
Jan Engelhardt16538e62007-05-01 23:26:34 +020024 depends on PCI && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -070025 help
26 If you say yes to this option, support will be included for the SMB
27 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
28 controller is part of the 7101 device, which is an ACPI-compliant
29 Power Management Unit (PMU).
30
31 This driver can also be built as a module. If so, the module
32 will be called i2c-ali1563.
33
34config I2C_ALI15X3
35 tristate "ALI 15x3"
Jan Engelhardt16538e62007-05-01 23:26:34 +020036 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070037 help
38 If you say yes to this option, support will be included for the
39 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
40
41 This driver can also be built as a module. If so, the module
42 will be called i2c-ali15x3.
43
44config I2C_AMD756
45 tristate "AMD 756/766/768/8111 and nVidia nForce"
Jan Engelhardt16538e62007-05-01 23:26:34 +020046 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070047 help
48 If you say yes to this option, support will be included for the AMD
49 756/766/768 mainboard I2C interfaces. The driver also includes
50 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
51 the nVidia nForce I2C interface.
52
53 This driver can also be built as a module. If so, the module
54 will be called i2c-amd756.
55
56config I2C_AMD756_S4882
57 tristate "SMBus multiplexing on the Tyan S4882"
Jean Delvaref1453ee2008-10-14 17:30:06 +020058 depends on I2C_AMD756 && X86 && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -070059 help
60 Enabling this option will add specific SMBus support for the Tyan
61 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
62 over 8 different channels, where the various memory module EEPROMs
63 and temperature sensors live. Saying yes here will give you access
64 to these in addition to the trunk.
65
66 This driver can also be built as a module. If so, the module
67 will be called i2c-amd756-s4882.
68
69config I2C_AMD8111
70 tristate "AMD 8111"
Jan Engelhardt16538e62007-05-01 23:26:34 +020071 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070072 help
73 If you say yes to this option, support will be included for the
74 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
75
76 This driver can also be built as a module. If so, the module
77 will be called i2c-amd8111.
78
Jean Delvaref5b728a2008-07-14 22:38:23 +020079config I2C_I801
80 tristate "Intel 82801 (ICH)"
81 depends on PCI
82 help
83 If you say yes to this option, support will be included for the Intel
84 801 family of mainboard I2C interfaces. Specifically, the following
85 versions of the chipset are supported:
86 82801AA
87 82801AB
88 82801BA
89 82801CA/CAM
90 82801DB
91 82801EB/ER (ICH5/ICH5R)
92 6300ESB
93 ICH6
94 ICH7
95 ESB2
96 ICH8
97 ICH9
98 Tolapai
99 ICH10
Seth Heasleyc429a242008-10-22 20:21:29 +0200100 PCH
Jean Delvaref5b728a2008-07-14 22:38:23 +0200101
102 This driver can also be built as a module. If so, the module
103 will be called i2c-i801.
104
Alek Du5bc12002008-07-14 22:38:27 +0200105config I2C_ISCH
106 tristate "Intel SCH SMBus 1.0"
107 depends on PCI
108 help
109 Say Y here if you want to use SMBus controller on the Intel SCH
110 based systems.
111
112 This driver can also be built as a module. If so, the module
113 will be called i2c-isch.
114
Jean Delvaref5b728a2008-07-14 22:38:23 +0200115config I2C_PIIX4
116 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
117 depends on PCI
118 help
119 If you say yes to this option, support will be included for the Intel
120 PIIX4 family of mainboard I2C interfaces. Specifically, the following
121 versions of the chipset are supported (note that Serverworks is part
122 of Broadcom):
123 Intel PIIX4
124 Intel 440MX
125 ATI IXP200
126 ATI IXP300
127 ATI IXP400
128 ATI SB600
129 ATI SB700
130 ATI SB800
131 Serverworks OSB4
132 Serverworks CSB5
133 Serverworks CSB6
134 Serverworks HT-1000
Flavio Leitner506a8b62009-03-28 21:34:46 +0100135 Serverworks HT-1100
Jean Delvaref5b728a2008-07-14 22:38:23 +0200136 SMSC Victory66
137
138 This driver can also be built as a module. If so, the module
139 will be called i2c-piix4.
140
141config I2C_NFORCE2
142 tristate "Nvidia nForce2, nForce3 and nForce4"
143 depends on PCI
144 help
145 If you say yes to this option, support will be included for the Nvidia
146 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
147
148 This driver can also be built as a module. If so, the module
149 will be called i2c-nforce2.
150
151config I2C_NFORCE2_S4985
152 tristate "SMBus multiplexing on the Tyan S4985"
Jean Delvaref1453ee2008-10-14 17:30:06 +0200153 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
Jean Delvaref5b728a2008-07-14 22:38:23 +0200154 help
155 Enabling this option will add specific SMBus support for the Tyan
156 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
157 over 4 different channels, where the various memory module EEPROMs
158 live. Saying yes here will give you access to these in addition
159 to the trunk.
160
161 This driver can also be built as a module. If so, the module
162 will be called i2c-nforce2-s4985.
163
164config I2C_SIS5595
165 tristate "SiS 5595"
166 depends on PCI
167 help
168 If you say yes to this option, support will be included for the
169 SiS5595 SMBus (a subset of I2C) interface.
170
171 This driver can also be built as a module. If so, the module
172 will be called i2c-sis5595.
173
174config I2C_SIS630
175 tristate "SiS 630/730"
176 depends on PCI
177 help
178 If you say yes to this option, support will be included for the
179 SiS630 and SiS730 SMBus (a subset of I2C) interface.
180
181 This driver can also be built as a module. If so, the module
182 will be called i2c-sis630.
183
184config I2C_SIS96X
185 tristate "SiS 96x"
186 depends on PCI
187 help
188 If you say yes to this option, support will be included for the SiS
189 96x SMBus (a subset of I2C) interfaces. Specifically, the following
190 chipsets are supported:
191 645/961
192 645DX/961
193 645DX/962
194 648/961
195 650/961
196 735
197 745
198
199 This driver can also be built as a module. If so, the module
200 will be called i2c-sis96x.
201
202config I2C_VIA
203 tristate "VIA VT82C586B"
204 depends on PCI && EXPERIMENTAL
205 select I2C_ALGOBIT
206 help
207 If you say yes to this option, support will be included for the VIA
208 82C586B I2C interface
209
210 This driver can also be built as a module. If so, the module
211 will be called i2c-via.
212
213config I2C_VIAPRO
Rudolf Marekb806a712008-10-14 17:30:03 +0200214 tristate "VIA VT82C596/82C686/82xx and CX700/VX800/VX820"
Jean Delvaref5b728a2008-07-14 22:38:23 +0200215 depends on PCI
216 help
217 If you say yes to this option, support will be included for the VIA
218 VT82C596 and later SMBus interface. Specifically, the following
219 chipsets are supported:
220 VT82C596A/B
221 VT82C686A/B
222 VT8231
223 VT8233/A
224 VT8235
225 VT8237R/A/S
226 VT8251
227 CX700
Rudolf Marekb806a712008-10-14 17:30:03 +0200228 VX800
229 VX820
Jean Delvaref5b728a2008-07-14 22:38:23 +0200230
231 This driver can also be built as a module. If so, the module
232 will be called i2c-viapro.
233
234comment "Mac SMBus host controller drivers"
235 depends on PPC_CHRP || PPC_PMAC
236
237config I2C_HYDRA
238 tristate "CHRP Apple Hydra Mac I/O I2C interface"
239 depends on PCI && PPC_CHRP && EXPERIMENTAL
240 select I2C_ALGOBIT
241 help
242 This supports the use of the I2C interface in the Apple Hydra Mac
243 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
244 have such a machine.
245
246 This support is also available as a module. If so, the module
247 will be called i2c-hydra.
248
249config I2C_POWERMAC
250 tristate "Powermac I2C interface"
251 depends on PPC_PMAC
252 default y
253 help
254 This exposes the various PowerMac i2c interfaces to the linux i2c
255 layer and to userland. It is used by various drivers on the PowerMac
256 platform, and should generally be enabled.
257
258 This support is also available as a module. If so, the module
259 will be called i2c-powermac.
260
261comment "I2C system bus drivers (mostly embedded / system-on-chip)"
262
Andrew Victor813e30e2006-12-10 21:21:30 +0100263config I2C_AT91
264 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
David Brownell24d0fb42007-10-13 23:56:32 +0200265 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
Andrew Victor813e30e2006-12-10 21:21:30 +0100266 help
267 This supports the use of the I2C interface on Atmel AT91
268 processors.
269
David Brownell24d0fb42007-10-13 23:56:32 +0200270 This driver is BROKEN because the controller which it uses
271 will easily trigger RX overrun and TX underrun errors. Using
272 low I2C clock rates may partially work around those issues
273 on some systems. Another serious problem is that there is no
274 documented way to issue repeated START conditions, as needed
275 to support combined I2C messages. Use the i2c-gpio driver
276 unless your system can cope with those limitations.
277
Linus Torvalds1da177e2005-04-16 15:20:36 -0700278config I2C_AU1550
Domen Puncera294de42006-08-13 23:37:13 +0200279 tristate "Au1550/Au1200 SMBus interface"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200280 depends on SOC_AU1550 || SOC_AU1200
Linus Torvalds1da177e2005-04-16 15:20:36 -0700281 help
282 If you say yes to this option, support will be included for the
Domen Puncera294de42006-08-13 23:37:13 +0200283 Au1550 and Au1200 SMBus interface.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700284
285 This driver can also be built as a module. If so, the module
286 will be called i2c-au1550.
287
Bryan Wud24ecfc2007-05-01 23:26:32 +0200288config I2C_BLACKFIN_TWI
289 tristate "Blackfin TWI I2C support"
Bryan Wud4ce2202008-04-22 22:16:48 +0200290 depends on BLACKFIN
Mike Frysinger4d2bee52008-07-14 22:38:22 +0200291 depends on !BF561 && !BF531 && !BF532 && !BF533
Bryan Wud24ecfc2007-05-01 23:26:32 +0200292 help
Mike Frysinger4d2bee52008-07-14 22:38:22 +0200293 This is the I2C bus driver for Blackfin on-chip TWI interface.
Bryan Wud4ce2202008-04-22 22:16:48 +0200294
Bryan Wud24ecfc2007-05-01 23:26:32 +0200295 This driver can also be built as a module. If so, the module
296 will be called i2c-bfin-twi.
297
298config I2C_BLACKFIN_TWI_CLK_KHZ
299 int "Blackfin TWI I2C clock (kHz)"
300 depends on I2C_BLACKFIN_TWI
301 range 10 400
302 default 50
303 help
304 The unit of the TWI clock is kHz.
305
Jochen Friedrich61045db2008-07-14 22:38:27 +0200306config I2C_CPM
307 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
308 depends on (CPM1 || CPM2) && OF_I2C
309 help
310 This supports the use of the I2C interface on Freescale
311 processors with CPM1 or CPM2.
312
313 This driver can also be built as a module. If so, the module
314 will be called i2c-cpm.
315
Vladimir Barinov95a7f102007-10-13 23:56:30 +0200316config I2C_DAVINCI
317 tristate "DaVinci I2C driver"
318 depends on ARCH_DAVINCI
319 help
320 Support for TI DaVinci I2C controller driver.
321
322 This driver can also be built as a module. If so, the module
323 will be called i2c-davinci.
324
325 Please note that this driver might be needed to bring up other
326 devices such as DaVinci NIC.
327 For details please see http://www.ti.com/davinci
328
Haavard Skinnemoen1c23af92007-05-01 23:26:34 +0200329config I2C_GPIO
330 tristate "GPIO-based bitbanging I2C"
331 depends on GENERIC_GPIO
332 select I2C_ALGOBIT
333 help
334 This is a very simple bitbanging I2C driver utilizing the
335 arch-neutral GPIO API to control the SCL and SDA lines.
336
Paul Mundt4ad48e62008-10-14 17:30:03 +0200337config I2C_HIGHLANDER
338 tristate "Highlander FPGA SMBus interface"
339 depends on SH_HIGHLANDER
340 help
341 If you say yes to this option, support will be included for
342 the SMBus interface located in the FPGA on various Highlander
343 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
344 FPGAs. This is wholly unrelated to the SoC I2C.
345
346 This driver can also be built as a module. If so, the module
347 will be called i2c-highlander.
348
Linus Torvalds1da177e2005-04-16 15:20:36 -0700349config I2C_IBM_IIC
350 tristate "IBM PPC 4xx on-chip I2C interface"
Sean MacLennan838349b2008-04-22 22:16:47 +0200351 depends on 4xx
Linus Torvalds1da177e2005-04-16 15:20:36 -0700352 help
Wolfram Sang4c03f682008-04-22 22:16:47 +0200353 Say Y here if you want to use IIC peripheral found on
354 embedded IBM PPC 4xx based systems.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700355
356 This driver can also be built as a module. If so, the module
357 will be called i2c-ibm_iic.
358
Darius Augulisaa11e382009-01-30 10:32:28 +0200359config I2C_IMX
360 tristate "IMX I2C interface"
361 depends on ARCH_MXC
362 help
363 Say Y here if you want to use the IIC bus controller on
364 the Freescale i.MX/MXC processors.
365
366 This driver can also be built as a module. If so, the module
367 will be called i2c-imx.
368
Linus Torvalds1da177e2005-04-16 15:20:36 -0700369config I2C_IOP3XX
Dan Williams285f5fa2006-12-07 02:59:39 +0100370 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200371 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700372 help
373 Say Y here if you want to use the IIC bus controller on
Dan Williams285f5fa2006-12-07 02:59:39 +0100374 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700375
376 This driver can also be built as a module. If so, the module
377 will be called i2c-iop3xx.
378
Linus Torvalds1da177e2005-04-16 15:20:36 -0700379config I2C_IXP2000
Jean Delvare11de70b2007-05-01 23:26:34 +0200380 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200381 depends on ARCH_IXP2000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700382 select I2C_ALGOBIT
383 help
Wolfram Sang4c03f682008-04-22 22:16:47 +0200384 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
Linus Torvalds1da177e2005-04-16 15:20:36 -0700385 system and are using GPIO lines for an I2C bus.
386
387 This support is also available as a module. If so, the module
388 will be called i2c-ixp2000.
389
Jean Delvare11de70b2007-05-01 23:26:34 +0200390 This driver is deprecated and will be dropped soon. Use i2c-gpio
391 instead.
392
Linus Torvalds1da177e2005-04-16 15:20:36 -0700393config I2C_MPC
Jon Loeliger2097c7f2006-06-17 17:52:54 -0500394 tristate "MPC107/824x/85xx/52xx/86xx"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200395 depends on PPC32
Linus Torvalds1da177e2005-04-16 15:20:36 -0700396 help
397 If you say yes to this option, support will be included for the
398 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
Jon Loeliger2097c7f2006-06-17 17:52:54 -0500399 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
Linus Torvalds1da177e2005-04-16 15:20:36 -0700400 family processors, though interrupts are known not to work.
401
402 This driver can also be built as a module. If so, the module
403 will be called i2c-mpc.
404
Jean Delvaref5b728a2008-07-14 22:38:23 +0200405config I2C_MV64XXX
406 tristate "Marvell mv64xxx I2C Controller"
407 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700408 help
Jean Delvaref5b728a2008-07-14 22:38:23 +0200409 If you say yes to this option, support will be included for the
410 built-in I2C interface on the Marvell 64xxx line of host bridges.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700411
412 This driver can also be built as a module. If so, the module
Jean Delvaref5b728a2008-07-14 22:38:23 +0200413 will be called i2c-mv64xxx.
Jean Delvare279e9022008-07-14 22:38:21 +0200414
Peter Korsgaard18f98b12006-06-04 20:01:08 +0200415config I2C_OCORES
416 tristate "OpenCores I2C Controller"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200417 depends on EXPERIMENTAL
Peter Korsgaard18f98b12006-06-04 20:01:08 +0200418 help
419 If you say yes to this option, support will be included for the
420 OpenCores I2C controller. For details see
421 http://www.opencores.org/projects.cgi/web/i2c/overview
422
423 This driver can also be built as a module. If so, the module
424 will be called i2c-ocores.
425
Komal Shah010d442c42006-08-13 23:44:09 +0200426config I2C_OMAP
427 tristate "OMAP I2C adapter"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200428 depends on ARCH_OMAP
Komal Shah010d442c42006-08-13 23:44:09 +0200429 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
430 help
431 If you say yes to this option, support will be included for the
432 I2C interface on the Texas Instruments OMAP1/2 family of processors.
433 Like OMAP1510/1610/1710/5912 and OMAP242x.
434 For details see http://www.ti.com/omap.
435
Jean Delvaref5b728a2008-07-14 22:38:23 +0200436config I2C_PASEMI
437 tristate "PA Semi SMBus interface"
438 depends on PPC_PASEMI && PCI
439 help
440 Supports the PA Semi PWRficient on-chip SMBus interfaces.
441
442config I2C_PNX
443 tristate "I2C bus support for Philips PNX targets"
444 depends on ARCH_PNX4008
445 help
446 This driver supports the Philips IP3204 I2C IP block master and/or
447 slave controller
448
449 This driver can also be built as a module. If so, the module
450 will be called i2c-pnx.
451
452config I2C_PXA
453 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
454 depends on EXPERIMENTAL && ARCH_PXA
455 help
456 If you have devices in the PXA I2C bus, say yes to this option.
457 This driver can also be built as a module. If so, the module
458 will be called i2c-pxa.
459
460config I2C_PXA_SLAVE
461 bool "Intel PXA2XX I2C Slave comms support"
462 depends on I2C_PXA
463 help
464 Support I2C slave mode communications on the PXA I2C bus. This
465 is necessary for systems where the PXA may be a target on the
466 I2C bus.
467
468config I2C_S3C2410
469 tristate "S3C2410 I2C Driver"
470 depends on ARCH_S3C2410
471 help
472 Say Y here to include support for I2C controller in the
473 Samsung S3C2410 based System-on-Chip devices.
474
475config I2C_SH7760
476 tristate "Renesas SH7760 I2C Controller"
477 depends on CPU_SUBTYPE_SH7760
478 help
479 This driver supports the 2 I2C interfaces on the Renesas SH7760.
480
481 This driver can also be built as a module. If so, the module
482 will be called i2c-sh7760.
483
484config I2C_SH_MOBILE
485 tristate "SuperH Mobile I2C Controller"
486 depends on SUPERH
487 help
488 If you say yes to this option, support will be included for the
489 built-in I2C interface on the Renesas SH-Mobile processor.
490
491 This driver can also be built as a module. If so, the module
492 will be called i2c-sh_mobile.
493
494config I2C_SIMTEC
495 tristate "Simtec Generic I2C interface"
496 select I2C_ALGOBIT
497 help
498 If you say yes to this option, support will be included for
499 the Simtec Generic I2C interface. This driver is for the
500 simple I2C bus used on newer Simtec products for general
501 I2C, such as DDC on the Simtec BBD2016A.
502
503 This driver can also be built as a module. If so, the module
504 will be called i2c-simtec.
505
506config I2C_VERSATILE
507 tristate "ARM Versatile/Realview I2C bus support"
508 depends on ARCH_VERSATILE || ARCH_REALVIEW
509 select I2C_ALGOBIT
510 help
511 Say yes if you want to support the I2C serial bus on ARMs Versatile
512 range of platforms.
513
514 This driver can also be built as a module. If so, the module
515 will be called i2c-versatile.
516
517comment "External I2C/SMBus adapter drivers"
518
Linus Torvalds1da177e2005-04-16 15:20:36 -0700519config I2C_PARPORT
520 tristate "Parallel port adapter"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200521 depends on PARPORT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700522 select I2C_ALGOBIT
523 help
524 This supports parallel port I2C adapters such as the ones made by
525 Philips or Velleman, Analog Devices evaluation boards, and more.
526 Basically any adapter using the parallel port as an I2C bus with
527 no extra chipset is supported by this driver, or could be.
528
529 This driver is a replacement for (and was inspired by) an older
530 driver named i2c-philips-par. The new driver supports more devices,
531 and makes it easier to add support for new devices.
Mark M. Hoffmane97b81d2006-03-23 16:50:25 +0100532
533 An adapter type parameter is now mandatory. Please read the file
534 Documentation/i2c/busses/i2c-parport for details.
535
Linus Torvalds1da177e2005-04-16 15:20:36 -0700536 Another driver exists, named i2c-parport-light, which doesn't depend
537 on the parport driver. This is meant for embedded systems. Don't say
538 Y here if you intend to say Y or M there.
539
Wolfram Sang4c03f682008-04-22 22:16:47 +0200540 This support is also available as a module. If so, the module
Linus Torvalds1da177e2005-04-16 15:20:36 -0700541 will be called i2c-parport.
542
543config I2C_PARPORT_LIGHT
544 tristate "Parallel port adapter (light)"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700545 select I2C_ALGOBIT
546 help
547 This supports parallel port I2C adapters such as the ones made by
548 Philips or Velleman, Analog Devices evaluation boards, and more.
549 Basically any adapter using the parallel port as an I2C bus with
550 no extra chipset is supported by this driver, or could be.
551
552 This driver is a light version of i2c-parport. It doesn't depend
553 on the parport driver, and uses direct I/O access instead. This
Matt LaPlante09509602006-10-03 22:31:37 +0200554 might be preferred on embedded systems where wasting memory for
Linus Torvalds1da177e2005-04-16 15:20:36 -0700555 the clean but heavy parport handling is not an option. The
556 drawback is a reduced portability and the impossibility to
Matt LaPlante09509602006-10-03 22:31:37 +0200557 daisy-chain other parallel port devices.
Wolfram Sang4c03f682008-04-22 22:16:47 +0200558
Linus Torvalds1da177e2005-04-16 15:20:36 -0700559 Don't say Y here if you said Y or M to i2c-parport. Saying M to
560 both is possible but both modules should not be loaded at the same
561 time.
562
Wolfram Sang4c03f682008-04-22 22:16:47 +0200563 This support is also available as a module. If so, the module
Linus Torvalds1da177e2005-04-16 15:20:36 -0700564 will be called i2c-parport-light.
565
Jean Delvaref5b728a2008-07-14 22:38:23 +0200566config I2C_TAOS_EVM
567 tristate "TAOS evaluation module"
568 depends on EXPERIMENTAL
569 select SERIO
570 select SERIO_SERPORT
571 default n
Olof Johanssonbeb58aa2007-02-13 22:09:03 +0100572 help
Jean Delvaref5b728a2008-07-14 22:38:23 +0200573 This supports TAOS evaluation modules on serial port. In order to
574 use this driver, you will need the inputattach tool, which is part
575 of the input-utils package.
Olof Johanssonbeb58aa2007-02-13 22:09:03 +0100576
Jean Delvaref5b728a2008-07-14 22:38:23 +0200577 If unsure, say N.
578
579 This support is also available as a module. If so, the module
580 will be called i2c-taos-evm.
581
582config I2C_TINY_USB
583 tristate "Tiny-USB adapter"
584 depends on USB
Linus Torvalds1da177e2005-04-16 15:20:36 -0700585 help
Jean Delvaref5b728a2008-07-14 22:38:23 +0200586 If you say yes to this option, support will be included for the
587 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
588 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
589
590 This driver can also be built as a module. If so, the module
591 will be called i2c-tiny-usb.
592
593comment "Graphics adapter I2C/DDC channel drivers"
594 depends on PCI
595
596config I2C_VOODOO3
597 tristate "Voodoo 3"
598 depends on PCI
599 select I2C_ALGOBIT
600 help
601 If you say yes to this option, support will be included for the
602 Voodoo 3 I2C interface.
603
604 This driver can also be built as a module. If so, the module
605 will be called i2c-voodoo3.
606
607comment "Other I2C/SMBus bus drivers"
608
609config I2C_ACORN
610 tristate "Acorn IOC/IOMD I2C bus support"
611 depends on ARCH_ACORN
612 default y
613 select I2C_ALGOBIT
614 help
615 Say yes if you want to support the I2C bus on Acorn platforms.
616
617 If you don't know, say Y.
618
619config I2C_ELEKTOR
620 tristate "Elektor ISA card"
621 depends on ISA && BROKEN_ON_SMP
622 select I2C_ALGOPCF
623 help
624 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
625 such an adapter.
626
627 This support is also available as a module. If so, the module
628 will be called i2c-elektor.
629
630config I2C_PCA_ISA
Marco Aurelio da Costaeff9ec92009-03-28 21:34:44 +0100631 tristate "PCA9564/PCA9665 on an ISA bus"
Jean Delvaref5b728a2008-07-14 22:38:23 +0200632 depends on ISA
633 select I2C_ALGOPCA
634 default n
635 help
Marco Aurelio da Costaeff9ec92009-03-28 21:34:44 +0100636 This driver supports ISA boards using the Philips PCA9564/PCA9665
Jean Delvaref5b728a2008-07-14 22:38:23 +0200637 parallel bus to I2C bus controller.
638
639 This driver can also be built as a module. If so, the module
640 will be called i2c-pca-isa.
641
642 This device is almost undetectable and using this driver on a
643 system which doesn't have this device will result in long
644 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
645 time). If unsure, say N.
646
647config I2C_PCA_PLATFORM
Marco Aurelio da Costaeff9ec92009-03-28 21:34:44 +0100648 tristate "PCA9564/PCA9665 as platform device"
Jean Delvaref5b728a2008-07-14 22:38:23 +0200649 select I2C_ALGOPCA
650 default n
651 help
Marco Aurelio da Costaeff9ec92009-03-28 21:34:44 +0100652 This driver supports a memory mapped Philips PCA9564/PCA9665
Jean Delvaref5b728a2008-07-14 22:38:23 +0200653 parallel bus to I2C bus controller.
654
655 This driver can also be built as a module. If so, the module
656 will be called i2c-pca-platform.
657
658config I2C_PMCMSP
659 tristate "PMC MSP I2C TWI Controller"
660 depends on PMC_MSP
661 help
662 This driver supports the PMC TWI controller on MSP devices.
663
664 This driver can also be built as module. If so, the module
665 will be called i2c-pmcmsp.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700666
Linus Torvalds1da177e2005-04-16 15:20:36 -0700667config I2C_SIBYTE
668 tristate "SiByte SMBus interface"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200669 depends on SIBYTE_SB1xxx_SOC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700670 help
671 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
672
Jean Delvaref5b728a2008-07-14 22:38:23 +0200673config I2C_STUB
674 tristate "I2C/SMBus Test Stub"
675 depends on EXPERIMENTAL && m
676 default 'n'
Ben Dooksbcda9f12007-05-01 23:26:34 +0200677 help
Jean Delvaref5b728a2008-07-14 22:38:23 +0200678 This module may be useful to developers of SMBus client drivers,
679 especially for certain kinds of sensor chips.
Ben Dooksbcda9f12007-05-01 23:26:34 +0200680
Jean Delvaref5b728a2008-07-14 22:38:23 +0200681 If you do build this module, be sure to read the notes and warnings
682 in <file:Documentation/i2c/i2c-stub>.
683
684 If you don't know what to do here, definitely say N.
Ben Dooksbcda9f12007-05-01 23:26:34 +0200685
Linus Torvalds1da177e2005-04-16 15:20:36 -0700686config SCx200_I2C
Jean Delvare11de70b2007-05-01 23:26:34 +0200687 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200688 depends on SCx200_GPIO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700689 select I2C_ALGOBIT
690 help
691 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
692
693 If you don't know what to do here, say N.
694
Wolfram Sang4c03f682008-04-22 22:16:47 +0200695 This support is also available as a module. If so, the module
Linus Torvalds1da177e2005-04-16 15:20:36 -0700696 will be called scx200_i2c.
697
Jean Delvare11de70b2007-05-01 23:26:34 +0200698 This driver is deprecated and will be dropped soon. Use i2c-gpio
699 (or scx200_acb) instead.
700
Linus Torvalds1da177e2005-04-16 15:20:36 -0700701config SCx200_I2C_SCL
702 int "GPIO pin used for SCL"
703 depends on SCx200_I2C
704 default "12"
705 help
706 Enter the GPIO pin number used for the SCL signal. This value can
707 also be specified with a module parameter.
708
709config SCx200_I2C_SDA
710 int "GPIO pin used for SDA"
711 depends on SCx200_I2C
712 default "13"
713 help
714 Enter the GPIO pin number used for the SSA signal. This value can
715 also be specified with a module parameter.
716
717config SCx200_ACB
Ben Gardnera417bbd2006-01-18 22:53:09 +0100718 tristate "Geode ACCESS.bus support"
Jan Engelhardt16538e62007-05-01 23:26:34 +0200719 depends on X86_32 && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700720 help
Ben Gardnera417bbd2006-01-18 22:53:09 +0100721 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
722 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700723
724 If you don't know what to do here, say N.
725
Wolfram Sang4c03f682008-04-22 22:16:47 +0200726 This support is also available as a module. If so, the module
Linus Torvalds1da177e2005-04-16 15:20:36 -0700727 will be called scx200_acb.
728
Linus Torvalds1da177e2005-04-16 15:20:36 -0700729endmenu