config add i2cx select

diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index b8a36ab4d3dcbcd5c7b2d29caa52e6739ac1a121..53b67a9eb07303955a9e9ce6f54d28e53eab1dd7 100644 (file)
--- a/drivers/i2c/busses/Kconfig
+++ b/drivers/i2c/busses/Kconfig
@@ -8,13 +8,22 @@ config I2C_RK2818
        tristate "RK2818 i2c interface (I2C)"
        depends on ARCH_RK2818
        help
-               This supports the use of the I2C interface on rk2818
-               processors.
-
-               Using low I2C clock rates may partially work around those issues
-               on some systems. Another serious problem is that there is no
-               documented way to issue repeated START conditions, as needed
-               to support combined I2C messages. Use the i2c-gpio driver
-               unless your system can cope with those limitations.
+               This supports the use of the I2C interface on rk2818 processors.
 
+if I2C_RK2818
+       comment "Now, there are two I2C interfaces selected by developer, I2C0 and I2C1."
+       
+       menuconfig I2C0_RK2818
+               tristate "RK2818 I2C0 interface support"
+               default y
+               depends on ARCH_RK2818
+               help
+                       This supports the use of the I2C0 interface on rk2818 processors.
+       menuconfig I2C1_RK2818
+               tristate "RK2818 I2C1 interface support"
+               default y
+               depends on ARCH_RK2818
+               help
+                       This supports the use of the I2C1 interface on rk2818 processors.
+endif
 endmenu