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_INTEL_MID
 480         tristate "Intel Moorestown/Medfield Platform I2C controller"
 481         depends on PCI
 482         help
 483           Say Y here if you have an Intel Moorestown/Medfield platform I2C
 484           controller.
 485
 486           This support is also available as a module. If so, the module
 487           will be called i2c-intel-mid.
 488
 489 config I2C_IOP3XX
 490         tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
 491         depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
 492         help
 493           Say Y here if you want to use the IIC bus controller on
 494           the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
 495
 496           This driver can also be built as a module.  If so, the module
 497           will be called i2c-iop3xx.
 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)
 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
 517           This driver can also be built as a module.  If so, the module
 518           will be called i2c-mv64xxx.
 519
 520 config I2C_MXS
 521         tristate "Freescale i.MX28 I2C interface"
 522         depends on SOC_IMX28
 523         select STMP_DEVICE
 524         help
 525           Say Y here if you want to use the I2C bus controller on
 526           the Freescale i.MX28 processors.
 527
 528           This driver can also be built as a module.  If so, the module
 529           will be called i2c-mxs.
 530
 531 config I2C_NOMADIK
 532         tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
 533         depends on ARM_AMBA
 534         help
 535           If you say yes to this option, support will be included for the
 536           I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
 537           as well as the STA2X11 PCIe I/O HUB.
 538
 539 config I2C_NUC900
 540         tristate "NUC900 I2C Driver"
 541         depends on ARCH_W90X900
 542         help
 543           Say Y here to include support for I2C controller in the
 544           Winbond/Nuvoton NUC900 based System-on-Chip devices.
 545
 546 config I2C_OCORES
 547         tristate "OpenCores I2C Controller"
 548         depends on GENERIC_HARDIRQS
 549         help
 550           If you say yes to this option, support will be included for the
 551           OpenCores I2C controller. For details see
 552           http://www.opencores.org/projects.cgi/web/i2c/overview
 553
 554           This driver can also be built as a module.  If so, the module
 555           will be called i2c-ocores.
 556
 557 config I2C_OMAP
 558         tristate "OMAP I2C adapter"
 559         depends on ARCH_OMAP
 560         default y if MACH_OMAP_H3 || MACH_OMAP_OSK
 561         help
 562           If you say yes to this option, support will be included for the
 563           I2C interface on the Texas Instruments OMAP1/2 family of processors.
 564           Like OMAP1510/1610/1710/5912 and OMAP242x.
 565           For details see http://www.ti.com/omap.
 566
 567 config I2C_PASEMI
 568         tristate "PA Semi SMBus interface"
 569         depends on PPC_PASEMI && PCI
 570         help
 571           Supports the PA Semi PWRficient on-chip SMBus interfaces.
 572
 573 config I2C_PCA_PLATFORM
 574         tristate "PCA9564/PCA9665 as platform device"
 575         select I2C_ALGOPCA
 576         default n
 577         help
 578           This driver supports a memory mapped Philips PCA9564/PCA9665
 579           parallel bus to I2C bus controller.
 580
 581           This driver can also be built as a module.  If so, the module
 582           will be called i2c-pca-platform.
 583
 584 config I2C_PMCMSP
 585         tristate "PMC MSP I2C TWI Controller"
 586         depends on PMC_MSP
 587         help
 588           This driver supports the PMC TWI controller on MSP devices.
 589
 590           This driver can also be built as module. If so, the module
 591           will be called i2c-pmcmsp.
 592
 593 config I2C_PNX
 594         tristate "I2C bus support for Philips PNX and NXP LPC targets"
 595         depends on ARCH_LPC32XX
 596         help
 597           This driver supports the Philips IP3204 I2C IP block master and/or
 598           slave controller
 599
 600           This driver can also be built as a module.  If so, the module
 601           will be called i2c-pnx.
 602
 603 config I2C_PUV3
 604         tristate "PKUnity v3 I2C bus support"
 605         depends on UNICORE32 && ARCH_PUV3
 606         select I2C_ALGOBIT
 607         help
 608           This driver supports the I2C IP inside the PKUnity-v3 SoC.
 609           This I2C bus controller is under AMBA/AXI bus.
 610
 611           This driver can also be built as a module.  If so, the module
 612           will be called i2c-puv3.
 613
 614 config I2C_PXA
 615         tristate "Intel PXA2XX I2C adapter"
 616         depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
 617         help
 618           If you have devices in the PXA I2C bus, say yes to this option.
 619           This driver can also be built as a module.  If so, the module
 620           will be called i2c-pxa.
 621
 622 config I2C_PXA_PCI
 623         def_bool I2C_PXA && X86_32 && PCI && OF
 624
 625 config I2C_PXA_SLAVE
 626         bool "Intel PXA2XX I2C Slave comms support"
 627         depends on I2C_PXA && !X86_32
 628         help
 629           Support I2C slave mode communications on the PXA I2C bus.  This
 630           is necessary for systems where the PXA may be a target on the
 631           I2C bus.
 632
 633 config HAVE_S3C2410_I2C
 634         bool
 635         help
 636           This will include I2C support for Samsung SoCs. If you want to
 637           include I2C support for any machine, kindly select this in the
 638           respective Kconfig file.
 639
 640 config I2C_S3C2410
 641         tristate "S3C2410 I2C Driver"
 642         depends on HAVE_S3C2410_I2C
 643         help
 644           Say Y here to include support for I2C controller in the
 645           Samsung SoCs.
 646
 647 config I2C_S6000
 648         tristate "S6000 I2C support"
 649         depends on XTENSA_VARIANT_S6000
 650         help
 651           This driver supports the on chip I2C device on the
 652           S6000 xtensa processor family.
 653
 654           To compile this driver as a module, choose M here. The module
 655           will be called i2c-s6000.
 656
 657 config I2C_SH7760
 658         tristate "Renesas SH7760 I2C Controller"
 659         depends on CPU_SUBTYPE_SH7760
 660         help
 661           This driver supports the 2 I2C interfaces on the Renesas SH7760.
 662
 663           This driver can also be built as a module.  If so, the module
 664           will be called i2c-sh7760.
 665
 666 config I2C_SH_MOBILE
 667         tristate "SuperH Mobile I2C Controller"
 668         depends on SUPERH || ARCH_SHMOBILE
 669         help
 670           If you say yes to this option, support will be included for the
 671           built-in I2C interface on the Renesas SH-Mobile processor.
 672
 673           This driver can also be built as a module.  If so, the module
 674           will be called i2c-sh_mobile.
 675
 676 config I2C_SIMTEC
 677         tristate "Simtec Generic I2C interface"
 678         select I2C_ALGOBIT
 679         help
 680           If you say yes to this option, support will be included for
 681           the Simtec Generic I2C interface. This driver is for the
 682           simple I2C bus used on newer Simtec products for general
 683           I2C, such as DDC on the Simtec BBD2016A.
 684
 685           This driver can also be built as a module. If so, the module
 686           will be called i2c-simtec.
 687
 688 config I2C_SIRF
 689         tristate "CSR SiRFprimaII I2C interface"
 690         depends on ARCH_PRIMA2
 691         help
 692           If you say yes to this option, support will be included for the
 693           CSR SiRFprimaII I2C interface.
 694
 695           This driver can also be built as a module.  If so, the module
 696           will be called i2c-sirf.
 697
 698 config I2C_STU300
 699         tristate "ST Microelectronics DDC I2C interface"
 700         depends on MACH_U300
 701         default y if MACH_U300
 702         help
 703           If you say yes to this option, support will be included for the
 704           I2C interface from ST Microelectronics simply called "DDC I2C"
 705           supporting both I2C and DDC, used in e.g. the U300 series
 706           mobile platforms.
 707
 708           This driver can also be built as a module. If so, the module
 709           will be called i2c-stu300.
 710
 711 config I2C_TEGRA
 712         tristate "NVIDIA Tegra internal I2C controller"
 713         depends on ARCH_TEGRA
 714         help
 715           If you say yes to this option, support will be included for the
 716           I2C controller embedded in NVIDIA Tegra SOCs
 717
 718 config I2C_VERSATILE
 719         tristate "ARM Versatile/Realview I2C bus support"
 720         depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
 721         select I2C_ALGOBIT
 722         help
 723           Say yes if you want to support the I2C serial bus on ARMs Versatile
 724           range of platforms.
 725
 726           This driver can also be built as a module.  If so, the module
 727           will be called i2c-versatile.
 728
 729 config I2C_OCTEON
 730         tristate "Cavium OCTEON I2C bus support"
 731         depends on CPU_CAVIUM_OCTEON
 732         help
 733           Say yes if you want to support the I2C serial bus on Cavium
 734           OCTEON SOC.
 735
 736           This driver can also be built as a module.  If so, the module
 737           will be called i2c-octeon.
 738
 739 config I2C_XILINX
 740         tristate "Xilinx I2C Controller"
 741         depends on HAS_IOMEM
 742         help
 743           If you say yes to this option, support will be included for the
 744           Xilinx I2C controller.
 745
 746           This driver can also be built as a module.  If so, the module
 747           will be called xilinx_i2c.
 748
 749 config I2C_XLR
 750         tristate "XLR I2C support"
 751         depends on CPU_XLR
 752         help
 753           This driver enables support for the on-chip I2C interface of
 754           the Netlogic XLR/XLS MIPS processors.
 755
 756           This driver can also be built as a module.  If so, the module
 757           will be called i2c-xlr.
 758
 759 config I2C_RCAR
 760         tristate "Renesas R-Car I2C Controller"
 761         depends on ARCH_SHMOBILE && I2C
 762         help
 763           If you say yes to this option, support will be included for the
 764           R-Car I2C controller.
 765
 766           This driver can also be built as a module.  If so, the module
 767           will be called i2c-rcar.
 768
 769 comment "External I2C/SMBus adapter drivers"
 770
 771 config I2C_DIOLAN_U2C
 772         tristate "Diolan U2C-12 USB adapter"
 773         depends on USB
 774         help
 775           If you say yes to this option, support will be included for Diolan
 776           U2C-12, a USB to I2C interface.
 777
 778           This driver can also be built as a module.  If so, the module
 779           will be called i2c-diolan-u2c.
 780
 781 config I2C_PARPORT
 782         tristate "Parallel port adapter"
 783         depends on PARPORT && GENERIC_HARDIRQS
 784         select I2C_ALGOBIT
 785         select I2C_SMBUS
 786         help
 787           This supports parallel port I2C adapters such as the ones made by
 788           Philips or Velleman, Analog Devices evaluation boards, and more.
 789           Basically any adapter using the parallel port as an I2C bus with
 790           no extra chipset is supported by this driver, or could be.
 791
 792           This driver is a replacement for (and was inspired by) an older
 793           driver named i2c-philips-par.  The new driver supports more devices,
 794           and makes it easier to add support for new devices.
 795
 796           An adapter type parameter is now mandatory.  Please read the file
 797           Documentation/i2c/busses/i2c-parport for details.
 798
 799           Another driver exists, named i2c-parport-light, which doesn't depend
 800           on the parport driver.  This is meant for embedded systems. Don't say
 801           Y here if you intend to say Y or M there.
 802
 803           This support is also available as a module.  If so, the module
 804           will be called i2c-parport.
 805
 806 config I2C_PARPORT_LIGHT
 807         tristate "Parallel port adapter (light)"
 808         depends on GENERIC_HARDIRQS
 809         select I2C_ALGOBIT
 810         select I2C_SMBUS
 811         help
 812           This supports parallel port I2C adapters such as the ones made by
 813           Philips or Velleman, Analog Devices evaluation boards, and more.
 814           Basically any adapter using the parallel port as an I2C bus with
 815           no extra chipset is supported by this driver, or could be.
 816
 817           This driver is a light version of i2c-parport.  It doesn't depend
 818           on the parport driver, and uses direct I/O access instead.  This
 819           might be preferred on embedded systems where wasting memory for
 820           the clean but heavy parport handling is not an option.  The
 821           drawback is a reduced portability and the impossibility to
 822           daisy-chain other parallel port devices.
 823
 824           Don't say Y here if you said Y or M to i2c-parport.  Saying M to
 825           both is possible but both modules should not be loaded at the same
 826           time.
 827
 828           This support is also available as a module.  If so, the module
 829           will be called i2c-parport-light.
 830
 831 config I2C_TAOS_EVM
 832         tristate "TAOS evaluation module"
 833         depends on TTY
 834         select SERIO
 835         select SERIO_SERPORT
 836         default n
 837         help
 838           This supports TAOS evaluation modules on serial port. In order to
 839           use this driver, you will need the inputattach tool, which is part
 840           of the input-utils package.
 841
 842           If unsure, say N.
 843
 844           This support is also available as a module.  If so, the module
 845           will be called i2c-taos-evm.
 846
 847 config I2C_TINY_USB
 848         tristate "Tiny-USB adapter"
 849         depends on USB
 850         help
 851           If you say yes to this option, support will be included for the
 852           i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
 853           http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
 854
 855           This driver can also be built as a module.  If so, the module
 856           will be called i2c-tiny-usb.
 857
 858 config I2C_VIPERBOARD
 859         tristate "Viperboard I2C master support"
 860         depends on MFD_VIPERBOARD && USB
 861         help
 862           Say yes here to access the I2C part of the Nano River
 863           Technologies Viperboard as I2C master.
 864           See viperboard API specification and Nano
 865           River Tech's viperboard.h for detailed meaning
 866           of the module parameters.
 867
 868 comment "Other I2C/SMBus bus drivers"
 869
 870 config I2C_ACORN
 871         tristate "Acorn IOC/IOMD I2C bus support"
 872         depends on ARCH_ACORN
 873         default y
 874         select I2C_ALGOBIT
 875         help
 876           Say yes if you want to support the I2C bus on Acorn platforms.
 877
 878           If you don't know, say Y.
 879
 880 config I2C_ELEKTOR
 881         tristate "Elektor ISA card"
 882         depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
 883         select I2C_ALGOPCF
 884         help
 885           This supports the PCF8584 ISA bus I2C adapter.  Say Y if you own
 886           such an adapter.
 887
 888           This support is also available as a module.  If so, the module
 889           will be called i2c-elektor.
 890
 891 config I2C_PCA_ISA
 892         tristate "PCA9564/PCA9665 on an ISA bus"
 893         depends on ISA
 894         select I2C_ALGOPCA
 895         default n
 896         help
 897           This driver supports ISA boards using the Philips PCA9564/PCA9665
 898           parallel bus to I2C bus controller.
 899
 900           This driver can also be built as a module.  If so, the module
 901           will be called i2c-pca-isa.
 902
 903           This device is almost undetectable and using this driver on a
 904           system which doesn't have this device will result in long
 905           delays when I2C/SMBus chip drivers are loaded (e.g. at boot
 906           time).  If unsure, say N.
 907
 908 config I2C_SIBYTE
 909         tristate "SiByte SMBus interface"
 910         depends on SIBYTE_SB1xxx_SOC
 911         help
 912           Supports the SiByte SOC on-chip I2C interfaces (2 channels).
 913
 914 config SCx200_I2C
 915         tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
 916         depends on SCx200_GPIO
 917         select I2C_ALGOBIT
 918         help
 919           Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
 920
 921           If you don't know what to do here, say N.
 922
 923           This support is also available as a module.  If so, the module
 924           will be called scx200_i2c.
 925
 926           This driver is deprecated and will be dropped soon. Use i2c-gpio
 927           (or scx200_acb) instead.
 928
 929 config SCx200_I2C_SCL
 930         int "GPIO pin used for SCL"
 931         depends on SCx200_I2C
 932         default "12"
 933         help
 934           Enter the GPIO pin number used for the SCL signal.  This value can
 935           also be specified with a module parameter.
 936
 937 config SCx200_I2C_SDA
 938         int "GPIO pin used for SDA"
 939         depends on SCx200_I2C
 940         default "13"
 941         help
 942           Enter the GPIO pin number used for the SSA signal.  This value can
 943           also be specified with a module parameter.
 944
 945 config SCx200_ACB
 946         tristate "Geode ACCESS.bus support"
 947         depends on X86_32 && PCI
 948         help
 949           Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
 950           SC1100 processors and the CS5535 and CS5536 Geode companion devices.
 951
 952           If you don't know what to do here, say N.
 953
 954           This support is also available as a module.  If so, the module
 955           will be called scx200_acb.
 956
 957 endmenu