aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/i2c/busses/Kconfig
diff options
context:
space:
mode:
Diffstat (limited to 'drivers/i2c/busses/Kconfig')
-rw-r--r--drivers/i2c/busses/Kconfig27
1 files changed, 20 insertions, 7 deletions
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index ff01c389e2da..65dd599a0262 100644
--- a/drivers/i2c/busses/Kconfig
+++ b/drivers/i2c/busses/Kconfig
@@ -294,18 +294,21 @@ comment "I2C system bus drivers (mostly embedded / system-on-chip)"
294 294
295config I2C_AT91 295config I2C_AT91
296 tristate "Atmel AT91 I2C Two-Wire interface (TWI)" 296 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
297 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN 297 depends on ARCH_AT91 && EXPERIMENTAL
298 help 298 help
299 This supports the use of the I2C interface on Atmel AT91 299 This supports the use of the I2C interface on Atmel AT91
300 processors. 300 processors.
301 301
302 This driver is BROKEN because the controller which it uses 302 A serious problem is that there is no documented way to issue
303 will easily trigger RX overrun and TX underrun errors. Using 303 repeated START conditions for more than two messages, as needed
304 low I2C clock rates may partially work around those issues
305 on some systems. Another serious problem is that there is no
306 documented way to issue repeated START conditions, as needed
307 to support combined I2C messages. Use the i2c-gpio driver 304 to support combined I2C messages. Use the i2c-gpio driver
308 unless your system can cope with those limitations. 305 unless your system can cope with this limitation.
306
307 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
308 don't have clock stretching in transmission mode. For that reason,
309 you can encounter underrun issues causing premature stop sendings if
310 the latency to fill the transmission register is too long. If you
311 are facing this situation, use the i2c-gpio driver.
309 312
310config I2C_AU1550 313config I2C_AU1550
311 tristate "Au1550/Au1200/Au1300 SMBus interface" 314 tristate "Au1550/Au1200/Au1300 SMBus interface"
@@ -718,6 +721,16 @@ config I2C_XLR
718 This driver can also be built as a module. If so, the module 721 This driver can also be built as a module. If so, the module
719 will be called i2c-xlr. 722 will be called i2c-xlr.
720 723
724config I2C_RCAR
725 tristate "Renesas R-Car I2C Controller"
726 depends on ARCH_SHMOBILE && I2C
727 help
728 If you say yes to this option, support will be included for the
729 R-Car I2C controller.
730
731 This driver can also be built as a module. If so, the module
732 will be called i2c-rcar.
733
721comment "External I2C/SMBus adapter drivers" 734comment "External I2C/SMBus adapter drivers"
722 735
723config I2C_DIOLAN_U2C 736config I2C_DIOLAN_U2C