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