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