In OMAP4 I2C module has only fclk control and iclks are controlled
through hardware.(The OMAP4 clock tree autogeneration script has
been updated accordingly.)

CC:Paul Walmsley <[email protected]>
CC:Benoit Cousson <[email protected])his patch>
Signed-off-by: Santosh Shilimkar <[email protected]>
---
 arch/arm/mach-omap2/clock44xx_data.c |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/arch/arm/mach-omap2/clock44xx_data.c 
b/arch/arm/mach-omap2/clock44xx_data.c
index 86af31d..a69e8a0 100644
--- a/arch/arm/mach-omap2/clock44xx_data.c
+++ b/arch/arm/mach-omap2/clock44xx_data.c
@@ -2665,10 +2665,10 @@ static struct omap_clk omap44xx_clks[] = {
        CLK(NULL,       "gptimer9_ck",                  &gptimer9_ck,   
CK_443X),
        CLK("omap2_hdq.0",      "ick",                          &hdq1w_ck,      
CK_443X),
        CLK(NULL,       "hsi_ck",                       &hsi_ck,        
CK_443X),
-       CLK("i2c_omap.1",       "ick",                          &i2c1_ck,       
CK_443X),
-       CLK("i2c_omap.2",       "ick",                          &i2c2_ck,       
CK_443X),
-       CLK("i2c_omap.3",       "ick",                          &i2c3_ck,       
CK_443X),
-       CLK("i2c_omap.4",       "ick",                          &i2c4_ck,       
CK_443X),
+       CLK("i2c_omap.1",       "fck",                          &i2c1_ck,       
CK_443X),
+       CLK("i2c_omap.2",       "fck",                          &i2c2_ck,       
CK_443X),
+       CLK("i2c_omap.3",       "fck",                          &i2c3_ck,       
CK_443X),
+       CLK("i2c_omap.4",       "fck",                          &i2c4_ck,       
CK_443X),
        CLK(NULL,       "iss_ck",                       &iss_ck,        
CK_443X),
        CLK(NULL,       "ivahd_ck",                     &ivahd_ck,      
CK_443X),
        CLK(NULL,       "keyboard_ck",                  &keyboard_ck,   
CK_443X),
-- 
1.6.0.4

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to