diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index b8a36ab4d3dc..53b67a9eb073 100644
--- 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