Hi All,
The atached file is the patch for the problem.Wending >-----Original Message----- >From: Sonasath, Moiz [mailto:[email protected]] >Sent: December 16, 2009 10:58 AM >To: Weng, Wending; [email protected]; [email protected] >Subject: RE: OMAP3 I2C driver timing problem with multiple messages >transfer > > >Wending, > >> -----Original Message----- >> From: [email protected] [mailto:linux-omap- >> [email protected]] On Behalf Of Weng, Wending >> Sent: Wednesday, December 16, 2009 8:54 AM >> To: [email protected]; [email protected] >> Subject: OMAP3 I2C driver timing problem with multiple messages transfer >> >> Hi All, >> >> Some I2C related protocols as SMBus, each command is composed of >> multiple I2C messages with timing constraint, the delay between two >> messages must be less than 10 ms, otherwise, the SMBus device will be >> timeout, and the command fails. As the function >> wait_for_completion_timeout is used to wait the end of a message, it >> doesn't guarante the next message will be sent out in 10 ms after the >> previous message is completed, so the SMBus command fails very often. I >> developped a patch for fixing this timing problem(2.6.32.RC5), is there >> anybody willing to review and to incorporate the patch into the furture >> release? >> >Yes, do send out the patch as I am sure people would be interested to review >your patch as well as incorporate it if it's >needed. Please send out the patch to these mailing lists. >> Wending >> Software Engineer >> at Rheinmetall Canada >> -- >> 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
i2c.patch
Description: i2c.patch
