Hi, The kernel is from the tag "v2.6.26-omap2". And I applied the patch
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commitdiff; h=663715fc55ea5d292171c6934a2b91d8f4874171;hp=3c0134484bd5fe3c3d9611aab1983881efc894c0 But it did not work for me. Pramod On Mon, Dec 22, 2008 at 10:44 AM, pramod gurav <pramodfo...@gmail.com> wrote: > Hi, > I am using current linux-omap git sources. Can you please post the patch to > fix > this timeout issue. > > On Sat, Dec 20, 2008 at 7:39 PM, Felipe Balbi <m...@felipebalbi.com> wrote: >> On Sat, Dec 20, 2008 at 03:34:00PM +0530, pramod gurav wrote: >>> Hi, >>> I am working on OMAP3430 board. The kernel is linux-omap-2.6. >>> The twl5030 module is sitting on i2c1. >>> I often come across a error saying >>> >>> i2c_omap i2c_omap.1: controller timed out >>> i2c_omap i2c_omap.1: controller timed out >>> >>> This is all what appears in logs when i2c1 times out and all the >>> other slave devices on i2c1 stop responding. Other i2c busses(2) >>> work properly. if try to reboot the I2C fails to respnd in u-boot also >>> saying >>> >>> timed out in wait_for_pin: I2C_STAT=0 >>> I2C read failed >>> timed out in wait_for_pin: I2C_STAT=0 >>> I2C read failed >>> timed out in wait_for_pin: I2C_STAT=0 >>> I2C read failed >>> >>> I have to to do hard reset to progress with the boot. >>> >>> I gone through the changes happened to i2-omap driver in between >>> and tried applying the patches manually. >>> The problem still persists. >>> May be I am missing some more changes. >>> >>> The i2-omap.c source is attached herewith this mail. >>> Somebody please suggest me on this issue if this has been seen as >>> a issue and if fixed. >> >> Are you using current linux-omap from git ? This problem is long gone. >> >> -- >> balbi >> > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
