diff options
-rw-r--r-- | drivers/i2c/busses/Kconfig | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig index d01d0b175e1c..495c971ce5bf 100644 --- a/drivers/i2c/busses/Kconfig +++ b/drivers/i2c/busses/Kconfig | |||
@@ -135,7 +135,7 @@ config I2C_ELEKTOR | |||
135 | This supports the PCF8584 ISA bus I2C adapter. Say Y if you own | 135 | This supports the PCF8584 ISA bus I2C adapter. Say Y if you own |
136 | such an adapter. | 136 | such an adapter. |
137 | 137 | ||
138 | This support is also available as a module. If so, the module | 138 | This support is also available as a module. If so, the module |
139 | will be called i2c-elektor. | 139 | will be called i2c-elektor. |
140 | 140 | ||
141 | config I2C_GPIO | 141 | config I2C_GPIO |
@@ -190,7 +190,7 @@ config I2C_I810 | |||
190 | select I2C_ALGOBIT | 190 | select I2C_ALGOBIT |
191 | help | 191 | help |
192 | If you say yes to this option, support will be included for the Intel | 192 | If you say yes to this option, support will be included for the Intel |
193 | 810/815 family of mainboard I2C interfaces. Specifically, the | 193 | 810/815 family of mainboard I2C interfaces. Specifically, the |
194 | following versions of the chipset are supported: | 194 | following versions of the chipset are supported: |
195 | i810AA | 195 | i810AA |
196 | i810AB | 196 | i810AB |
@@ -248,8 +248,8 @@ config I2C_IBM_IIC | |||
248 | tristate "IBM PPC 4xx on-chip I2C interface" | 248 | tristate "IBM PPC 4xx on-chip I2C interface" |
249 | depends on 4xx | 249 | depends on 4xx |
250 | help | 250 | help |
251 | Say Y here if you want to use IIC peripheral found on | 251 | Say Y here if you want to use IIC peripheral found on |
252 | embedded IBM PPC 4xx based systems. | 252 | embedded IBM PPC 4xx based systems. |
253 | 253 | ||
254 | This driver can also be built as a module. If so, the module | 254 | This driver can also be built as a module. If so, the module |
255 | will be called i2c-ibm_iic. | 255 | will be called i2c-ibm_iic. |
@@ -269,7 +269,7 @@ config I2C_IXP2000 | |||
269 | depends on ARCH_IXP2000 | 269 | depends on ARCH_IXP2000 |
270 | select I2C_ALGOBIT | 270 | select I2C_ALGOBIT |
271 | help | 271 | help |
272 | Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based | 272 | Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based |
273 | system and are using GPIO lines for an I2C bus. | 273 | system and are using GPIO lines for an I2C bus. |
274 | 274 | ||
275 | This support is also available as a module. If so, the module | 275 | This support is also available as a module. If so, the module |
@@ -354,7 +354,7 @@ config I2C_PARPORT | |||
354 | on the parport driver. This is meant for embedded systems. Don't say | 354 | on the parport driver. This is meant for embedded systems. Don't say |
355 | Y here if you intend to say Y or M there. | 355 | Y here if you intend to say Y or M there. |
356 | 356 | ||
357 | This support is also available as a module. If so, the module | 357 | This support is also available as a module. If so, the module |
358 | will be called i2c-parport. | 358 | will be called i2c-parport. |
359 | 359 | ||
360 | config I2C_PARPORT_LIGHT | 360 | config I2C_PARPORT_LIGHT |
@@ -372,12 +372,12 @@ config I2C_PARPORT_LIGHT | |||
372 | the clean but heavy parport handling is not an option. The | 372 | the clean but heavy parport handling is not an option. The |
373 | drawback is a reduced portability and the impossibility to | 373 | drawback is a reduced portability and the impossibility to |
374 | daisy-chain other parallel port devices. | 374 | daisy-chain other parallel port devices. |
375 | 375 | ||
376 | Don't say Y here if you said Y or M to i2c-parport. Saying M to | 376 | Don't say Y here if you said Y or M to i2c-parport. Saying M to |
377 | both is possible but both modules should not be loaded at the same | 377 | both is possible but both modules should not be loaded at the same |
378 | time. | 378 | time. |
379 | 379 | ||
380 | This support is also available as a module. If so, the module | 380 | This support is also available as a module. If so, the module |
381 | will be called i2c-parport-light. | 381 | will be called i2c-parport-light. |
382 | 382 | ||
383 | config I2C_PASEMI | 383 | config I2C_PASEMI |
@@ -401,7 +401,7 @@ config I2C_PROSAVAGE | |||
401 | 401 | ||
402 | This driver is deprecated in favor of the savagefb driver. | 402 | This driver is deprecated in favor of the savagefb driver. |
403 | 403 | ||
404 | This support is also available as a module. If so, the module | 404 | This support is also available as a module. If so, the module |
405 | will be called i2c-prosavage. | 405 | will be called i2c-prosavage. |
406 | 406 | ||
407 | config I2C_S3C2410 | 407 | config I2C_S3C2410 |
@@ -417,7 +417,7 @@ config I2C_SAVAGE4 | |||
417 | depends on PCI | 417 | depends on PCI |
418 | select I2C_ALGOBIT | 418 | select I2C_ALGOBIT |
419 | help | 419 | help |
420 | If you say yes to this option, support will be included for the | 420 | If you say yes to this option, support will be included for the |
421 | S3 Savage 4 I2C interface. | 421 | S3 Savage 4 I2C interface. |
422 | 422 | ||
423 | This driver is deprecated in favor of the savagefb driver. | 423 | This driver is deprecated in favor of the savagefb driver. |
@@ -452,7 +452,7 @@ config SCx200_I2C | |||
452 | 452 | ||
453 | If you don't know what to do here, say N. | 453 | If you don't know what to do here, say N. |
454 | 454 | ||
455 | This support is also available as a module. If so, the module | 455 | This support is also available as a module. If so, the module |
456 | will be called scx200_i2c. | 456 | will be called scx200_i2c. |
457 | 457 | ||
458 | This driver is deprecated and will be dropped soon. Use i2c-gpio | 458 | This driver is deprecated and will be dropped soon. Use i2c-gpio |
@@ -483,14 +483,14 @@ config SCx200_ACB | |||
483 | 483 | ||
484 | If you don't know what to do here, say N. | 484 | If you don't know what to do here, say N. |
485 | 485 | ||
486 | This support is also available as a module. If so, the module | 486 | This support is also available as a module. If so, the module |
487 | will be called scx200_acb. | 487 | will be called scx200_acb. |
488 | 488 | ||
489 | config I2C_SIS5595 | 489 | config I2C_SIS5595 |
490 | tristate "SiS 5595" | 490 | tristate "SiS 5595" |
491 | depends on PCI | 491 | depends on PCI |
492 | help | 492 | help |
493 | If you say yes to this option, support will be included for the | 493 | If you say yes to this option, support will be included for the |
494 | SiS5595 SMBus (a subset of I2C) interface. | 494 | SiS5595 SMBus (a subset of I2C) interface. |
495 | 495 | ||
496 | This driver can also be built as a module. If so, the module | 496 | This driver can also be built as a module. If so, the module |
@@ -500,7 +500,7 @@ config I2C_SIS630 | |||
500 | tristate "SiS 630/730" | 500 | tristate "SiS 630/730" |
501 | depends on PCI | 501 | depends on PCI |
502 | help | 502 | help |
503 | If you say yes to this option, support will be included for the | 503 | If you say yes to this option, support will be included for the |
504 | SiS630 and SiS730 SMBus (a subset of I2C) interface. | 504 | SiS630 and SiS730 SMBus (a subset of I2C) interface. |
505 | 505 | ||
506 | This driver can also be built as a module. If so, the module | 506 | This driver can also be built as a module. If so, the module |
@@ -634,7 +634,7 @@ config I2C_PCA_ISA | |||
634 | help | 634 | help |
635 | This driver supports ISA boards using the Philips PCA9564 | 635 | This driver supports ISA boards using the Philips PCA9564 |
636 | parallel bus to I2C bus controller. | 636 | parallel bus to I2C bus controller. |
637 | 637 | ||
638 | This driver can also be built as a module. If so, the module | 638 | This driver can also be built as a module. If so, the module |
639 | will be called i2c-pca-isa. | 639 | will be called i2c-pca-isa. |
640 | 640 | ||