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 || COMPILE_TEST
  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_IPROC
 376         tristate "Broadcom iProc I2C controller"
 377         depends on ARCH_BCM_IPROC || COMPILE_TEST
 378         default ARCH_BCM_IPROC
 379         help
 380           If you say yes to this option, support will be included for the
 381           Broadcom iProc I2C controller.
 382
 383           If you don't know what to do here, say N.
 384
 385 config I2C_BCM_KONA
 386         tristate "BCM Kona I2C adapter"
 387         depends on ARCH_BCM_MOBILE
 388         default y
 389         help
 390           If you say yes to this option, support will be included for the
 391           I2C interface on the Broadcom Kona family of processors.
 392
 393           If you do not need KONA I2C interface, say N.
 394
 395 config I2C_BLACKFIN_TWI
 396         tristate "Blackfin TWI I2C support"
 397         depends on BLACKFIN
 398         depends on !BF561 && !BF531 && !BF532 && !BF533
 399         help
 400           This is the I2C bus driver for Blackfin on-chip TWI interface.
 401
 402           This driver can also be built as a module.  If so, the module
 403           will be called i2c-bfin-twi.
 404
 405 config I2C_BLACKFIN_TWI_CLK_KHZ
 406         int "Blackfin TWI I2C clock (kHz)"
 407         depends on I2C_BLACKFIN_TWI
 408         range 21 400
 409         default 50
 410         help
 411           The unit of the TWI clock is kHz.
 412
 413 config I2C_CADENCE
 414         tristate "Cadence I2C Controller"
 415         depends on ARCH_ZYNQ
 416         help
 417           Say yes here to select Cadence I2C Host Controller. This controller is
 418           e.g. used by Xilinx Zynq.
 419
 420 config I2C_CBUS_GPIO
 421         tristate "CBUS I2C driver"
 422         depends on GPIOLIB
 423         help
 424           Support for CBUS access using I2C API. Mostly relevant for Nokia
 425           Internet Tablets (770, N800 and N810).
 426
 427           This driver can also be built as a module.  If so, the module
 428           will be called i2c-cbus-gpio.
 429
 430 config I2C_CPM
 431         tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
 432         depends on CPM1 || CPM2
 433         help
 434           This supports the use of the I2C interface on Freescale
 435           processors with CPM1 or CPM2.
 436
 437           This driver can also be built as a module.  If so, the module
 438           will be called i2c-cpm.
 439
 440 config I2C_DAVINCI
 441         tristate "DaVinci I2C driver"
 442         depends on ARCH_DAVINCI || ARCH_KEYSTONE
 443         help
 444           Support for TI DaVinci I2C controller driver.
 445
 446           This driver can also be built as a module.  If so, the module
 447           will be called i2c-davinci.
 448
 449           Please note that this driver might be needed to bring up other
 450           devices such as DaVinci NIC.
 451           For details please see http://www.ti.com/davinci
 452
 453 config I2C_DESIGNWARE_CORE
 454         tristate
 455
 456 config I2C_DESIGNWARE_PLATFORM
 457         tristate "Synopsys DesignWare Platform"
 458         select I2C_DESIGNWARE_CORE
 459         depends on (ACPI && COMMON_CLK) || !ACPI
 460         help
 461           If you say yes to this option, support will be included for the
 462           Synopsys DesignWare I2C adapter. Only master mode is supported.
 463
 464           This driver can also be built as a module.  If so, the module
 465           will be called i2c-designware-platform.
 466
 467 config I2C_DESIGNWARE_PCI
 468         tristate "Synopsys DesignWare PCI"
 469         depends on PCI
 470         select I2C_DESIGNWARE_CORE
 471         help
 472           If you say yes to this option, support will be included for the
 473           Synopsys DesignWare I2C adapter. Only master mode is supported.
 474
 475           This driver can also be built as a module.  If so, the module
 476           will be called i2c-designware-pci.
 477
 478 config I2C_DESIGNWARE_BAYTRAIL
 479         bool "Intel Baytrail I2C semaphore support"
 480         depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI
 481         help
 482           This driver enables managed host access to the PMIC I2C bus on select
 483           Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
 484           the host to request uninterrupted access to the PMIC's I2C bus from
 485           the platform firmware controlling it. You should say Y if running on
 486           a BayTrail system using the AXP288.
 487
 488 config I2C_EFM32
 489         tristate "EFM32 I2C controller"
 490         depends on ARCH_EFM32 || COMPILE_TEST
 491         help
 492           This driver supports the i2c block found in Energy Micro's EFM32
 493           SoCs.
 494
 495 config I2C_EG20T
 496         tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
 497         depends on PCI && (X86_32 || COMPILE_TEST)
 498         help
 499           This driver is for PCH(Platform controller Hub) I2C of EG20T which
 500           is an IOH(Input/Output Hub) for x86 embedded processor.
 501           This driver can access PCH I2C bus device.
 502
 503           This driver also can be used for LAPIS Semiconductor IOH(Input/
 504           Output Hub), ML7213, ML7223 and ML7831.
 505           ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
 506           for MP(Media Phone) use and ML7831 IOH is for general purpose use.
 507           ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
 508           ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
 509
 510 config I2C_EXYNOS5
 511         tristate "Exynos5 high-speed I2C driver"
 512         depends on ARCH_EXYNOS && OF
 513         default y
 514         help
 515           High-speed I2C controller on Exynos5 based Samsung SoCs.
 516
 517 config I2C_GPIO
 518         tristate "GPIO-based bitbanging I2C"
 519         depends on GPIOLIB
 520         select I2C_ALGOBIT
 521         help
 522           This is a very simple bitbanging I2C driver utilizing the
 523           arch-neutral GPIO API to control the SCL and SDA lines.
 524
 525 config I2C_HIGHLANDER
 526         tristate "Highlander FPGA SMBus interface"
 527         depends on SH_HIGHLANDER
 528         help
 529           If you say yes to this option, support will be included for
 530           the SMBus interface located in the FPGA on various Highlander
 531           boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
 532           FPGAs. This is wholly unrelated to the SoC I2C.
 533
 534           This driver can also be built as a module.  If so, the module
 535           will be called i2c-highlander.
 536
 537 config I2C_IBM_IIC
 538         tristate "IBM PPC 4xx on-chip I2C interface"
 539         depends on 4xx
 540         help
 541           Say Y here if you want to use IIC peripheral found on
 542           embedded IBM PPC 4xx based systems.
 543
 544           This driver can also be built as a module.  If so, the module
 545           will be called i2c-ibm_iic.
 546
 547 config I2C_IMG
 548         tristate "Imagination Technologies I2C SCB Controller"
 549         depends on MIPS || METAG || COMPILE_TEST
 550         help
 551           Say Y here if you want to use the IMG I2C SCB controller,
 552           available on the TZ1090 and other IMG SoCs.
 553
 554           This driver can also be built as a module.  If so, the module
 555           will be called i2c-img-scb.
 556
 557 config I2C_IMX
 558         tristate "IMX I2C interface"
 559         depends on ARCH_MXC
 560         help
 561           Say Y here if you want to use the IIC bus controller on
 562           the Freescale i.MX/MXC processors.
 563
 564           This driver can also be built as a module.  If so, the module
 565           will be called i2c-imx.
 566
 567 config I2C_IOP3XX
 568         tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
 569         depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
 570         help
 571           Say Y here if you want to use the IIC bus controller on
 572           the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
 573
 574           This driver can also be built as a module.  If so, the module
 575           will be called i2c-iop3xx.
 576
 577 config I2C_KEMPLD
 578         tristate "Kontron COM I2C Controller"
 579         depends on MFD_KEMPLD
 580         help
 581           This enables support for the I2C bus interface on some Kontron ETX
 582           and COMexpress (ETXexpress) modules.
 583
 584           This driver can also be built as a module. If so, the module
 585           will be called i2c-kempld.
 586
 587 config I2C_MESON
 588         tristate "Amlogic Meson I2C controller"
 589         depends on ARCH_MESON
 590         help
 591           If you say yes to this option, support will be included for the
 592           I2C interface on the Amlogic Meson family of SoCs.
 593
 594 config I2C_MPC
 595         tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
 596         depends on PPC
 597         help
 598           If you say yes to this option, support will be included for the
 599           built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
 600           MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
 601
 602           This driver can also be built as a module.  If so, the module
 603           will be called i2c-mpc.
 604
 605 config I2C_MV64XXX
 606         tristate "Marvell mv64xxx I2C Controller"
 607         depends on MV64X60 || PLAT_ORION || ARCH_SUNXI
 608         help
 609           If you say yes to this option, support will be included for the
 610           built-in I2C interface on the Marvell 64xxx line of host bridges.
 611           This driver is also used for Allwinner SoCs I2C controllers.
 612
 613           This driver can also be built as a module.  If so, the module
 614           will be called i2c-mv64xxx.
 615
 616 config I2C_MXS
 617         tristate "Freescale i.MX28 I2C interface"
 618         depends on SOC_IMX28
 619         select STMP_DEVICE
 620         help
 621           Say Y here if you want to use the I2C bus controller on
 622           the Freescale i.MX28 processors.
 623
 624           This driver can also be built as a module.  If so, the module
 625           will be called i2c-mxs.
 626
 627 config I2C_NOMADIK
 628         tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
 629         depends on ARM_AMBA
 630         help
 631           If you say yes to this option, support will be included for the
 632           I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
 633           as well as the STA2X11 PCIe I/O HUB.
 634
 635 config I2C_OCORES
 636         tristate "OpenCores I2C Controller"
 637         help
 638           If you say yes to this option, support will be included for the
 639           OpenCores I2C controller. For details see
 640           http://www.opencores.org/projects.cgi/web/i2c/overview
 641
 642           This driver can also be built as a module.  If so, the module
 643           will be called i2c-ocores.
 644
 645 config I2C_OMAP
 646         tristate "OMAP I2C adapter"
 647         depends on ARCH_OMAP
 648         default y if MACH_OMAP_H3 || MACH_OMAP_OSK
 649         help
 650           If you say yes to this option, support will be included for the
 651           I2C interface on the Texas Instruments OMAP1/2 family of processors.
 652           Like OMAP1510/1610/1710/5912 and OMAP242x.
 653           For details see http://www.ti.com/omap.
 654
 655 config I2C_PASEMI
 656         tristate "PA Semi SMBus interface"
 657         depends on PPC_PASEMI && PCI
 658         help
 659           Supports the PA Semi PWRficient on-chip SMBus interfaces.
 660
 661 config I2C_PCA_PLATFORM
 662         tristate "PCA9564/PCA9665 as platform device"
 663         select I2C_ALGOPCA
 664         default n
 665         help
 666           This driver supports a memory mapped Philips PCA9564/PCA9665
 667           parallel bus to I2C bus controller.
 668
 669           This driver can also be built as a module.  If so, the module
 670           will be called i2c-pca-platform.
 671
 672 config I2C_PMCMSP
 673         tristate "PMC MSP I2C TWI Controller"
 674         depends on PMC_MSP
 675         help
 676           This driver supports the PMC TWI controller on MSP devices.
 677
 678           This driver can also be built as module. If so, the module
 679           will be called i2c-pmcmsp.
 680
 681 config I2C_PNX
 682         tristate "I2C bus support for Philips PNX and NXP LPC targets"
 683         depends on ARCH_LPC32XX
 684         help
 685           This driver supports the Philips IP3204 I2C IP block master and/or
 686           slave controller
 687
 688           This driver can also be built as a module.  If so, the module
 689           will be called i2c-pnx.
 690
 691 config I2C_PUV3
 692         tristate "PKUnity v3 I2C bus support"
 693         depends on UNICORE32 && ARCH_PUV3
 694         select I2C_ALGOBIT
 695         help
 696           This driver supports the I2C IP inside the PKUnity-v3 SoC.
 697           This I2C bus controller is under AMBA/AXI bus.
 698
 699           This driver can also be built as a module.  If so, the module
 700           will be called i2c-puv3.
 701
 702 config I2C_PXA
 703         tristate "Intel PXA2XX I2C adapter"
 704         depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
 705         help
 706           If you have devices in the PXA I2C bus, say yes to this option.
 707           This driver can also be built as a module.  If so, the module
 708           will be called i2c-pxa.
 709
 710 config I2C_PXA_PCI
 711         def_bool I2C_PXA && X86_32 && PCI && OF
 712
 713 config I2C_PXA_SLAVE
 714         bool "Intel PXA2XX I2C Slave comms support"
 715         depends on I2C_PXA && !X86_32
 716         help
 717           Support I2C slave mode communications on the PXA I2C bus.  This
 718           is necessary for systems where the PXA may be a target on the
 719           I2C bus.
 720
 721 config I2C_QUP
 722         tristate "Qualcomm QUP based I2C controller"
 723         depends on ARCH_QCOM
 724         help
 725           If you say yes to this option, support will be included for the
 726           built-in I2C interface on the Qualcomm SoCs.
 727
 728           This driver can also be built as a module.  If so, the module
 729           will be called i2c-qup.
 730
 731 config I2C_RIIC
 732         tristate "Renesas RIIC adapter"
 733         depends on ARCH_SHMOBILE || COMPILE_TEST
 734         help
 735           If you say yes to this option, support will be included for the
 736           Renesas RIIC I2C interface.
 737
 738           This driver can also be built as a module.  If so, the module
 739           will be called i2c-riic.
 740
 741 config I2C_RK3X
 742         tristate "Rockchip RK3xxx I2C adapter"
 743         depends on OF && COMMON_CLK
 744         help
 745           Say Y here to include support for the I2C adapter in Rockchip RK3xxx
 746           SoCs.
 747
 748           This driver can also be built as a module. If so, the module will
 749           be called i2c-rk3x.
 750
 751 config HAVE_S3C2410_I2C
 752         bool
 753         help
 754           This will include I2C support for Samsung SoCs. If you want to
 755           include I2C support for any machine, kindly select this in the
 756           respective Kconfig file.
 757
 758 config I2C_S3C2410
 759         tristate "S3C2410 I2C Driver"
 760         depends on HAVE_S3C2410_I2C
 761         help
 762           Say Y here to include support for I2C controller in the
 763           Samsung SoCs.
 764
 765 config I2C_SH7760
 766         tristate "Renesas SH7760 I2C Controller"
 767         depends on CPU_SUBTYPE_SH7760
 768         help
 769           This driver supports the 2 I2C interfaces on the Renesas SH7760.
 770
 771           This driver can also be built as a module.  If so, the module
 772           will be called i2c-sh7760.
 773
 774 config I2C_SH_MOBILE
 775         tristate "SuperH Mobile I2C Controller"
 776         depends on HAS_DMA
 777         depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
 778         help
 779           If you say yes to this option, support will be included for the
 780           built-in I2C interface on the Renesas SH-Mobile processor.
 781
 782           This driver can also be built as a module.  If so, the module
 783           will be called i2c-sh_mobile.
 784
 785 config I2C_SIMTEC
 786         tristate "Simtec Generic I2C interface"
 787         select I2C_ALGOBIT
 788         help
 789           If you say yes to this option, support will be included for
 790           the Simtec Generic I2C interface. This driver is for the
 791           simple I2C bus used on newer Simtec products for general
 792           I2C, such as DDC on the Simtec BBD2016A.
 793
 794           This driver can also be built as a module. If so, the module
 795           will be called i2c-simtec.
 796
 797 config I2C_SIRF
 798         tristate "CSR SiRFprimaII I2C interface"
 799         depends on ARCH_SIRF
 800         help
 801           If you say yes to this option, support will be included for the
 802           CSR SiRFprimaII I2C interface.
 803
 804           This driver can also be built as a module.  If so, the module
 805           will be called i2c-sirf.
 806
 807 config I2C_ST
 808         tristate "STMicroelectronics SSC I2C support"
 809         depends on ARCH_STI
 810         help
 811           Enable this option to add support for STMicroelectronics SoCs
 812           hardware SSC (Synchronous Serial Controller) as an I2C controller.
 813
 814           This driver can also be built as module. If so, the module
 815           will be called i2c-st.
 816
 817 config I2C_STU300
 818         tristate "ST Microelectronics DDC I2C interface"
 819         depends on MACH_U300
 820         default y if MACH_U300
 821         help
 822           If you say yes to this option, support will be included for the
 823           I2C interface from ST Microelectronics simply called "DDC I2C"
 824           supporting both I2C and DDC, used in e.g. the U300 series
 825           mobile platforms.
 826
 827           This driver can also be built as a module. If so, the module
 828           will be called i2c-stu300.
 829
 830 config I2C_SUN6I_P2WI
 831         tristate "Allwinner sun6i internal P2WI controller"
 832         depends on RESET_CONTROLLER
 833         depends on MACH_SUN6I || COMPILE_TEST
 834         help
 835           If you say yes to this option, support will be included for the
 836           P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
 837           SOCs.
 838           The P2WI looks like an SMBus controller (which supports only byte
 839           accesses), except that it only supports one slave device.
 840           This interface is used to connect to specific PMIC devices (like the
 841           AXP221).
 842
 843 config I2C_TEGRA
 844         tristate "NVIDIA Tegra internal I2C controller"
 845         depends on ARCH_TEGRA
 846         help
 847           If you say yes to this option, support will be included for the
 848           I2C controller embedded in NVIDIA Tegra SOCs
 849
 850 config I2C_VERSATILE
 851         tristate "ARM Versatile/Realview I2C bus support"
 852         depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
 853         select I2C_ALGOBIT
 854         help
 855           Say yes if you want to support the I2C serial bus on ARMs Versatile
 856           range of platforms.
 857
 858           This driver can also be built as a module.  If so, the module
 859           will be called i2c-versatile.
 860
 861 config I2C_WMT
 862         tristate "Wondermedia WM8xxx SoC I2C bus support"
 863         depends on ARCH_VT8500
 864         help
 865           Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
 866           SoCs.
 867
 868           This driver can also be built as a module. If so, the module will be
 869           called i2c-wmt.
 870
 871 config I2C_OCTEON
 872         tristate "Cavium OCTEON I2C bus support"
 873         depends on CAVIUM_OCTEON_SOC
 874         help
 875           Say yes if you want to support the I2C serial bus on Cavium
 876           OCTEON SOC.
 877
 878           This driver can also be built as a module.  If so, the module
 879           will be called i2c-octeon.
 880
 881 config I2C_XILINX
 882         tristate "Xilinx I2C Controller"
 883         depends on HAS_IOMEM
 884         help
 885           If you say yes to this option, support will be included for the
 886           Xilinx I2C controller.
 887
 888           This driver can also be built as a module.  If so, the module
 889           will be called xilinx_i2c.
 890
 891 config I2C_XLR
 892         tristate "XLR I2C support"
 893         depends on CPU_XLR
 894         help
 895           This driver enables support for the on-chip I2C interface of
 896           the Netlogic XLR/XLS MIPS processors.
 897
 898           This driver can also be built as a module.  If so, the module
 899           will be called i2c-xlr.
 900
 901 config I2C_RCAR
 902         tristate "Renesas R-Car I2C Controller"
 903         depends on ARCH_SHMOBILE || COMPILE_TEST
 904         help
 905           If you say yes to this option, support will be included for the
 906           R-Car I2C controller.
 907
 908           This driver can also be built as a module.  If so, the module
 909           will be called i2c-rcar.
 910
 911 comment "External I2C/SMBus adapter drivers"
 912
 913 config I2C_DIOLAN_U2C
 914         tristate "Diolan U2C-12 USB adapter"
 915         depends on USB
 916         help
 917           If you say yes to this option, support will be included for Diolan
 918           U2C-12, a USB to I2C interface.
 919
 920           This driver can also be built as a module.  If so, the module
 921           will be called i2c-diolan-u2c.
 922
 923 config I2C_DLN2
 924        tristate "Diolan DLN-2 USB I2C adapter"
 925        depends on MFD_DLN2
 926        help
 927          If you say yes to this option, support will be included for Diolan
 928          DLN2, a USB to I2C interface.
 929
 930          This driver can also be built as a module.  If so, the module
 931          will be called i2c-dln2.
 932
 933 config I2C_PARPORT
 934         tristate "Parallel port adapter"
 935         depends on PARPORT
 936         select I2C_ALGOBIT
 937         select I2C_SMBUS
 938         help
 939           This supports parallel port I2C adapters such as the ones made by
 940           Philips or Velleman, Analog Devices evaluation boards, and more.
 941           Basically any adapter using the parallel port as an I2C bus with
 942           no extra chipset is supported by this driver, or could be.
 943
 944           This driver is a replacement for (and was inspired by) an older
 945           driver named i2c-philips-par.  The new driver supports more devices,
 946           and makes it easier to add support for new devices.
 947
 948           An adapter type parameter is now mandatory.  Please read the file
 949           Documentation/i2c/busses/i2c-parport for details.
 950
 951           Another driver exists, named i2c-parport-light, which doesn't depend
 952           on the parport driver.  This is meant for embedded systems. Don't say
 953           Y here if you intend to say Y or M there.
 954
 955           This support is also available as a module.  If so, the module
 956           will be called i2c-parport.
 957
 958 config I2C_PARPORT_LIGHT
 959         tristate "Parallel port adapter (light)"
 960         select I2C_ALGOBIT
 961         select I2C_SMBUS
 962         help
 963           This supports parallel port I2C adapters such as the ones made by
 964           Philips or Velleman, Analog Devices evaluation boards, and more.
 965           Basically any adapter using the parallel port as an I2C bus with
 966           no extra chipset is supported by this driver, or could be.
 967
 968           This driver is a light version of i2c-parport.  It doesn't depend
 969           on the parport driver, and uses direct I/O access instead.  This
 970           might be preferred on embedded systems where wasting memory for
 971           the clean but heavy parport handling is not an option.  The
 972           drawback is a reduced portability and the impossibility to
 973           daisy-chain other parallel port devices.
 974
 975           Don't say Y here if you said Y or M to i2c-parport.  Saying M to
 976           both is possible but both modules should not be loaded at the same
 977           time.
 978
 979           This support is also available as a module.  If so, the module
 980           will be called i2c-parport-light.
 981
 982 config I2C_ROBOTFUZZ_OSIF
 983         tristate "RobotFuzz Open Source InterFace USB adapter"
 984         depends on USB
 985         help
 986           If you say yes to this option, support will be included for the
 987           RobotFuzz Open Source InterFace USB to I2C interface.
 988
 989           This driver can also be built as a module.  If so, the module
 990           will be called i2c-osif.
 991
 992 config I2C_TAOS_EVM
 993         tristate "TAOS evaluation module"
 994         depends on TTY
 995         select SERIO
 996         select SERIO_SERPORT
 997         default n
 998         help
 999           This supports TAOS evaluation modules on serial port. In order to
1000           use this driver, you will need the inputattach tool, which is part
1001           of the input-utils package.
1002
1003           If unsure, say N.
1004
1005           This support is also available as a module.  If so, the module
1006           will be called i2c-taos-evm.
1007
1008 config I2C_TINY_USB
1009         tristate "Tiny-USB adapter"
1010         depends on USB
1011         help
1012           If you say yes to this option, support will be included for the
1013           i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1014           http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1015
1016           This driver can also be built as a module.  If so, the module
1017           will be called i2c-tiny-usb.
1018
1019 config I2C_VIPERBOARD
1020         tristate "Viperboard I2C master support"
1021         depends on MFD_VIPERBOARD && USB
1022         help
1023           Say yes here to access the I2C part of the Nano River
1024           Technologies Viperboard as I2C master.
1025           See viperboard API specification and Nano
1026           River Tech's viperboard.h for detailed meaning
1027           of the module parameters.
1028
1029 comment "Other I2C/SMBus bus drivers"
1030
1031 config I2C_ACORN
1032         tristate "Acorn IOC/IOMD I2C bus support"
1033         depends on ARCH_ACORN
1034         default y
1035         select I2C_ALGOBIT
1036         help
1037           Say yes if you want to support the I2C bus on Acorn platforms.
1038
1039           If you don't know, say Y.
1040
1041 config I2C_ELEKTOR
1042         tristate "Elektor ISA card"
1043         depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1044         select I2C_ALGOPCF
1045         help
1046           This supports the PCF8584 ISA bus I2C adapter.  Say Y if you own
1047           such an adapter.
1048
1049           This support is also available as a module.  If so, the module
1050           will be called i2c-elektor.
1051
1052 config I2C_PCA_ISA
1053         tristate "PCA9564/PCA9665 on an ISA bus"
1054         depends on ISA
1055         select I2C_ALGOPCA
1056         default n
1057         help
1058           This driver supports ISA boards using the Philips PCA9564/PCA9665
1059           parallel bus to I2C bus controller.
1060
1061           This driver can also be built as a module.  If so, the module
1062           will be called i2c-pca-isa.
1063
1064           This device is almost undetectable and using this driver on a
1065           system which doesn't have this device will result in long
1066           delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1067           time).  If unsure, say N.
1068
1069 config I2C_SIBYTE
1070         tristate "SiByte SMBus interface"
1071         depends on SIBYTE_SB1xxx_SOC
1072         help
1073           Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1074
1075 config I2C_CROS_EC_TUNNEL
1076         tristate "ChromeOS EC tunnel I2C bus"
1077         depends on MFD_CROS_EC
1078         help
1079           If you say yes here you get an I2C bus that will tunnel i2c commands
1080           through to the other side of the ChromeOS EC to the i2c bus
1081           connected there. This will work whatever the interface used to
1082           talk to the EC (SPI, I2C or LPC).
1083
1084 config SCx200_ACB
1085         tristate "Geode ACCESS.bus support"
1086         depends on X86_32 && PCI
1087         help
1088           Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1089           SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1090
1091           If you don't know what to do here, say N.
1092
1093           This support is also available as a module.  If so, the module
1094           will be called scx200_acb.
1095
1096 config I2C_OPAL
1097         tristate "IBM OPAL I2C driver"
1098         depends on PPC_POWERNV
1099         default y
1100         help
1101           This exposes the PowerNV platform i2c busses to the linux i2c layer,
1102           the driver is based on the OPAL interfaces.
1103
1104           This driver can also be built as a module. If so, the module will be
1105           called as i2c-opal.
1106
1107 endmenu