From 6995d0cb2fd820fb0db949e2f36bad3f242e6064 Mon Sep 17 00:00:00 2001 From: =?utf8?q?=E6=9F=AF=E9=A3=9E=E9=9B=84?= Date: Thu, 13 May 2010 13:07:50 +0000 Subject: [PATCH] config add i2cx select --- drivers/i2c/busses/Kconfig | 25 +++++++++++++++++-------- 1 file changed, 17 insertions(+), 8 deletions(-) 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 -- 2.34.1