1. 27 7月, 2010 1 次提交
    • A
      OMAP3: wait on IDLEST after enabling USBTLL fclk · 25499d93
      Anand Gadiyar 提交于
      We need to wait on the IDLEST bit after the clocks are enabled
      before attempting to access any register.
      
      Currently, the USBTLL i-clock ops uses the clkops_omap2_dflt_wait,
      while the USBTLL f-clock ops uses clkops_omap2_dflt. If the
      i-clock is enabled first, the clkops_omap2_dflt_wait is
      short-circuited as the companion f-clock is not enabled.
      This can cause a data abort if the IDLEST has not transitioned,
      and we try to access a USBTLL register.
      
      Since the USBTLL i-clock and f-clock could be enabled in any order,
      this is a bug. Fix it by changing the clkops for the f-clock.
      Signed-off-by: NAnand Gadiyar <gadiyar@ti.com>
      Acked-by: NKevin Hilman <khilman@deeprootsystems.com>
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      25499d93
  2. 23 7月, 2010 7 次提交
  3. 22 7月, 2010 17 次提交
  4. 21 7月, 2010 15 次提交