1. 30 4月, 2014 1 次提交
  2. 05 3月, 2014 1 次提交
  3. 22 11月, 2013 1 次提交
  4. 21 10月, 2013 1 次提交
  5. 13 6月, 2013 1 次提交
  6. 30 1月, 2013 1 次提交
    • S
      ARM: imx: return zero in case next event gets a large increment · eea8e326
      Shawn Guo 提交于
      The return of v2_set_next_event() will lead to an infinite loop in
      tick_handle_oneshot_broadcast() - "goto again;" with imx6q WAIT mode
      (to be enabled).  This happens because when global event did not expire
      any CPU local events, the broadcast device will be rearmed to a CPU
      local next_event, which could be far away from now and result in a
      max_delta_tick programming in set_next_event().
      
      Fix the problem by detecting those next events with increments larger
      than 0x7fffffff, and simply return zero in that case.
      
      It leaves mx1_2_set_next_event() unchanged since only v2_set_next_event()
      will be running with imx6q WAIT mode support.
      
      Thanks Russell King for helping understand the problem.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      eea8e326
  7. 15 1月, 2013 1 次提交
  8. 15 10月, 2012 3 次提交
  9. 17 7月, 2012 1 次提交
  10. 16 5月, 2012 2 次提交
  11. 25 4月, 2012 1 次提交
    • S
      ARM i.MX timer: request correct clock · 821dc4df
      Sascha Hauer 提交于
      We used to pass the timer clock directly to mxc_timer_init. We
      should instead request the correct clock. This is an intermediate
      step: For now we request the clock in the timer code when NULL
      is passed as clock.
      Also, the gpt on some i.MX have an additional ipg clock which can
      be gated. Request and enable this.
      Signed-off-by: NSascha Hauer <s.hauer@pengutronix.de>
      821dc4df
  12. 01 2月, 2012 1 次提交
  13. 19 12月, 2011 1 次提交
  14. 24 5月, 2011 1 次提交
  15. 19 5月, 2011 1 次提交
  16. 23 3月, 2011 2 次提交
  17. 23 12月, 2010 1 次提交
  18. 23 4月, 2010 1 次提交
  19. 22 4月, 2010 1 次提交
  20. 09 2月, 2010 1 次提交
  21. 14 8月, 2009 2 次提交
  22. 07 8月, 2009 1 次提交
  23. 07 5月, 2009 2 次提交
  24. 22 4月, 2009 1 次提交
  25. 13 3月, 2009 2 次提交
  26. 13 12月, 2008 1 次提交
  27. 07 8月, 2008 2 次提交
  28. 05 7月, 2008 1 次提交