diff options
Diffstat (limited to 'drivers/i2c/busses')
-rw-r--r-- | drivers/i2c/busses/Kconfig | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig index a9cab3e5b8bd..de95c75efb41 100644 --- a/drivers/i2c/busses/Kconfig +++ b/drivers/i2c/busses/Kconfig | |||
@@ -75,11 +75,19 @@ config I2C_AMD8111 | |||
75 | 75 | ||
76 | config I2C_AT91 | 76 | config I2C_AT91 |
77 | tristate "Atmel AT91 I2C Two-Wire interface (TWI)" | 77 | tristate "Atmel AT91 I2C Two-Wire interface (TWI)" |
78 | depends on ARCH_AT91 && EXPERIMENTAL | 78 | depends on ARCH_AT91 && EXPERIMENTAL && BROKEN |
79 | help | 79 | help |
80 | This supports the use of the I2C interface on Atmel AT91 | 80 | This supports the use of the I2C interface on Atmel AT91 |
81 | processors. | 81 | processors. |
82 | 82 | ||
83 | This driver is BROKEN because the controller which it uses | ||
84 | will easily trigger RX overrun and TX underrun errors. Using | ||
85 | low I2C clock rates may partially work around those issues | ||
86 | on some systems. Another serious problem is that there is no | ||
87 | documented way to issue repeated START conditions, as needed | ||
88 | to support combined I2C messages. Use the i2c-gpio driver | ||
89 | unless your system can cope with those limitations. | ||
90 | |||
83 | config I2C_AU1550 | 91 | config I2C_AU1550 |
84 | tristate "Au1550/Au1200 SMBus interface" | 92 | tristate "Au1550/Au1200 SMBus interface" |
85 | depends on SOC_AU1550 || SOC_AU1200 | 93 | depends on SOC_AU1550 || SOC_AU1200 |