1. 18 Dec, 2018 2 commits
  2. 23 May, 2018 2 commits
  3. 14 Jun, 2017 1 commit
  4. 28 Jun, 2016 2 commits
  5. 15 Oct, 2015 1 commit
  6. 20 Aug, 2015 1 commit
  7. 10 Aug, 2015 1 commit
    • Viresh Kumar's avatar
      clockevents/drivers/timer-imx-gpt: Migrate to new 'set-state' interface · 26b91f04
      Viresh Kumar authored
      Migrate timer-imx-gpt driver to the new 'set-state' interface provided
      by clockevents core, the earlier 'set-mode' interface is marked obsolete
      now.
      
      This also enables us to implement callbacks for new states of clockevent
      devices, for example: ONESHOT_STOPPED.
      
      Also drop:
      - 'imx_timer.cem': It was caching the last state of the clockevent
        device. The same behavior can be achieved by using clockevents state
        helpers. These helpers are only required for oneshot mode as
        shutdown/resume wouldn't be done twice by the core.
      
      - 'clock_event_mode_label': CLOCK_EVT_MODE_* shouldn't be used anymore
        by drivers. The prints are modified to print the set-state functions
        name now to debug the driver.
      
      Cc: Shawn Guo <shawn.guo@linaro.org>
      Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
      Signed-off-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
      Signed-off-by: default avatarDaniel Lezcano <daniel.lezcano@linaro.org>
      26b91f04
  8. 07 Jul, 2015 1 commit
  9. 03 Jun, 2015 15 commits
  10. 16 Sep, 2014 1 commit
    • Anson Huang's avatar
      ARM: imx: source gpt per clk from OSC for system timer · bad3db10
      Anson Huang authored
      On i.MX6Q TO > 1.0, i.MX6DL and i.MX6SX, gpt per clock
      can be from OSC instead of ipg_per, as ipg_per's rate
      may be scaled when system enter low bus mode, to keep
      system timer NOT drift, better to make gpt per clock
      at fixed rate, here add support for gpt per clock to
      be from OSC which is at fixed rate always.
      
      There are some difference on this implementation of
      gpt per clock source, see below for details:
      
      i.MX6Q TO > 1.0: GPT_CR_CLKSRC, b'101 selects fix clock
          of OSC / 8 for gpt per clk;
      i.MX6DL and i.MX6SX: GPT_CR_CLKSRC, b'101 selects OSC
          for gpt per clk, and we must enable GPT_CR_24MEM to
          enable OSC clk source for gpt per, GPT_PR_PRESCALER24M
          is for pre-scaling of this OSC clk, here set it to 8
          to make gpt per clk is 3MHz;
      i.MX6SL: ipg_per can be from OSC directly, so no need to
          implement this new clk source for gpt per.
      Signed-off-by: default avatarAnson Huang <b20788@freescale.com>
      Signed-off-by: default avatarShawn Guo <shawn.guo@freescale.com>
      bad3db10
  11. 18 Jul, 2014 3 commits
  12. 30 Apr, 2014 1 commit
  13. 05 Mar, 2014 1 commit
  14. 21 Nov, 2013 1 commit
  15. 21 Oct, 2013 1 commit
  16. 12 Jun, 2013 1 commit
  17. 30 Jan, 2013 1 commit
    • Shawn Guo's avatar
      ARM: imx: return zero in case next event gets a large increment · eea8e326
      Shawn Guo authored
      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: default avatarShawn Guo <shawn.guo@linaro.org>
      eea8e326
  18. 14 Jan, 2013 1 commit
  19. 15 Oct, 2012 3 commits