diff options
-rw-r--r-- | drivers/i2c/busses/Kconfig | 6 | ||||
-rw-r--r-- | drivers/i2c/chips/Kconfig | 8 |
2 files changed, 14 insertions, 0 deletions
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig index e3450d16d8a4..d25a8cbbec0a 100644 --- a/drivers/i2c/busses/Kconfig +++ b/drivers/i2c/busses/Kconfig | |||
@@ -503,6 +503,7 @@ config I2C_PCA_ISA | |||
503 | tristate "PCA9564 on an ISA bus" | 503 | tristate "PCA9564 on an ISA bus" |
504 | depends on I2C | 504 | depends on I2C |
505 | select I2C_ALGOPCA | 505 | select I2C_ALGOPCA |
506 | default n | ||
506 | help | 507 | help |
507 | This driver supports ISA boards using the Philips PCA 9564 | 508 | This driver supports ISA boards using the Philips PCA 9564 |
508 | Parallel bus to I2C bus controller | 509 | Parallel bus to I2C bus controller |
@@ -510,6 +511,11 @@ config I2C_PCA_ISA | |||
510 | This driver can also be built as a module. If so, the module | 511 | This driver can also be built as a module. If so, the module |
511 | will be called i2c-pca-isa. | 512 | will be called i2c-pca-isa. |
512 | 513 | ||
514 | This device is almost undetectable and using this driver on a | ||
515 | system which doesn't have this device will result in long | ||
516 | delays when I2C/SMBus chip drivers are loaded (e.g. at boot | ||
517 | time). If unsure, say N. | ||
518 | |||
513 | config I2C_MV64XXX | 519 | config I2C_MV64XXX |
514 | tristate "Marvell mv64xxx I2C Controller" | 520 | tristate "Marvell mv64xxx I2C Controller" |
515 | depends on I2C && MV64X60 && EXPERIMENTAL | 521 | depends on I2C && MV64X60 && EXPERIMENTAL |
diff --git a/drivers/i2c/chips/Kconfig b/drivers/i2c/chips/Kconfig index 7aa5c38f0855..87ee3ce58618 100644 --- a/drivers/i2c/chips/Kconfig +++ b/drivers/i2c/chips/Kconfig | |||
@@ -39,6 +39,7 @@ config SENSORS_EEPROM | |||
39 | config SENSORS_PCF8574 | 39 | config SENSORS_PCF8574 |
40 | tristate "Philips PCF8574 and PCF8574A" | 40 | tristate "Philips PCF8574 and PCF8574A" |
41 | depends on I2C && EXPERIMENTAL | 41 | depends on I2C && EXPERIMENTAL |
42 | default n | ||
42 | help | 43 | help |
43 | If you say yes here you get support for Philips PCF8574 and | 44 | If you say yes here you get support for Philips PCF8574 and |
44 | PCF8574A chips. | 45 | PCF8574A chips. |
@@ -46,6 +47,9 @@ config SENSORS_PCF8574 | |||
46 | This driver can also be built as a module. If so, the module | 47 | This driver can also be built as a module. If so, the module |
47 | will be called pcf8574. | 48 | will be called pcf8574. |
48 | 49 | ||
50 | These devices are hard to detect and rarely found on mainstream | ||
51 | hardware. If unsure, say N. | ||
52 | |||
49 | config SENSORS_PCA9539 | 53 | config SENSORS_PCA9539 |
50 | tristate "Philips PCA9539 16-bit I/O port" | 54 | tristate "Philips PCA9539 16-bit I/O port" |
51 | depends on I2C && EXPERIMENTAL | 55 | depends on I2C && EXPERIMENTAL |
@@ -59,12 +63,16 @@ config SENSORS_PCA9539 | |||
59 | config SENSORS_PCF8591 | 63 | config SENSORS_PCF8591 |
60 | tristate "Philips PCF8591" | 64 | tristate "Philips PCF8591" |
61 | depends on I2C && EXPERIMENTAL | 65 | depends on I2C && EXPERIMENTAL |
66 | default n | ||
62 | help | 67 | help |
63 | If you say yes here you get support for Philips PCF8591 chips. | 68 | If you say yes here you get support for Philips PCF8591 chips. |
64 | 69 | ||
65 | This driver can also be built as a module. If so, the module | 70 | This driver can also be built as a module. If so, the module |
66 | will be called pcf8591. | 71 | will be called pcf8591. |
67 | 72 | ||
73 | These devices are hard to detect and rarely found on mainstream | ||
74 | hardware. If unsure, say N. | ||
75 | |||
68 | config ISP1301_OMAP | 76 | config ISP1301_OMAP |
69 | tristate "Philips ISP1301 with OMAP OTG" | 77 | tristate "Philips ISP1301 with OMAP OTG" |
70 | depends on I2C && ARCH_OMAP_OTG | 78 | depends on I2C && ARCH_OMAP_OTG |