1. 23 Feb, 2011 2 commits
    • Richard woodruff's avatar
      i2c-omap: Double clear of ARDY status in IRQ handler · cb527ede
      Richard woodruff authored
      This errata occurs when the ARDY interrupt generation is enabled.
      At the begining of every new transaction the ARDY interrupt is cleared.
      
      On continuous i2c transactions where after clearing the ARDY bit from
      I2C_STAT register (clearing the interrupt), the IRQ line is reasserted and the
      I2C_STAT[ARDY] bit set again on 1. In fact, the ARDY status bit is not cleared
      at the write access to I2C_STAT[ARDY] and only the IRQ line is deasserted and
      then reasserted. This is not captured in the usual errata documents.
      
      The workaround is to have a double clear of ARDY status in irq handler.
      Signed-off-by: default avatarRichard woodruff <r-woodruff2@ti.com>
      Signed-off-by: default avatarKeerthy <j-keerthy@ti.com>
      Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
      cb527ede
    • Balaji T K's avatar
      i2c-omap: fix build for !CONFIG_SUSPEND · f72487e7
      Balaji T K authored
      fix the build break when !CONFIG_SUSPEND
      
      drivers/i2c/busses/i2c-omap.c:1173: error: lvalue required as unary '&' operand
      make[3]: *** [drivers/i2c/busses/i2c-omap.o] Error 1
      make[2]: *** [drivers/i2c/busses] Error 2
      make[1]: *** [drivers/i2c] Error 2
      make: *** [drivers] Error 2
      Signed-off-by: default avatarBalaji T K <balajitk@ti.com>
      Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
      f72487e7
  2. 22 Feb, 2011 9 commits
  3. 21 Feb, 2011 29 commits