Kalle Jokiniemi said the following on 10/07/2009 05:10 AM: >>> extra delays and subsequent re-trys cause i2c clocks >>> to be active more often. This has also an negative >>> effect on power consumption. >>> >>> Added a constraint that allows MPU to wake up in few >>> hundred usecs, which is roughly the average i2c wait >>> period. >>> >> How did you arrive at the number 500us for the wakeup latency? >> > > This was about the average time that I observed i2c-transfers to be > (from clk_enable to clk_disable), when off mode was not enabled. > just a quick 2cents: I understand that the 500uSec might need to be board dependent - here is why: one theory we have regarding the timeout delay having to be modified on zoom2 was that if the delay was 500uSec, the touch screen controller timesout and pulls of the data in the middle of transfer. Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
