tjh.dev
Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
1#
2# Sensor device configuration
3#
4
5menu "I2C Hardware Bus support"
6
7comment "PC SMBus host controller drivers"
8 depends on PCI
9
10config I2C_ALI1535
11 tristate "ALI 1535"
12 depends on PCI
13 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"
24 depends on PCI && EXPERIMENTAL
25 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"
36 depends on PCI
37 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"
46 depends on PCI
47 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"
58 depends on I2C_AMD756 && X86 && EXPERIMENTAL
59 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"
71 depends on PCI
72 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
79config I2C_I801
80 tristate "Intel 82801 (ICH/PCH)"
81 depends on PCI
82 select CHECK_SIGNATURE if X86 && DMI
83 help
84 If you say yes to this option, support will be included for the Intel
85 801 family of mainboard I2C interfaces. Specifically, the following
86 versions of the chipset are supported:
87 82801AA
88 82801AB
89 82801BA
90 82801CA/CAM
91 82801DB
92 82801EB/ER (ICH5/ICH5R)
93 6300ESB
94 ICH6
95 ICH7
96 ESB2
97 ICH8
98 ICH9
99 EP80579 (Tolapai)
100 ICH10
101 5/3400 Series (PCH)
102 6 Series (PCH)
103 Patsburg (PCH)
104 DH89xxCC (PCH)
105 Panther Point (PCH)
106
107 This driver can also be built as a module. If so, the module
108 will be called i2c-i801.
109
110config I2C_ISCH
111 tristate "Intel SCH SMBus 1.0"
112 depends on PCI
113 select MFD_CORE
114 select LPC_SCH
115 help
116 Say Y here if you want to use SMBus controller on the Intel SCH
117 based systems.
118
119 This driver can also be built as a module. If so, the module
120 will be called i2c-isch.
121
122config I2C_PIIX4
123 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
124 depends on PCI
125 help
126 If you say yes to this option, support will be included for the Intel
127 PIIX4 family of mainboard I2C interfaces. Specifically, the following
128 versions of the chipset are supported (note that Serverworks is part
129 of Broadcom):
130 Intel PIIX4
131 Intel 440MX
132 ATI IXP200
133 ATI IXP300
134 ATI IXP400
135 ATI SB600
136 ATI SB700
137 ATI SB800
138 AMD Hudson-2
139 Serverworks OSB4
140 Serverworks CSB5
141 Serverworks CSB6
142 Serverworks HT-1000
143 Serverworks HT-1100
144 SMSC Victory66
145
146 This driver can also be built as a module. If so, the module
147 will be called i2c-piix4.
148
149config I2C_NFORCE2
150 tristate "Nvidia nForce2, nForce3 and nForce4"
151 depends on PCI
152 help
153 If you say yes to this option, support will be included for the Nvidia
154 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
155
156 This driver can also be built as a module. If so, the module
157 will be called i2c-nforce2.
158
159config I2C_NFORCE2_S4985
160 tristate "SMBus multiplexing on the Tyan S4985"
161 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
162 help
163 Enabling this option will add specific SMBus support for the Tyan
164 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
165 over 4 different channels, where the various memory module EEPROMs
166 live. Saying yes here will give you access to these in addition
167 to the trunk.
168
169 This driver can also be built as a module. If so, the module
170 will be called i2c-nforce2-s4985.
171
172config I2C_SIS5595
173 tristate "SiS 5595"
174 depends on PCI
175 help
176 If you say yes to this option, support will be included for the
177 SiS5595 SMBus (a subset of I2C) interface.
178
179 This driver can also be built as a module. If so, the module
180 will be called i2c-sis5595.
181
182config I2C_SIS630
183 tristate "SiS 630/730"
184 depends on PCI
185 help
186 If you say yes to this option, support will be included for the
187 SiS630 and SiS730 SMBus (a subset of I2C) interface.
188
189 This driver can also be built as a module. If so, the module
190 will be called i2c-sis630.
191
192config I2C_SIS96X
193 tristate "SiS 96x"
194 depends on PCI
195 help
196 If you say yes to this option, support will be included for the SiS
197 96x SMBus (a subset of I2C) interfaces. Specifically, the following
198 chipsets are supported:
199 645/961
200 645DX/961
201 645DX/962
202 648/961
203 650/961
204 735
205 745
206
207 This driver can also be built as a module. If so, the module
208 will be called i2c-sis96x.
209
210config I2C_VIA
211 tristate "VIA VT82C586B"
212 depends on PCI && EXPERIMENTAL
213 select I2C_ALGOBIT
214 help
215 If you say yes to this option, support will be included for the VIA
216 82C586B I2C interface
217
218 This driver can also be built as a module. If so, the module
219 will be called i2c-via.
220
221config I2C_VIAPRO
222 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
223 depends on PCI
224 help
225 If you say yes to this option, support will be included for the VIA
226 VT82C596 and later SMBus interface. Specifically, the following
227 chipsets are supported:
228 VT82C596A/B
229 VT82C686A/B
230 VT8231
231 VT8233/A
232 VT8235
233 VT8237R/A/S
234 VT8251
235 CX700
236 VX800/VX820
237 VX855/VX875
238
239 This driver can also be built as a module. If so, the module
240 will be called i2c-viapro.
241
242if ACPI
243
244comment "ACPI drivers"
245
246config I2C_SCMI
247 tristate "SMBus Control Method Interface"
248 help
249 This driver supports the SMBus Control Method Interface. It needs the
250 BIOS to declare ACPI control methods as described in the SMBus Control
251 Method Interface specification.
252
253 To compile this driver as a module, choose M here:
254 the module will be called i2c-scmi.
255
256endif # ACPI
257
258comment "Mac SMBus host controller drivers"
259 depends on PPC_CHRP || PPC_PMAC
260
261config I2C_HYDRA
262 tristate "CHRP Apple Hydra Mac I/O I2C interface"
263 depends on PCI && PPC_CHRP && EXPERIMENTAL
264 select I2C_ALGOBIT
265 help
266 This supports the use of the I2C interface in the Apple Hydra Mac
267 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
268 have such a machine.
269
270 This support is also available as a module. If so, the module
271 will be called i2c-hydra.
272
273config I2C_POWERMAC
274 tristate "Powermac I2C interface"
275 depends on PPC_PMAC
276 default y
277 help
278 This exposes the various PowerMac i2c interfaces to the linux i2c
279 layer and to userland. It is used by various drivers on the PowerMac
280 platform, and should generally be enabled.
281
282 This support is also available as a module. If so, the module
283 will be called i2c-powermac.
284
285comment "I2C system bus drivers (mostly embedded / system-on-chip)"
286
287config I2C_AT91
288 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
289 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
290 help
291 This supports the use of the I2C interface on Atmel AT91
292 processors.
293
294 This driver is BROKEN because the controller which it uses
295 will easily trigger RX overrun and TX underrun errors. Using
296 low I2C clock rates may partially work around those issues
297 on some systems. Another serious problem is that there is no
298 documented way to issue repeated START conditions, as needed
299 to support combined I2C messages. Use the i2c-gpio driver
300 unless your system can cope with those limitations.
301
302config I2C_AU1550
303 tristate "Au1550/Au1200 SMBus interface"
304 depends on SOC_AU1550 || SOC_AU1200
305 help
306 If you say yes to this option, support will be included for the
307 Au1550 and Au1200 SMBus interface.
308
309 This driver can also be built as a module. If so, the module
310 will be called i2c-au1550.
311
312config I2C_BLACKFIN_TWI
313 tristate "Blackfin TWI I2C support"
314 depends on BLACKFIN
315 depends on !BF561 && !BF531 && !BF532 && !BF533
316 help
317 This is the I2C bus driver for Blackfin on-chip TWI interface.
318
319 This driver can also be built as a module. If so, the module
320 will be called i2c-bfin-twi.
321
322config I2C_BLACKFIN_TWI_CLK_KHZ
323 int "Blackfin TWI I2C clock (kHz)"
324 depends on I2C_BLACKFIN_TWI
325 range 21 400
326 default 50
327 help
328 The unit of the TWI clock is kHz.
329
330config I2C_CPM
331 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
332 depends on (CPM1 || CPM2) && OF_I2C
333 help
334 This supports the use of the I2C interface on Freescale
335 processors with CPM1 or CPM2.
336
337 This driver can also be built as a module. If so, the module
338 will be called i2c-cpm.
339
340config I2C_DAVINCI
341 tristate "DaVinci I2C driver"
342 depends on ARCH_DAVINCI
343 help
344 Support for TI DaVinci I2C controller driver.
345
346 This driver can also be built as a module. If so, the module
347 will be called i2c-davinci.
348
349 Please note that this driver might be needed to bring up other
350 devices such as DaVinci NIC.
351 For details please see http://www.ti.com/davinci
352
353config I2C_DESIGNWARE
354 tristate "Synopsys DesignWare"
355 depends on HAVE_CLK
356 help
357 If you say yes to this option, support will be included for the
358 Synopsys DesignWare I2C adapter. Only master mode is supported.
359
360 This driver can also be built as a module. If so, the module
361 will be called i2c-designware.
362
363config I2C_GPIO
364 tristate "GPIO-based bitbanging I2C"
365 depends on GENERIC_GPIO
366 select I2C_ALGOBIT
367 help
368 This is a very simple bitbanging I2C driver utilizing the
369 arch-neutral GPIO API to control the SCL and SDA lines.
370
371config I2C_HIGHLANDER
372 tristate "Highlander FPGA SMBus interface"
373 depends on SH_HIGHLANDER
374 help
375 If you say yes to this option, support will be included for
376 the SMBus interface located in the FPGA on various Highlander
377 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
378 FPGAs. This is wholly unrelated to the SoC I2C.
379
380 This driver can also be built as a module. If so, the module
381 will be called i2c-highlander.
382
383config I2C_IBM_IIC
384 tristate "IBM PPC 4xx on-chip I2C interface"
385 depends on 4xx
386 help
387 Say Y here if you want to use IIC peripheral found on
388 embedded IBM PPC 4xx based systems.
389
390 This driver can also be built as a module. If so, the module
391 will be called i2c-ibm_iic.
392
393config I2C_IMX
394 tristate "IMX I2C interface"
395 depends on ARCH_MXC
396 help
397 Say Y here if you want to use the IIC bus controller on
398 the Freescale i.MX/MXC processors.
399
400 This driver can also be built as a module. If so, the module
401 will be called i2c-imx.
402
403config I2C_INTEL_MID
404 tristate "Intel Moorestown/Medfield Platform I2C controller"
405 depends on PCI
406 help
407 Say Y here if you have an Intel Moorestown/Medfield platform I2C
408 controller.
409
410 This support is also available as a module. If so, the module
411 will be called i2c-intel-mid.
412
413config I2C_IOP3XX
414 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
415 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
416 help
417 Say Y here if you want to use the IIC bus controller on
418 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
419
420 This driver can also be built as a module. If so, the module
421 will be called i2c-iop3xx.
422
423config I2C_IXP2000
424 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
425 depends on ARCH_IXP2000
426 select I2C_ALGOBIT
427 help
428 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
429 system and are using GPIO lines for an I2C bus.
430
431 This support is also available as a module. If so, the module
432 will be called i2c-ixp2000.
433
434 This driver is deprecated and will be dropped soon. Use i2c-gpio
435 instead.
436
437config I2C_MPC
438 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
439 depends on PPC
440 help
441 If you say yes to this option, support will be included for the
442 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
443 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
444
445 This driver can also be built as a module. If so, the module
446 will be called i2c-mpc.
447
448config I2C_MV64XXX
449 tristate "Marvell mv64xxx I2C Controller"
450 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
451 help
452 If you say yes to this option, support will be included for the
453 built-in I2C interface on the Marvell 64xxx line of host bridges.
454
455 This driver can also be built as a module. If so, the module
456 will be called i2c-mv64xxx.
457
458config I2C_MXS
459 tristate "Freescale i.MX28 I2C interface"
460 depends on SOC_IMX28
461 help
462 Say Y here if you want to use the I2C bus controller on
463 the Freescale i.MX28 processors.
464
465 This driver can also be built as a module. If so, the module
466 will be called i2c-mxs.
467
468config I2C_NOMADIK
469 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
470 depends on PLAT_NOMADIK
471 help
472 If you say yes to this option, support will be included for the
473 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
474
475config I2C_NUC900
476 tristate "NUC900 I2C Driver"
477 depends on ARCH_W90X900
478 help
479 Say Y here to include support for I2C controller in the
480 Winbond/Nuvoton NUC900 based System-on-Chip devices.
481
482config I2C_OCORES
483 tristate "OpenCores I2C Controller"
484 depends on EXPERIMENTAL
485 help
486 If you say yes to this option, support will be included for the
487 OpenCores I2C controller. For details see
488 http://www.opencores.org/projects.cgi/web/i2c/overview
489
490 This driver can also be built as a module. If so, the module
491 will be called i2c-ocores.
492
493config I2C_OMAP
494 tristate "OMAP I2C adapter"
495 depends on ARCH_OMAP
496 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
497 help
498 If you say yes to this option, support will be included for the
499 I2C interface on the Texas Instruments OMAP1/2 family of processors.
500 Like OMAP1510/1610/1710/5912 and OMAP242x.
501 For details see http://www.ti.com/omap.
502
503config I2C_PASEMI
504 tristate "PA Semi SMBus interface"
505 depends on PPC_PASEMI && PCI
506 help
507 Supports the PA Semi PWRficient on-chip SMBus interfaces.
508
509config I2C_PCA_PLATFORM
510 tristate "PCA9564/PCA9665 as platform device"
511 select I2C_ALGOPCA
512 default n
513 help
514 This driver supports a memory mapped Philips PCA9564/PCA9665
515 parallel bus to I2C bus controller.
516
517 This driver can also be built as a module. If so, the module
518 will be called i2c-pca-platform.
519
520config I2C_PMCMSP
521 tristate "PMC MSP I2C TWI Controller"
522 depends on PMC_MSP
523 help
524 This driver supports the PMC TWI controller on MSP devices.
525
526 This driver can also be built as module. If so, the module
527 will be called i2c-pmcmsp.
528
529config I2C_PNX
530 tristate "I2C bus support for Philips PNX and NXP LPC targets"
531 depends on ARCH_PNX4008 || ARCH_LPC32XX
532 help
533 This driver supports the Philips IP3204 I2C IP block master and/or
534 slave controller
535
536 This driver can also be built as a module. If so, the module
537 will be called i2c-pnx.
538
539config I2C_PUV3
540 tristate "PKUnity v3 I2C bus support"
541 depends on UNICORE32 && ARCH_PUV3
542 select I2C_ALGOBIT
543 help
544 This driver supports the I2C IP inside the PKUnity-v3 SoC.
545 This I2C bus controller is under AMBA/AXI bus.
546
547 This driver can also be built as a module. If so, the module
548 will be called i2c-puv3.
549
550config I2C_PXA
551 tristate "Intel PXA2XX I2C adapter"
552 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
553 help
554 If you have devices in the PXA I2C bus, say yes to this option.
555 This driver can also be built as a module. If so, the module
556 will be called i2c-pxa.
557
558config I2C_PXA_PCI
559 def_bool I2C_PXA && X86_32 && PCI && OF
560
561config I2C_PXA_SLAVE
562 bool "Intel PXA2XX I2C Slave comms support"
563 depends on I2C_PXA && !X86_32
564 help
565 Support I2C slave mode communications on the PXA I2C bus. This
566 is necessary for systems where the PXA may be a target on the
567 I2C bus.
568
569config HAVE_S3C2410_I2C
570 bool
571 help
572 This will include I2C support for Samsung SoCs. If you want to
573 include I2C support for any machine, kindly select this in the
574 respective Kconfig file.
575
576config I2C_S3C2410
577 tristate "S3C2410 I2C Driver"
578 depends on HAVE_S3C2410_I2C
579 help
580 Say Y here to include support for I2C controller in the
581 Samsung SoCs.
582
583config I2C_S6000
584 tristate "S6000 I2C support"
585 depends on XTENSA_VARIANT_S6000
586 help
587 This driver supports the on chip I2C device on the
588 S6000 xtensa processor family.
589
590 To compile this driver as a module, choose M here. The module
591 will be called i2c-s6000.
592
593config I2C_SH7760
594 tristate "Renesas SH7760 I2C Controller"
595 depends on CPU_SUBTYPE_SH7760
596 help
597 This driver supports the 2 I2C interfaces on the Renesas SH7760.
598
599 This driver can also be built as a module. If so, the module
600 will be called i2c-sh7760.
601
602config I2C_SH_MOBILE
603 tristate "SuperH Mobile I2C Controller"
604 depends on SUPERH || ARCH_SHMOBILE
605 help
606 If you say yes to this option, support will be included for the
607 built-in I2C interface on the Renesas SH-Mobile processor.
608
609 This driver can also be built as a module. If so, the module
610 will be called i2c-sh_mobile.
611
612config I2C_SIMTEC
613 tristate "Simtec Generic I2C interface"
614 select I2C_ALGOBIT
615 help
616 If you say yes to this option, support will be included for
617 the Simtec Generic I2C interface. This driver is for the
618 simple I2C bus used on newer Simtec products for general
619 I2C, such as DDC on the Simtec BBD2016A.
620
621 This driver can also be built as a module. If so, the module
622 will be called i2c-simtec.
623
624config I2C_STU300
625 tristate "ST Microelectronics DDC I2C interface"
626 depends on MACH_U300
627 default y if MACH_U300
628 help
629 If you say yes to this option, support will be included for the
630 I2C interface from ST Microelectronics simply called "DDC I2C"
631 supporting both I2C and DDC, used in e.g. the U300 series
632 mobile platforms.
633
634 This driver can also be built as a module. If so, the module
635 will be called i2c-stu300.
636
637config I2C_TEGRA
638 tristate "NVIDIA Tegra internal I2C controller"
639 depends on ARCH_TEGRA
640 help
641 If you say yes to this option, support will be included for the
642 I2C controller embedded in NVIDIA Tegra SOCs
643
644config I2C_VERSATILE
645 tristate "ARM Versatile/Realview I2C bus support"
646 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
647 select I2C_ALGOBIT
648 help
649 Say yes if you want to support the I2C serial bus on ARMs Versatile
650 range of platforms.
651
652 This driver can also be built as a module. If so, the module
653 will be called i2c-versatile.
654
655config I2C_OCTEON
656 tristate "Cavium OCTEON I2C bus support"
657 depends on CPU_CAVIUM_OCTEON
658 help
659 Say yes if you want to support the I2C serial bus on Cavium
660 OCTEON SOC.
661
662 This driver can also be built as a module. If so, the module
663 will be called i2c-octeon.
664
665config I2C_XILINX
666 tristate "Xilinx I2C Controller"
667 depends on EXPERIMENTAL && HAS_IOMEM
668 help
669 If you say yes to this option, support will be included for the
670 Xilinx I2C controller.
671
672 This driver can also be built as a module. If so, the module
673 will be called xilinx_i2c.
674
675config I2C_EG20T
676 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
677 depends on PCI
678 help
679 This driver is for PCH(Platform controller Hub) I2C of EG20T which
680 is an IOH(Input/Output Hub) for x86 embedded processor.
681 This driver can access PCH I2C bus device.
682
683 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
684 Output Hub), ML7213 and ML7223.
685 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
686 for MP(Media Phone) use.
687 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
688 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
689
690comment "External I2C/SMBus adapter drivers"
691
692config I2C_DIOLAN_U2C
693 tristate "Diolan U2C-12 USB adapter"
694 depends on USB
695 help
696 If you say yes to this option, support will be included for Diolan
697 U2C-12, a USB to I2C interface.
698
699 This driver can also be built as a module. If so, the module
700 will be called i2c-diolan-u2c.
701
702config I2C_PARPORT
703 tristate "Parallel port adapter"
704 depends on PARPORT
705 select I2C_ALGOBIT
706 select I2C_SMBUS
707 help
708 This supports parallel port I2C adapters such as the ones made by
709 Philips or Velleman, Analog Devices evaluation boards, and more.
710 Basically any adapter using the parallel port as an I2C bus with
711 no extra chipset is supported by this driver, or could be.
712
713 This driver is a replacement for (and was inspired by) an older
714 driver named i2c-philips-par. The new driver supports more devices,
715 and makes it easier to add support for new devices.
716
717 An adapter type parameter is now mandatory. Please read the file
718 Documentation/i2c/busses/i2c-parport for details.
719
720 Another driver exists, named i2c-parport-light, which doesn't depend
721 on the parport driver. This is meant for embedded systems. Don't say
722 Y here if you intend to say Y or M there.
723
724 This support is also available as a module. If so, the module
725 will be called i2c-parport.
726
727config I2C_PARPORT_LIGHT
728 tristate "Parallel port adapter (light)"
729 select I2C_ALGOBIT
730 select I2C_SMBUS
731 help
732 This supports parallel port I2C adapters such as the ones made by
733 Philips or Velleman, Analog Devices evaluation boards, and more.
734 Basically any adapter using the parallel port as an I2C bus with
735 no extra chipset is supported by this driver, or could be.
736
737 This driver is a light version of i2c-parport. It doesn't depend
738 on the parport driver, and uses direct I/O access instead. This
739 might be preferred on embedded systems where wasting memory for
740 the clean but heavy parport handling is not an option. The
741 drawback is a reduced portability and the impossibility to
742 daisy-chain other parallel port devices.
743
744 Don't say Y here if you said Y or M to i2c-parport. Saying M to
745 both is possible but both modules should not be loaded at the same
746 time.
747
748 This support is also available as a module. If so, the module
749 will be called i2c-parport-light.
750
751config I2C_TAOS_EVM
752 tristate "TAOS evaluation module"
753 depends on EXPERIMENTAL
754 select SERIO
755 select SERIO_SERPORT
756 default n
757 help
758 This supports TAOS evaluation modules on serial port. In order to
759 use this driver, you will need the inputattach tool, which is part
760 of the input-utils package.
761
762 If unsure, say N.
763
764 This support is also available as a module. If so, the module
765 will be called i2c-taos-evm.
766
767config I2C_TINY_USB
768 tristate "Tiny-USB adapter"
769 depends on USB
770 help
771 If you say yes to this option, support will be included for the
772 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
773 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
774
775 This driver can also be built as a module. If so, the module
776 will be called i2c-tiny-usb.
777
778comment "Other I2C/SMBus bus drivers"
779
780config I2C_ACORN
781 tristate "Acorn IOC/IOMD I2C bus support"
782 depends on ARCH_ACORN
783 default y
784 select I2C_ALGOBIT
785 help
786 Say yes if you want to support the I2C bus on Acorn platforms.
787
788 If you don't know, say Y.
789
790config I2C_ELEKTOR
791 tristate "Elektor ISA card"
792 depends on ISA && BROKEN_ON_SMP
793 select I2C_ALGOPCF
794 help
795 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
796 such an adapter.
797
798 This support is also available as a module. If so, the module
799 will be called i2c-elektor.
800
801config I2C_PCA_ISA
802 tristate "PCA9564/PCA9665 on an ISA bus"
803 depends on ISA
804 select I2C_ALGOPCA
805 default n
806 help
807 This driver supports ISA boards using the Philips PCA9564/PCA9665
808 parallel bus to I2C bus controller.
809
810 This driver can also be built as a module. If so, the module
811 will be called i2c-pca-isa.
812
813 This device is almost undetectable and using this driver on a
814 system which doesn't have this device will result in long
815 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
816 time). If unsure, say N.
817
818config I2C_SIBYTE
819 tristate "SiByte SMBus interface"
820 depends on SIBYTE_SB1xxx_SOC
821 help
822 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
823
824config I2C_STUB
825 tristate "I2C/SMBus Test Stub"
826 depends on EXPERIMENTAL && m
827 default 'n'
828 help
829 This module may be useful to developers of SMBus client drivers,
830 especially for certain kinds of sensor chips.
831
832 If you do build this module, be sure to read the notes and warnings
833 in <file:Documentation/i2c/i2c-stub>.
834
835 If you don't know what to do here, definitely say N.
836
837config SCx200_I2C
838 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
839 depends on SCx200_GPIO
840 select I2C_ALGOBIT
841 help
842 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
843
844 If you don't know what to do here, say N.
845
846 This support is also available as a module. If so, the module
847 will be called scx200_i2c.
848
849 This driver is deprecated and will be dropped soon. Use i2c-gpio
850 (or scx200_acb) instead.
851
852config SCx200_I2C_SCL
853 int "GPIO pin used for SCL"
854 depends on SCx200_I2C
855 default "12"
856 help
857 Enter the GPIO pin number used for the SCL signal. This value can
858 also be specified with a module parameter.
859
860config SCx200_I2C_SDA
861 int "GPIO pin used for SDA"
862 depends on SCx200_I2C
863 default "13"
864 help
865 Enter the GPIO pin number used for the SSA signal. This value can
866 also be specified with a module parameter.
867
868config SCx200_ACB
869 tristate "Geode ACCESS.bus support"
870 depends on X86_32 && PCI
871 help
872 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
873 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
874
875 If you don't know what to do here, say N.
876
877 This support is also available as a module. If so, the module
878 will be called scx200_acb.
879
880endmenu