Version:  2.0.40 2.2.26 2.4.37 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19

Linux/drivers/i2c/busses/Kconfig

  1 #
  2 # Sensor device configuration
  3 #
  4 
  5 menu "I2C Hardware Bus support"
  6         depends on HAS_IOMEM
  7 
  8 comment "PC SMBus host controller drivers"
  9         depends on PCI
 10 
 11 config I2C_ALI1535
 12         tristate "ALI 1535"
 13         depends on PCI
 14         help
 15           If you say yes to this option, support will be included for the SMB
 16           Host controller on Acer Labs Inc. (ALI) M1535 South Bridges.  The SMB
 17           controller is part of the 7101 device, which is an ACPI-compliant
 18           Power Management Unit (PMU).
 19 
 20           This driver can also be built as a module.  If so, the module
 21           will be called i2c-ali1535.
 22 
 23 config I2C_ALI1563
 24         tristate "ALI 1563"
 25         depends on PCI
 26         help
 27           If you say yes to this option, support will be included for the SMB
 28           Host controller on Acer Labs Inc. (ALI) M1563 South Bridges.  The SMB
 29           controller is part of the 7101 device, which is an ACPI-compliant
 30           Power Management Unit (PMU).
 31 
 32           This driver can also be built as a module.  If so, the module
 33           will be called i2c-ali1563.
 34 
 35 config I2C_ALI15X3
 36         tristate "ALI 15x3"
 37         depends on PCI
 38         help
 39           If you say yes to this option, support will be included for the
 40           Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
 41 
 42           This driver can also be built as a module.  If so, the module
 43           will be called i2c-ali15x3.
 44 
 45 config I2C_AMD756
 46         tristate "AMD 756/766/768/8111 and nVidia nForce"
 47         depends on PCI
 48         help
 49           If you say yes to this option, support will be included for the AMD
 50           756/766/768 mainboard I2C interfaces.  The driver also includes
 51           support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
 52           the nVidia nForce I2C interface.
 53 
 54           This driver can also be built as a module.  If so, the module
 55           will be called i2c-amd756.
 56 
 57 config I2C_AMD756_S4882
 58         tristate "SMBus multiplexing on the Tyan S4882"
 59         depends on I2C_AMD756 && X86
 60         help
 61           Enabling this option will add specific SMBus support for the Tyan
 62           S4882 motherboard.  On this 4-CPU board, the SMBus is multiplexed
 63           over 8 different channels, where the various memory module EEPROMs
 64           and temperature sensors live.  Saying yes here will give you access
 65           to these in addition to the trunk.
 66 
 67           This driver can also be built as a module.  If so, the module
 68           will be called i2c-amd756-s4882.
 69 
 70 config I2C_AMD8111
 71         tristate "AMD 8111"
 72         depends on PCI
 73         help
 74           If you say yes to this option, support will be included for the
 75           second (SMBus 2.0) AMD 8111 mainboard I2C interface.
 76 
 77           This driver can also be built as a module.  If so, the module
 78           will be called i2c-amd8111.
 79 
 80 config I2C_HIX5HD2
 81         tristate "Hix5hd2 high-speed I2C driver"
 82         depends on ARCH_HIX5HD2
 83         help
 84           Say Y here to include support for high-speed I2C controller in the
 85           Hisilicon based hix5hd2 SoCs.
 86 
 87           This driver can also be built as a module.  If so, the module
 88           will be called i2c-hix5hd2.
 89 
 90 config I2C_I801
 91         tristate "Intel 82801 (ICH/PCH)"
 92         depends on PCI
 93         select CHECK_SIGNATURE if X86 && DMI
 94         help
 95           If you say yes to this option, support will be included for the Intel
 96           801 family of mainboard I2C interfaces.  Specifically, the following
 97           versions of the chipset are supported:
 98             82801AA
 99             82801AB
100             82801BA
101             82801CA/CAM
102             82801DB
103             82801EB/ER (ICH5/ICH5R)
104             6300ESB
105             ICH6
106             ICH7
107             ESB2
108             ICH8
109             ICH9
110             EP80579 (Tolapai)
111             ICH10
112             5/3400 Series (PCH)
113             6 Series (PCH)
114             Patsburg (PCH)
115             DH89xxCC (PCH)
116             Panther Point (PCH)
117             Lynx Point (PCH)
118             Lynx Point-LP (PCH)
119             Avoton (SOC)
120             Wellsburg (PCH)
121             Coleto Creek (PCH)
122             Wildcat Point (PCH)
123             Wildcat Point-LP (PCH)
124             BayTrail (SOC)
125             Sunrise Point-H (PCH)
126             Sunrise Point-LP (PCH)
127 
128           This driver can also be built as a module.  If so, the module
129           will be called i2c-i801.
130 
131 config I2C_ISCH
132         tristate "Intel SCH SMBus 1.0"
133         depends on PCI
134         select LPC_SCH
135         help
136           Say Y here if you want to use SMBus controller on the Intel SCH
137           based systems.
138 
139           This driver can also be built as a module. If so, the module
140           will be called i2c-isch.
141 
142 config I2C_ISMT
143         tristate "Intel iSMT SMBus Controller"
144         depends on PCI && X86
145         help
146           If you say yes to this option, support will be included for the Intel
147           iSMT SMBus host controller interface.
148 
149           This driver can also be built as a module.  If so, the module will be
150           called i2c-ismt.
151 
152 config I2C_PIIX4
153         tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
154         depends on PCI
155         help
156           If you say yes to this option, support will be included for the Intel
157           PIIX4 family of mainboard I2C interfaces.  Specifically, the following
158           versions of the chipset are supported (note that Serverworks is part
159           of Broadcom):
160             Intel PIIX4
161             Intel 440MX
162             ATI IXP200
163             ATI IXP300
164             ATI IXP400
165             ATI SB600
166             ATI SB700/SP5100
167             ATI SB800
168             AMD Hudson-2
169             AMD ML
170             AMD CZ
171             Serverworks OSB4
172             Serverworks CSB5
173             Serverworks CSB6
174             Serverworks HT-1000
175             Serverworks HT-1100
176             SMSC Victory66
177 
178           Some AMD chipsets contain two PIIX4-compatible SMBus
179           controllers. This driver will attempt to use both controllers
180           on the SB700/SP5100, if they have been initialized by the BIOS.
181 
182           This driver can also be built as a module.  If so, the module
183           will be called i2c-piix4.
184 
185 config I2C_NFORCE2
186         tristate "Nvidia nForce2, nForce3 and nForce4"
187         depends on PCI
188         help
189           If you say yes to this option, support will be included for the Nvidia
190           nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
191 
192           This driver can also be built as a module.  If so, the module
193           will be called i2c-nforce2.
194 
195 config I2C_NFORCE2_S4985
196         tristate "SMBus multiplexing on the Tyan S4985"
197         depends on I2C_NFORCE2 && X86
198         help
199           Enabling this option will add specific SMBus support for the Tyan
200           S4985 motherboard.  On this 4-CPU board, the SMBus is multiplexed
201           over 4 different channels, where the various memory module EEPROMs
202           live.  Saying yes here will give you access to these in addition
203           to the trunk.
204 
205           This driver can also be built as a module.  If so, the module
206           will be called i2c-nforce2-s4985.
207 
208 config I2C_SIS5595
209         tristate "SiS 5595"
210         depends on PCI
211         help
212           If you say yes to this option, support will be included for the
213           SiS5595 SMBus (a subset of I2C) interface.
214 
215           This driver can also be built as a module.  If so, the module
216           will be called i2c-sis5595.
217 
218 config I2C_SIS630
219         tristate "SiS 630/730/964"
220         depends on PCI
221         help
222           If you say yes to this option, support will be included for the
223           SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
224 
225           This driver can also be built as a module.  If so, the module
226           will be called i2c-sis630.
227 
228 config I2C_SIS96X
229         tristate "SiS 96x"
230         depends on PCI
231         help
232           If you say yes to this option, support will be included for the SiS
233           96x SMBus (a subset of I2C) interfaces.  Specifically, the following
234           chipsets are supported:
235             645/961
236             645DX/961
237             645DX/962
238             648/961
239             650/961
240             735
241             745
242 
243           This driver can also be built as a module.  If so, the module
244           will be called i2c-sis96x.
245 
246 config I2C_VIA
247         tristate "VIA VT82C586B"
248         depends on PCI
249         select I2C_ALGOBIT
250         help
251           If you say yes to this option, support will be included for the VIA
252           82C586B I2C interface
253 
254           This driver can also be built as a module.  If so, the module
255           will be called i2c-via.
256 
257 config I2C_VIAPRO
258         tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
259         depends on PCI
260         help
261           If you say yes to this option, support will be included for the VIA
262           VT82C596 and later SMBus interface.  Specifically, the following
263           chipsets are supported:
264             VT82C596A/B
265             VT82C686A/B
266             VT8231
267             VT8233/A
268             VT8235
269             VT8237R/A/S
270             VT8251
271             CX700
272             VX800/VX820
273             VX855/VX875
274             VX900
275 
276           This driver can also be built as a module.  If so, the module
277           will be called i2c-viapro.
278 
279 if ACPI
280 
281 comment "ACPI drivers"
282 
283 config I2C_SCMI
284         tristate "SMBus Control Method Interface"
285         help
286           This driver supports the SMBus Control Method Interface. It needs the
287           BIOS to declare ACPI control methods as described in the SMBus Control
288           Method Interface specification.
289 
290           To compile this driver as a module, choose M here:
291           the module will be called i2c-scmi.
292 
293 endif # ACPI
294 
295 comment "Mac SMBus host controller drivers"
296         depends on PPC_CHRP || PPC_PMAC
297 
298 config I2C_HYDRA
299         tristate "CHRP Apple Hydra Mac I/O I2C interface"
300         depends on PCI && PPC_CHRP
301         select I2C_ALGOBIT
302         help
303           This supports the use of the I2C interface in the Apple Hydra Mac
304           I/O chip on some CHRP machines (e.g. the LongTrail).  Say Y if you
305           have such a machine.
306 
307           This support is also available as a module.  If so, the module
308           will be called i2c-hydra.
309 
310 config I2C_POWERMAC
311         tristate "Powermac I2C interface"
312         depends on PPC_PMAC
313         default y
314         help
315           This exposes the various PowerMac i2c interfaces to the linux i2c
316           layer and to userland. It is used by various drivers on the PowerMac
317           platform, and should generally be enabled.
318 
319           This support is also available as a module.  If so, the module
320           will be called i2c-powermac.
321 
322 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
323 
324 config I2C_AT91
325         tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
326         depends on ARCH_AT91
327         help
328           This supports the use of the I2C interface on Atmel AT91
329           processors.
330 
331           A serious problem is that there is no documented way to issue
332           repeated START conditions for more than two messages, as needed
333           to support combined I2C messages.  Use the i2c-gpio driver
334           unless your system can cope with this limitation.
335 
336           Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
337           don't have clock stretching in transmission mode. For that reason,
338           you can encounter underrun issues causing premature stop sendings if
339           the latency to fill the transmission register is too long. If you
340           are facing this situation, use the i2c-gpio driver.
341 
342 config I2C_AU1550
343         tristate "Au1550/Au1200/Au1300 SMBus interface"
344         depends on MIPS_ALCHEMY
345         help
346           If you say yes to this option, support will be included for the
347           Au1550/Au1200/Au1300 SMBus interface.
348 
349           This driver can also be built as a module.  If so, the module
350           will be called i2c-au1550.
351 
352 config I2C_AXXIA
353         tristate "Axxia I2C controller"
354         depends on ARCH_AXXIA || COMPILE_TEST
355         default ARCH_AXXIA
356         help
357           Say yes if you want to support the I2C bus on Axxia platforms.
358 
359           Please note that this controller is limited to transfers of maximum
360           255 bytes in length. Any attempt to to a larger transfer will return
361           an error.
362 
363 config I2C_BCM2835
364         tristate "Broadcom BCM2835 I2C controller"
365         depends on ARCH_BCM2835
366         help
367           If you say yes to this option, support will be included for the
368           BCM2835 I2C controller.
369 
370           If you don't know what to do here, say N.
371 
372           This support is also available as a module.  If so, the module
373           will be called i2c-bcm2835.
374 
375 config I2C_BCM_KONA
376         tristate "BCM Kona I2C adapter"
377         depends on ARCH_BCM_MOBILE
378         default y
379         help
380           If you say yes to this option, support will be included for the
381           I2C interface on the Broadcom Kona family of processors.
382 
383           If you do not need KONA I2C interface, say N.
384 
385 config I2C_BLACKFIN_TWI
386         tristate "Blackfin TWI I2C support"
387         depends on BLACKFIN
388         depends on !BF561 && !BF531 && !BF532 && !BF533
389         help
390           This is the I2C bus driver for Blackfin on-chip TWI interface.
391 
392           This driver can also be built as a module.  If so, the module
393           will be called i2c-bfin-twi.
394 
395 config I2C_BLACKFIN_TWI_CLK_KHZ
396         int "Blackfin TWI I2C clock (kHz)"
397         depends on I2C_BLACKFIN_TWI
398         range 21 400
399         default 50
400         help
401           The unit of the TWI clock is kHz.
402 
403 config I2C_CADENCE
404         tristate "Cadence I2C Controller"
405         depends on ARCH_ZYNQ
406         help
407           Say yes here to select Cadence I2C Host Controller. This controller is
408           e.g. used by Xilinx Zynq.
409 
410 config I2C_CBUS_GPIO
411         tristate "CBUS I2C driver"
412         depends on GPIOLIB
413         help
414           Support for CBUS access using I2C API. Mostly relevant for Nokia
415           Internet Tablets (770, N800 and N810).
416 
417           This driver can also be built as a module.  If so, the module
418           will be called i2c-cbus-gpio.
419 
420 config I2C_CPM
421         tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
422         depends on CPM1 || CPM2
423         help
424           This supports the use of the I2C interface on Freescale
425           processors with CPM1 or CPM2.
426 
427           This driver can also be built as a module.  If so, the module
428           will be called i2c-cpm.
429 
430 config I2C_DAVINCI
431         tristate "DaVinci I2C driver"
432         depends on ARCH_DAVINCI || ARCH_KEYSTONE
433         help
434           Support for TI DaVinci I2C controller driver.
435 
436           This driver can also be built as a module.  If so, the module
437           will be called i2c-davinci.
438 
439           Please note that this driver might be needed to bring up other
440           devices such as DaVinci NIC.
441           For details please see http://www.ti.com/davinci
442 
443 config I2C_DESIGNWARE_CORE
444         tristate
445 
446 config I2C_DESIGNWARE_PLATFORM
447         tristate "Synopsys DesignWare Platform"
448         select I2C_DESIGNWARE_CORE
449         depends on (ACPI && COMMON_CLK) || !ACPI
450         help
451           If you say yes to this option, support will be included for the
452           Synopsys DesignWare I2C adapter. Only master mode is supported.
453 
454           This driver can also be built as a module.  If so, the module
455           will be called i2c-designware-platform.
456 
457 config I2C_DESIGNWARE_PCI
458         tristate "Synopsys DesignWare PCI"
459         depends on PCI
460         select I2C_DESIGNWARE_CORE
461         help
462           If you say yes to this option, support will be included for the
463           Synopsys DesignWare I2C adapter. Only master mode is supported.
464 
465           This driver can also be built as a module.  If so, the module
466           will be called i2c-designware-pci.
467 
468 config I2C_EFM32
469         tristate "EFM32 I2C controller"
470         depends on ARCH_EFM32 || COMPILE_TEST
471         help
472           This driver supports the i2c block found in Energy Micro's EFM32
473           SoCs.
474 
475 config I2C_EG20T
476         tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
477         depends on PCI && (X86_32 || COMPILE_TEST)
478         help
479           This driver is for PCH(Platform controller Hub) I2C of EG20T which
480           is an IOH(Input/Output Hub) for x86 embedded processor.
481           This driver can access PCH I2C bus device.
482 
483           This driver also can be used for LAPIS Semiconductor IOH(Input/
484           Output Hub), ML7213, ML7223 and ML7831.
485           ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
486           for MP(Media Phone) use and ML7831 IOH is for general purpose use.
487           ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
488           ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
489 
490 config I2C_EXYNOS5
491         tristate "Exynos5 high-speed I2C driver"
492         depends on ARCH_EXYNOS && OF
493         default y
494         help
495           High-speed I2C controller on Exynos5 based Samsung SoCs.
496 
497 config I2C_GPIO
498         tristate "GPIO-based bitbanging I2C"
499         depends on GPIOLIB
500         select I2C_ALGOBIT
501         help
502           This is a very simple bitbanging I2C driver utilizing the
503           arch-neutral GPIO API to control the SCL and SDA lines.
504 
505 config I2C_HIGHLANDER
506         tristate "Highlander FPGA SMBus interface"
507         depends on SH_HIGHLANDER
508         help
509           If you say yes to this option, support will be included for
510           the SMBus interface located in the FPGA on various Highlander
511           boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
512           FPGAs. This is wholly unrelated to the SoC I2C.
513 
514           This driver can also be built as a module.  If so, the module
515           will be called i2c-highlander.
516 
517 config I2C_IBM_IIC
518         tristate "IBM PPC 4xx on-chip I2C interface"
519         depends on 4xx
520         help
521           Say Y here if you want to use IIC peripheral found on
522           embedded IBM PPC 4xx based systems.
523 
524           This driver can also be built as a module.  If so, the module
525           will be called i2c-ibm_iic.
526 
527 config I2C_IMG
528         tristate "Imagination Technologies I2C SCB Controller"
529         depends on MIPS || METAG || COMPILE_TEST
530         help
531           Say Y here if you want to use the IMG I2C SCB controller,
532           available on the TZ1090 and other IMG SoCs.
533 
534           This driver can also be built as a module.  If so, the module
535           will be called i2c-img-scb.
536 
537 config I2C_IMX
538         tristate "IMX I2C interface"
539         depends on ARCH_MXC
540         help
541           Say Y here if you want to use the IIC bus controller on
542           the Freescale i.MX/MXC processors.
543 
544           This driver can also be built as a module.  If so, the module
545           will be called i2c-imx.
546 
547 config I2C_IOP3XX
548         tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
549         depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
550         help
551           Say Y here if you want to use the IIC bus controller on
552           the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
553 
554           This driver can also be built as a module.  If so, the module
555           will be called i2c-iop3xx.
556 
557 config I2C_KEMPLD
558         tristate "Kontron COM I2C Controller"
559         depends on MFD_KEMPLD
560         help
561           This enables support for the I2C bus interface on some Kontron ETX
562           and COMexpress (ETXexpress) modules.
563 
564           This driver can also be built as a module. If so, the module
565           will be called i2c-kempld.
566 
567 config I2C_MESON
568         tristate "Amlogic Meson I2C controller"
569         depends on ARCH_MESON
570         help
571           If you say yes to this option, support will be included for the
572           I2C interface on the Amlogic Meson family of SoCs.
573 
574 config I2C_MPC
575         tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
576         depends on PPC
577         help
578           If you say yes to this option, support will be included for the
579           built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
580           MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
581 
582           This driver can also be built as a module.  If so, the module
583           will be called i2c-mpc.
584 
585 config I2C_MV64XXX
586         tristate "Marvell mv64xxx I2C Controller"
587         depends on MV64X60 || PLAT_ORION || ARCH_SUNXI
588         help
589           If you say yes to this option, support will be included for the
590           built-in I2C interface on the Marvell 64xxx line of host bridges.
591           This driver is also used for Allwinner SoCs I2C controllers.
592 
593           This driver can also be built as a module.  If so, the module
594           will be called i2c-mv64xxx.
595 
596 config I2C_MXS
597         tristate "Freescale i.MX28 I2C interface"
598         depends on SOC_IMX28
599         select STMP_DEVICE
600         help
601           Say Y here if you want to use the I2C bus controller on
602           the Freescale i.MX28 processors.
603 
604           This driver can also be built as a module.  If so, the module
605           will be called i2c-mxs.
606 
607 config I2C_NOMADIK
608         tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
609         depends on ARM_AMBA
610         help
611           If you say yes to this option, support will be included for the
612           I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
613           as well as the STA2X11 PCIe I/O HUB.
614 
615 config I2C_OCORES
616         tristate "OpenCores I2C Controller"
617         help
618           If you say yes to this option, support will be included for the
619           OpenCores I2C controller. For details see
620           http://www.opencores.org/projects.cgi/web/i2c/overview
621 
622           This driver can also be built as a module.  If so, the module
623           will be called i2c-ocores.
624 
625 config I2C_OMAP
626         tristate "OMAP I2C adapter"
627         depends on ARCH_OMAP
628         default y if MACH_OMAP_H3 || MACH_OMAP_OSK
629         help
630           If you say yes to this option, support will be included for the
631           I2C interface on the Texas Instruments OMAP1/2 family of processors.
632           Like OMAP1510/1610/1710/5912 and OMAP242x.
633           For details see http://www.ti.com/omap.
634 
635 config I2C_PASEMI
636         tristate "PA Semi SMBus interface"
637         depends on PPC_PASEMI && PCI
638         help
639           Supports the PA Semi PWRficient on-chip SMBus interfaces.
640 
641 config I2C_PCA_PLATFORM
642         tristate "PCA9564/PCA9665 as platform device"
643         select I2C_ALGOPCA
644         default n
645         help
646           This driver supports a memory mapped Philips PCA9564/PCA9665
647           parallel bus to I2C bus controller.
648 
649           This driver can also be built as a module.  If so, the module
650           will be called i2c-pca-platform.
651 
652 config I2C_PMCMSP
653         tristate "PMC MSP I2C TWI Controller"
654         depends on PMC_MSP
655         help
656           This driver supports the PMC TWI controller on MSP devices.
657 
658           This driver can also be built as module. If so, the module
659           will be called i2c-pmcmsp.
660 
661 config I2C_PNX
662         tristate "I2C bus support for Philips PNX and NXP LPC targets"
663         depends on ARCH_LPC32XX
664         help
665           This driver supports the Philips IP3204 I2C IP block master and/or
666           slave controller
667 
668           This driver can also be built as a module.  If so, the module
669           will be called i2c-pnx.
670 
671 config I2C_PUV3
672         tristate "PKUnity v3 I2C bus support"
673         depends on UNICORE32 && ARCH_PUV3
674         select I2C_ALGOBIT
675         help
676           This driver supports the I2C IP inside the PKUnity-v3 SoC.
677           This I2C bus controller is under AMBA/AXI bus.
678 
679           This driver can also be built as a module.  If so, the module
680           will be called i2c-puv3.
681 
682 config I2C_PXA
683         tristate "Intel PXA2XX I2C adapter"
684         depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
685         help
686           If you have devices in the PXA I2C bus, say yes to this option.
687           This driver can also be built as a module.  If so, the module
688           will be called i2c-pxa.
689 
690 config I2C_PXA_PCI
691         def_bool I2C_PXA && X86_32 && PCI && OF
692 
693 config I2C_PXA_SLAVE
694         bool "Intel PXA2XX I2C Slave comms support"
695         depends on I2C_PXA && !X86_32
696         help
697           Support I2C slave mode communications on the PXA I2C bus.  This
698           is necessary for systems where the PXA may be a target on the
699           I2C bus.
700 
701 config I2C_QUP
702         tristate "Qualcomm QUP based I2C controller"
703         depends on ARCH_QCOM
704         help
705           If you say yes to this option, support will be included for the
706           built-in I2C interface on the Qualcomm SoCs.
707 
708           This driver can also be built as a module.  If so, the module
709           will be called i2c-qup.
710 
711 config I2C_RIIC
712         tristate "Renesas RIIC adapter"
713         depends on ARCH_SHMOBILE || COMPILE_TEST
714         help
715           If you say yes to this option, support will be included for the
716           Renesas RIIC I2C interface.
717 
718           This driver can also be built as a module.  If so, the module
719           will be called i2c-riic.
720 
721 config I2C_RK3X
722         tristate "Rockchip RK3xxx I2C adapter"
723         depends on OF && COMMON_CLK
724         help
725           Say Y here to include support for the I2C adapter in Rockchip RK3xxx
726           SoCs.
727 
728           This driver can also be built as a module. If so, the module will
729           be called i2c-rk3x.
730 
731 config HAVE_S3C2410_I2C
732         bool
733         help
734           This will include I2C support for Samsung SoCs. If you want to
735           include I2C support for any machine, kindly select this in the
736           respective Kconfig file.
737 
738 config I2C_S3C2410
739         tristate "S3C2410 I2C Driver"
740         depends on HAVE_S3C2410_I2C
741         help
742           Say Y here to include support for I2C controller in the
743           Samsung SoCs.
744 
745 config I2C_SH7760
746         tristate "Renesas SH7760 I2C Controller"
747         depends on CPU_SUBTYPE_SH7760
748         help
749           This driver supports the 2 I2C interfaces on the Renesas SH7760.
750 
751           This driver can also be built as a module.  If so, the module
752           will be called i2c-sh7760.
753 
754 config I2C_SH_MOBILE
755         tristate "SuperH Mobile I2C Controller"
756         depends on HAS_DMA
757         depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
758         help
759           If you say yes to this option, support will be included for the
760           built-in I2C interface on the Renesas SH-Mobile processor.
761 
762           This driver can also be built as a module.  If so, the module
763           will be called i2c-sh_mobile.
764 
765 config I2C_SIMTEC
766         tristate "Simtec Generic I2C interface"
767         select I2C_ALGOBIT
768         help
769           If you say yes to this option, support will be included for
770           the Simtec Generic I2C interface. This driver is for the
771           simple I2C bus used on newer Simtec products for general
772           I2C, such as DDC on the Simtec BBD2016A.
773 
774           This driver can also be built as a module. If so, the module
775           will be called i2c-simtec.
776 
777 config I2C_SIRF
778         tristate "CSR SiRFprimaII I2C interface"
779         depends on ARCH_SIRF
780         help
781           If you say yes to this option, support will be included for the
782           CSR SiRFprimaII I2C interface.
783 
784           This driver can also be built as a module.  If so, the module
785           will be called i2c-sirf.
786 
787 config I2C_ST
788         tristate "STMicroelectronics SSC I2C support"
789         depends on ARCH_STI
790         help
791           Enable this option to add support for STMicroelectronics SoCs
792           hardware SSC (Synchronous Serial Controller) as an I2C controller.
793 
794           This driver can also be built as module. If so, the module
795           will be called i2c-st.
796 
797 config I2C_STU300
798         tristate "ST Microelectronics DDC I2C interface"
799         depends on MACH_U300
800         default y if MACH_U300
801         help
802           If you say yes to this option, support will be included for the
803           I2C interface from ST Microelectronics simply called "DDC I2C"
804           supporting both I2C and DDC, used in e.g. the U300 series
805           mobile platforms.
806 
807           This driver can also be built as a module. If so, the module
808           will be called i2c-stu300.
809 
810 config I2C_SUN6I_P2WI
811         tristate "Allwinner sun6i internal P2WI controller"
812         depends on RESET_CONTROLLER
813         depends on MACH_SUN6I || COMPILE_TEST
814         help
815           If you say yes to this option, support will be included for the
816           P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
817           SOCs.
818           The P2WI looks like an SMBus controller (which supports only byte
819           accesses), except that it only supports one slave device.
820           This interface is used to connect to specific PMIC devices (like the
821           AXP221).
822 
823 config I2C_TEGRA
824         tristate "NVIDIA Tegra internal I2C controller"
825         depends on ARCH_TEGRA
826         help
827           If you say yes to this option, support will be included for the
828           I2C controller embedded in NVIDIA Tegra SOCs
829 
830 config I2C_VERSATILE
831         tristate "ARM Versatile/Realview I2C bus support"
832         depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
833         select I2C_ALGOBIT
834         help
835           Say yes if you want to support the I2C serial bus on ARMs Versatile
836           range of platforms.
837 
838           This driver can also be built as a module.  If so, the module
839           will be called i2c-versatile.
840 
841 config I2C_WMT
842         tristate "Wondermedia WM8xxx SoC I2C bus support"
843         depends on ARCH_VT8500
844         help
845           Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
846           SoCs.
847 
848           This driver can also be built as a module. If so, the module will be
849           called i2c-wmt.
850 
851 config I2C_OCTEON
852         tristate "Cavium OCTEON I2C bus support"
853         depends on CAVIUM_OCTEON_SOC
854         help
855           Say yes if you want to support the I2C serial bus on Cavium
856           OCTEON SOC.
857 
858           This driver can also be built as a module.  If so, the module
859           will be called i2c-octeon.
860 
861 config I2C_XILINX
862         tristate "Xilinx I2C Controller"
863         depends on HAS_IOMEM
864         help
865           If you say yes to this option, support will be included for the
866           Xilinx I2C controller.
867 
868           This driver can also be built as a module.  If so, the module
869           will be called xilinx_i2c.
870 
871 config I2C_XLR
872         tristate "XLR I2C support"
873         depends on CPU_XLR
874         help
875           This driver enables support for the on-chip I2C interface of
876           the Netlogic XLR/XLS MIPS processors.
877 
878           This driver can also be built as a module.  If so, the module
879           will be called i2c-xlr.
880 
881 config I2C_RCAR
882         tristate "Renesas R-Car I2C Controller"
883         depends on ARCH_SHMOBILE || COMPILE_TEST
884         select I2C_SLAVE
885         help
886           If you say yes to this option, support will be included for the
887           R-Car I2C controller.
888 
889           This driver can also be built as a module.  If so, the module
890           will be called i2c-rcar.
891 
892 comment "External I2C/SMBus adapter drivers"
893 
894 config I2C_DIOLAN_U2C
895         tristate "Diolan U2C-12 USB adapter"
896         depends on USB
897         help
898           If you say yes to this option, support will be included for Diolan
899           U2C-12, a USB to I2C interface.
900 
901           This driver can also be built as a module.  If so, the module
902           will be called i2c-diolan-u2c.
903 
904 config I2C_DLN2
905        tristate "Diolan DLN-2 USB I2C adapter"
906        depends on MFD_DLN2
907        help
908          If you say yes to this option, support will be included for Diolan
909          DLN2, a USB to I2C interface.
910 
911          This driver can also be built as a module.  If so, the module
912          will be called i2c-dln2.
913 
914 config I2C_PARPORT
915         tristate "Parallel port adapter"
916         depends on PARPORT
917         select I2C_ALGOBIT
918         select I2C_SMBUS
919         help
920           This supports parallel port I2C adapters such as the ones made by
921           Philips or Velleman, Analog Devices evaluation boards, and more.
922           Basically any adapter using the parallel port as an I2C bus with
923           no extra chipset is supported by this driver, or could be.
924 
925           This driver is a replacement for (and was inspired by) an older
926           driver named i2c-philips-par.  The new driver supports more devices,
927           and makes it easier to add support for new devices.
928 
929           An adapter type parameter is now mandatory.  Please read the file
930           Documentation/i2c/busses/i2c-parport for details.
931 
932           Another driver exists, named i2c-parport-light, which doesn't depend
933           on the parport driver.  This is meant for embedded systems. Don't say
934           Y here if you intend to say Y or M there.
935 
936           This support is also available as a module.  If so, the module
937           will be called i2c-parport.
938 
939 config I2C_PARPORT_LIGHT
940         tristate "Parallel port adapter (light)"
941         select I2C_ALGOBIT
942         select I2C_SMBUS
943         help
944           This supports parallel port I2C adapters such as the ones made by
945           Philips or Velleman, Analog Devices evaluation boards, and more.
946           Basically any adapter using the parallel port as an I2C bus with
947           no extra chipset is supported by this driver, or could be.
948 
949           This driver is a light version of i2c-parport.  It doesn't depend
950           on the parport driver, and uses direct I/O access instead.  This
951           might be preferred on embedded systems where wasting memory for
952           the clean but heavy parport handling is not an option.  The
953           drawback is a reduced portability and the impossibility to
954           daisy-chain other parallel port devices.
955 
956           Don't say Y here if you said Y or M to i2c-parport.  Saying M to
957           both is possible but both modules should not be loaded at the same
958           time.
959 
960           This support is also available as a module.  If so, the module
961           will be called i2c-parport-light.
962 
963 config I2C_ROBOTFUZZ_OSIF
964         tristate "RobotFuzz Open Source InterFace USB adapter"
965         depends on USB
966         help
967           If you say yes to this option, support will be included for the
968           RobotFuzz Open Source InterFace USB to I2C interface.
969 
970           This driver can also be built as a module.  If so, the module
971           will be called i2c-osif.
972 
973 config I2C_TAOS_EVM
974         tristate "TAOS evaluation module"
975         depends on TTY
976         select SERIO
977         select SERIO_SERPORT
978         default n
979         help
980           This supports TAOS evaluation modules on serial port. In order to
981           use this driver, you will need the inputattach tool, which is part
982           of the input-utils package.
983 
984           If unsure, say N.
985 
986           This support is also available as a module.  If so, the module
987           will be called i2c-taos-evm.
988 
989 config I2C_TINY_USB
990         tristate "Tiny-USB adapter"
991         depends on USB
992         help
993           If you say yes to this option, support will be included for the
994           i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
995           http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
996 
997           This driver can also be built as a module.  If so, the module
998           will be called i2c-tiny-usb.
999 
1000 config I2C_VIPERBOARD
1001         tristate "Viperboard I2C master support"
1002         depends on MFD_VIPERBOARD && USB
1003         help
1004           Say yes here to access the I2C part of the Nano River
1005           Technologies Viperboard as I2C master.
1006           See viperboard API specification and Nano
1007           River Tech's viperboard.h for detailed meaning
1008           of the module parameters.
1009 
1010 comment "Other I2C/SMBus bus drivers"
1011 
1012 config I2C_ACORN
1013         tristate "Acorn IOC/IOMD I2C bus support"
1014         depends on ARCH_ACORN
1015         default y
1016         select I2C_ALGOBIT
1017         help
1018           Say yes if you want to support the I2C bus on Acorn platforms.
1019 
1020           If you don't know, say Y.
1021 
1022 config I2C_ELEKTOR
1023         tristate "Elektor ISA card"
1024         depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1025         select I2C_ALGOPCF
1026         help
1027           This supports the PCF8584 ISA bus I2C adapter.  Say Y if you own
1028           such an adapter.
1029 
1030           This support is also available as a module.  If so, the module
1031           will be called i2c-elektor.
1032 
1033 config I2C_PCA_ISA
1034         tristate "PCA9564/PCA9665 on an ISA bus"
1035         depends on ISA
1036         select I2C_ALGOPCA
1037         default n
1038         help
1039           This driver supports ISA boards using the Philips PCA9564/PCA9665
1040           parallel bus to I2C bus controller.
1041 
1042           This driver can also be built as a module.  If so, the module
1043           will be called i2c-pca-isa.
1044 
1045           This device is almost undetectable and using this driver on a
1046           system which doesn't have this device will result in long
1047           delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1048           time).  If unsure, say N.
1049 
1050 config I2C_SIBYTE
1051         tristate "SiByte SMBus interface"
1052         depends on SIBYTE_SB1xxx_SOC
1053         help
1054           Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1055 
1056 config I2C_CROS_EC_TUNNEL
1057         tristate "ChromeOS EC tunnel I2C bus"
1058         depends on MFD_CROS_EC
1059         help
1060           If you say yes here you get an I2C bus that will tunnel i2c commands
1061           through to the other side of the ChromeOS EC to the i2c bus
1062           connected there. This will work whatever the interface used to
1063           talk to the EC (SPI, I2C or LPC).
1064 
1065 config SCx200_ACB
1066         tristate "Geode ACCESS.bus support"
1067         depends on X86_32 && PCI
1068         help
1069           Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1070           SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1071 
1072           If you don't know what to do here, say N.
1073 
1074           This support is also available as a module.  If so, the module
1075           will be called scx200_acb.
1076 
1077 config I2C_OPAL
1078         tristate "IBM OPAL I2C driver"
1079         depends on PPC_POWERNV
1080         default y
1081         help
1082           This exposes the PowerNV platform i2c busses to the linux i2c layer,
1083           the driver is based on the OPAL interfaces.
1084 
1085           This driver can also be built as a module. If so, the module will be
1086           called as i2c-opal.
1087 
1088 endmenu

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us