i2c 2 issues on omap3430

From: "naveen krishna ch" <naveenkrishna.ch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: i2c 2 issues on omap3430
Date: Mon, 25 Aug 2008 12:48:04 +0530	[thread overview]
Message-ID: <ef0d8a250808250018w587c2de0s726511c52c0794e3@mail.gmail.com> (raw)
In-Reply-To: <ef0d8a250808250005sbf8bb8cg9cfacc6a6f2b4195-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1.1: Type: text/plain, Size: 1041 bytes --]

Hi,
    I am facing some i2c issues on omap3430 with linux 2.6.24 kernel.

    My device is a slave sitting on I2C2 of OMAP3430.

    I am observing the following,
     1) Sometimes i get "i2c_omap.2: controller timed out"

                   i2c_omap.2: No acknowledmentif i use i2c 2 at 100khz
        and i dont find them when i run at 400khz.

     2) Sometimes the i2c write and read succeeds but data received is junk.

     3) The I2C reads are not consistent. with same image if i boot
several times

        The readed values keep variying.

      I am not sure what could be the problem. The mux settings seems okay.

     The client creation seems fine. Can any one suggest me the exact
     i2c bus registration steps. right now i only have

omap_register_i2c_bus(1, CONFIG_I2C_OMAP34XX_HS_BUS1, NULL, 0);

in the board file. and

MUX configurations in the

arch/arm/plat-omap/i2c.c
arch/arm/mach-omap2/mux.c
include/asm/arch/mux.h

files

     Am i missing something?

     Please advice,

-- 
Thanks,
(: Naveen Krishna Ch :)

[-- Attachment #1.2: Type: text/html, Size: 1291 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c