drivers/i2c/busses/Kconfig

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