This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

omap_device: omap_i2c.1: new worst case activate latency

Other Parts Discussed in Thread: AM3505

I've been seeing the following occasionally on my unit,

omap_device: omap_i2c.1: new worst case activate latency 0: 366210

I am using AM3505 and its i2c to work with 2 temp sensors LM75 and one 24c02 eeprom

Don't experience any issues though I am not sure what this print suggests is happening to the i2c and could it be important?

Thanks

  • Hi Yakir,

    I will forward this to the SW experts.

  • Hi Yakir,

    Which kernel do you use?

    In latest SDK7, which uses kernel v3.12.10, this message is not present, grep does not return anything.  

    But in earlier kernels, i.e. v3.8, this message is printed withing the _omap_device_activate() function in arch/arm/mach-omap2/omap_device.c driver.

    If you have a look at the source code you will see that this is not an error, but a warning message, and it shouldn't affect the work of your device.

    Description of the _omap_device_activate() function is:

    /**

    * _omap_device_activate - increase device readiness

    * @od: struct omap_device *

    * @ignore_lat: increase to latency target (0) or full readiness (1)?

    *

    * Increase readiness of omap_device @od (thus decreasing device

    * wakeup latency, but consuming more power).  If @ignore_lat is

    * IGNORE_WAKEUP_LAT, make the omap_device fully active.  Otherwise,

    * if @ignore_lat is USE_WAKEUP_LAT, and the device's maximum wakeup

    * latency is greater than the requested maximum wakeup latency, step

    * backwards in the omap_device_pm_latency table to ensure the

    * device's maximum wakeup latency is less than or equal to the

    * requested maximum wakeup latency.  Returns 0.

    */


    Hope this helps.

    Best Regards,
    Yordan