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