1. 26 Jul, 2010 1 commit
    • Anand Gadiyar's avatar
      OMAP3: wait on IDLEST after enabling USBTLL fclk · 25499d93
      Anand Gadiyar authored
      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: default avatarAnand Gadiyar <gadiyar@ti.com>
      Acked-by: default avatarKevin Hilman <khilman@deeprootsystems.com>
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      25499d93
  2. 22 Jul, 2010 18 commits
  3. 21 Jul, 2010 14 commits
  4. 20 Jul, 2010 7 commits