1# 2# Sensor device configuration 3# 4 5menu "I2C Hardware Bus support" 6 depends on I2C 7 8config I2C_ALI1535 9 tristate "ALI 1535" 10 depends on I2C && PCI 11 help 12 If you say yes to this option, support will be included for the SMB 13 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB 14 controller is part of the 7101 device, which is an ACPI-compliant 15 Power Management Unit (PMU). 16 17 This driver can also be built as a module. If so, the module 18 will be called i2c-ali1535. 19 20config I2C_ALI1563 21 tristate "ALI 1563" 22 depends on I2C && PCI && EXPERIMENTAL 23 help 24 If you say yes to this option, support will be included for the SMB 25 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB 26 controller is part of the 7101 device, which is an ACPI-compliant 27 Power Management Unit (PMU). 28 29 This driver can also be built as a module. If so, the module 30 will be called i2c-ali1563. 31 32config I2C_ALI15X3 33 tristate "ALI 15x3" 34 depends on I2C && PCI 35 help 36 If you say yes to this option, support will be included for the 37 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces. 38 39 This driver can also be built as a module. If so, the module 40 will be called i2c-ali15x3. 41 42config I2C_AMD756 43 tristate "AMD 756/766/768/8111 and nVidia nForce" 44 depends on I2C && PCI 45 help 46 If you say yes to this option, support will be included for the AMD 47 756/766/768 mainboard I2C interfaces. The driver also includes 48 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and 49 the nVidia nForce I2C interface. 50 51 This driver can also be built as a module. If so, the module 52 will be called i2c-amd756. 53 54config I2C_AMD756_S4882 55 tristate "SMBus multiplexing on the Tyan S4882" 56 depends on I2C_AMD756 && EXPERIMENTAL 57 help 58 Enabling this option will add specific SMBus support for the Tyan 59 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed 60 over 8 different channels, where the various memory module EEPROMs 61 and temperature sensors live. Saying yes here will give you access 62 to these in addition to the trunk. 63 64 This driver can also be built as a module. If so, the module 65 will be called i2c-amd756-s4882. 66 67config I2C_AMD8111 68 tristate "AMD 8111" 69 depends on I2C && PCI 70 help 71 If you say yes to this option, support will be included for the 72 second (SMBus 2.0) AMD 8111 mainboard I2C interface. 73 74 This driver can also be built as a module. If so, the module 75 will be called i2c-amd8111. 76 77config I2C_AU1550 78 tristate "Au1550 SMBus interface" 79 depends on I2C && SOC_AU1550 80 help 81 If you say yes to this option, support will be included for the 82 Au1550 SMBus interface. 83 84 This driver can also be built as a module. If so, the module 85 will be called i2c-au1550. 86 87config I2C_ELEKTOR 88 tristate "Elektor ISA card" 89 depends on I2C && ISA && BROKEN_ON_SMP 90 select I2C_ALGOPCF 91 help 92 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own 93 such an adapter. 94 95 This support is also available as a module. If so, the module 96 will be called i2c-elektor. 97 98config I2C_HYDRA 99 tristate "CHRP Apple Hydra Mac I/O I2C interface" 100 depends on I2C && PCI && PPC_CHRP && EXPERIMENTAL 101 select I2C_ALGOBIT 102 help 103 This supports the use of the I2C interface in the Apple Hydra Mac 104 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you 105 have such a machine. 106 107 This support is also available as a module. If so, the module 108 will be called i2c-hydra. 109 110config I2C_I801 111 tristate "Intel 82801 (ICH)" 112 depends on I2C && PCI 113 help 114 If you say yes to this option, support will be included for the Intel 115 801 family of mainboard I2C interfaces. Specifically, the following 116 versions of the chipset are supported: 117 82801AA 118 82801AB 119 82801BA 120 82801CA/CAM 121 82801DB 122 82801EB/ER (ICH5/ICH5R) 123 6300ESB 124 ICH6 125 ICH7 126 ESB2 127 128 This driver can also be built as a module. If so, the module 129 will be called i2c-i801. 130 131config I2C_I810 132 tristate "Intel 810/815" 133 depends on I2C && PCI 134 select I2C_ALGOBIT 135 help 136 If you say yes to this option, support will be included for the Intel 137 810/815 family of mainboard I2C interfaces. Specifically, the 138 following versions of the chipset is supported: 139 i810AA 140 i810AB 141 i810E 142 i815 143 144 This driver can also be built as a module. If so, the module 145 will be called i2c-i810. 146 147config I2C_PXA 148 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)" 149 depends on I2C && EXPERIMENTAL && ARCH_PXA 150 help 151 If you have devices in the PXA I2C bus, say yes to this option. 152 This driver can also be built as a module. If so, the module 153 will be called i2c-pxa. 154 155config I2C_PXA_SLAVE 156 bool "Intel PXA2XX I2C Slave comms support" 157 depends on I2C_PXA 158 help 159 Support I2C slave mode communications on the PXA I2C bus. This 160 is necessary for systems where the PXA may be a target on the 161 I2C bus. 162 163config I2C_PIIX4 164 tristate "Intel PIIX4" 165 depends on I2C && PCI 166 help 167 If you say yes to this option, support will be included for the Intel 168 PIIX4 family of mainboard I2C interfaces. Specifically, the following 169 versions of the chipset are supported: 170 Intel PIIX4 171 Intel 440MX 172 Serverworks OSB4 173 Serverworks CSB5 174 Serverworks CSB6 175 SMSC Victory66 176 177 This driver can also be built as a module. If so, the module 178 will be called i2c-piix4. 179 180config I2C_IBM_IIC 181 tristate "IBM PPC 4xx on-chip I2C interface" 182 depends on IBM_OCP && I2C 183 help 184 Say Y here if you want to use IIC peripheral found on 185 embedded IBM PPC 4xx based systems. 186 187 This driver can also be built as a module. If so, the module 188 will be called i2c-ibm_iic. 189 190config I2C_IOP3XX 191 tristate "Intel IOP3xx and IXP4xx on-chip I2C interface" 192 depends on (ARCH_IOP3XX || ARCH_IXP4XX) && I2C 193 help 194 Say Y here if you want to use the IIC bus controller on 195 the Intel IOP3xx I/O Processors or IXP4xx Network Processors. 196 197 This driver can also be built as a module. If so, the module 198 will be called i2c-iop3xx. 199 200config I2C_ISA 201 tristate 202 depends on I2C 203 204config I2C_ITE 205 tristate "ITE I2C Adapter" 206 depends on I2C && MIPS_ITE8172 207 select I2C_ALGOITE 208 help 209 This supports the ITE8172 I2C peripheral found on some MIPS 210 systems. Say Y if you have one of these. You should also say Y for 211 the ITE I2C driver algorithm support above. 212 213 This support is also available as a module. If so, the module 214 will be called i2c-ite. 215 216config I2C_IXP4XX 217 tristate "IXP4xx GPIO-Based I2C Interface" 218 depends on I2C && ARCH_IXP4XX 219 select I2C_ALGOBIT 220 help 221 Say Y here if you have an Intel IXP4xx(420,421,422,425) based 222 system and are using GPIO lines for an I2C bus. 223 224 This support is also available as a module. If so, the module 225 will be called i2c-ixp4xx. 226 227config I2C_IXP2000 228 tristate "IXP2000 GPIO-Based I2C Interface" 229 depends on I2C && ARCH_IXP2000 230 select I2C_ALGOBIT 231 help 232 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based 233 system and are using GPIO lines for an I2C bus. 234 235 This support is also available as a module. If so, the module 236 will be called i2c-ixp2000. 237 238config I2C_KEYWEST 239 tristate "Powermac Keywest I2C interface" 240 depends on I2C && PPC_PMAC 241 help 242 This supports the use of the I2C interface in the combo-I/O 243 chip on recent Apple machines. Say Y if you have such a machine. 244 245 This support is also available as a module. If so, the module 246 will be called i2c-keywest. 247 248config I2C_PMAC_SMU 249 tristate "Powermac SMU I2C interface" 250 depends on I2C && PMAC_SMU 251 help 252 This supports the use of the I2C interface in the SMU 253 chip on recent Apple machines like the iMac G5. It is used 254 among others by the thermal control driver for those machines. 255 Say Y if you have such a machine. 256 257 This support is also available as a module. If so, the module 258 will be called i2c-pmac-smu. 259 260config I2C_MPC 261 tristate "MPC107/824x/85xx/52xx" 262 depends on I2C && PPC32 263 help 264 If you say yes to this option, support will be included for the 265 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and 266 MPC85xx family processors. The driver may also work on 52xx 267 family processors, though interrupts are known not to work. 268 269 This driver can also be built as a module. If so, the module 270 will be called i2c-mpc. 271 272config I2C_NFORCE2 273 tristate "Nvidia nForce2, nForce3 and nForce4" 274 depends on I2C && PCI 275 help 276 If you say yes to this option, support will be included for the Nvidia 277 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces. 278 279 This driver can also be built as a module. If so, the module 280 will be called i2c-nforce2. 281 282config I2C_PARPORT 283 tristate "Parallel port adapter" 284 depends on I2C && PARPORT 285 select I2C_ALGOBIT 286 help 287 This supports parallel port I2C adapters such as the ones made by 288 Philips or Velleman, Analog Devices evaluation boards, and more. 289 Basically any adapter using the parallel port as an I2C bus with 290 no extra chipset is supported by this driver, or could be. 291 292 This driver is a replacement for (and was inspired by) an older 293 driver named i2c-philips-par. The new driver supports more devices, 294 and makes it easier to add support for new devices. 295 296 Another driver exists, named i2c-parport-light, which doesn't depend 297 on the parport driver. This is meant for embedded systems. Don't say 298 Y here if you intend to say Y or M there. 299 300 This support is also available as a module. If so, the module 301 will be called i2c-parport. 302 303config I2C_PARPORT_LIGHT 304 tristate "Parallel port adapter (light)" 305 depends on I2C 306 select I2C_ALGOBIT 307 help 308 This supports parallel port I2C adapters such as the ones made by 309 Philips or Velleman, Analog Devices evaluation boards, and more. 310 Basically any adapter using the parallel port as an I2C bus with 311 no extra chipset is supported by this driver, or could be. 312 313 This driver is a light version of i2c-parport. It doesn't depend 314 on the parport driver, and uses direct I/O access instead. This 315 might be prefered on embedded systems where wasting memory for 316 the clean but heavy parport handling is not an option. The 317 drawback is a reduced portability and the impossibility to 318 dasiy-chain other parallel port devices. 319 320 Don't say Y here if you said Y or M to i2c-parport. Saying M to 321 both is possible but both modules should not be loaded at the same 322 time. 323 324 This support is also available as a module. If so, the module 325 will be called i2c-parport-light. 326 327config I2C_PROSAVAGE 328 tristate "S3/VIA (Pro)Savage" 329 depends on I2C && PCI 330 select I2C_ALGOBIT 331 help 332 If you say yes to this option, support will be included for the 333 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8 334 graphics processors. 335 chipsets supported: 336 S3/VIA KM266/VT8375 aka ProSavage8 337 S3/VIA KM133/VT8365 aka Savage4 338 339 This support is also available as a module. If so, the module 340 will be called i2c-prosavage. 341 342config I2C_RPXLITE 343 tristate "Embedded Planet RPX Lite/Classic support" 344 depends on (RPXLITE || RPXCLASSIC) && I2C 345 select I2C_ALGO8XX 346 347config I2C_S3C2410 348 tristate "S3C2410 I2C Driver" 349 depends on I2C && ARCH_S3C2410 350 help 351 Say Y here to include support for I2C controller in the 352 Samsung S3C2410 based System-on-Chip devices. 353 354config I2C_SAVAGE4 355 tristate "S3 Savage 4" 356 depends on I2C && PCI && EXPERIMENTAL 357 select I2C_ALGOBIT 358 help 359 If you say yes to this option, support will be included for the 360 S3 Savage 4 I2C interface. 361 362 This driver can also be built as a module. If so, the module 363 will be called i2c-savage4. 364 365config I2C_SIBYTE 366 tristate "SiByte SMBus interface" 367 depends on SIBYTE_SB1xxx_SOC && I2C 368 help 369 Supports the SiByte SOC on-chip I2C interfaces (2 channels). 370 371config SCx200_I2C 372 tristate "NatSemi SCx200 I2C using GPIO pins" 373 depends on SCx200_GPIO && I2C 374 select I2C_ALGOBIT 375 help 376 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus. 377 378 If you don't know what to do here, say N. 379 380 This support is also available as a module. If so, the module 381 will be called scx200_i2c. 382 383config SCx200_I2C_SCL 384 int "GPIO pin used for SCL" 385 depends on SCx200_I2C 386 default "12" 387 help 388 Enter the GPIO pin number used for the SCL signal. This value can 389 also be specified with a module parameter. 390 391config SCx200_I2C_SDA 392 int "GPIO pin used for SDA" 393 depends on SCx200_I2C 394 default "13" 395 help 396 Enter the GPIO pin number used for the SSA signal. This value can 397 also be specified with a module parameter. 398 399config SCx200_ACB 400 tristate "NatSemi SCx200 ACCESS.bus" 401 depends on I2C && PCI 402 help 403 Enable the use of the ACCESS.bus controllers of a SCx200 processor. 404 405 If you don't know what to do here, say N. 406 407 This support is also available as a module. If so, the module 408 will be called scx200_acb. 409 410config I2C_SIS5595 411 tristate "SiS 5595" 412 depends on I2C && PCI 413 help 414 If you say yes to this option, support will be included for the 415 SiS5595 SMBus (a subset of I2C) interface. 416 417 This driver can also be built as a module. If so, the module 418 will be called i2c-sis5595. 419 420config I2C_SIS630 421 tristate "SiS 630/730" 422 depends on I2C && PCI 423 help 424 If you say yes to this option, support will be included for the 425 SiS630 and SiS730 SMBus (a subset of I2C) interface. 426 427 This driver can also be built as a module. If so, the module 428 will be called i2c-sis630. 429 430config I2C_SIS96X 431 tristate "SiS 96x" 432 depends on I2C && PCI 433 help 434 If you say yes to this option, support will be included for the SiS 435 96x SMBus (a subset of I2C) interfaces. Specifically, the following 436 chipsets are supported: 437 645/961 438 645DX/961 439 645DX/962 440 648/961 441 650/961 442 735 443 745 444 445 This driver can also be built as a module. If so, the module 446 will be called i2c-sis96x. 447 448config I2C_STUB 449 tristate "I2C/SMBus Test Stub" 450 depends on I2C && EXPERIMENTAL && 'm' 451 default 'n' 452 help 453 This module may be useful to developers of SMBus client drivers, 454 especially for certain kinds of sensor chips. 455 456 If you do build this module, be sure to read the notes and warnings 457 in <file:Documentation/i2c/i2c-stub>. 458 459 If you don't know what to do here, definitely say N. 460 461config I2C_VIA 462 tristate "VIA 82C586B" 463 depends on I2C && PCI && EXPERIMENTAL 464 select I2C_ALGOBIT 465 help 466 If you say yes to this option, support will be included for the VIA 467 82C586B I2C interface 468 469 This driver can also be built as a module. If so, the module 470 will be called i2c-via. 471 472config I2C_VIAPRO 473 tristate "VIA 82C596/82C686/823x" 474 depends on I2C && PCI 475 help 476 If you say yes to this option, support will be included for the VIA 477 82C596/82C686/823x I2C interfaces. Specifically, the following 478 chipsets are supported: 479 82C596A/B 480 82C686A/B 481 8231 482 8233 483 8233A 484 8235 485 8237 486 487 This driver can also be built as a module. If so, the module 488 will be called i2c-viapro. 489 490config I2C_VOODOO3 491 tristate "Voodoo 3" 492 depends on I2C && PCI 493 select I2C_ALGOBIT 494 help 495 If you say yes to this option, support will be included for the 496 Voodoo 3 I2C interface. 497 498 This driver can also be built as a module. If so, the module 499 will be called i2c-voodoo3. 500 501config I2C_PCA_ISA 502 tristate "PCA9564 on an ISA bus" 503 depends on I2C 504 select I2C_ALGOPCA 505 help 506 This driver supports ISA boards using the Philips PCA 9564 507 Parallel bus to I2C bus controller 508 509 This driver can also be built as a module. If so, the module 510 will be called i2c-pca-isa. 511 512config I2C_MV64XXX 513 tristate "Marvell mv64xxx I2C Controller" 514 depends on I2C && MV64X60 && EXPERIMENTAL 515 help 516 If you say yes to this option, support will be included for the 517 built-in I2C interface on the Marvell 64xxx line of host bridges. 518 519 This driver can also be built as a module. If so, the module 520 will be called i2c-mv64xxx. 521 522endmenu 523