1. 31 Aug, 2018 2 commits
    • Philippe Gerum's avatar
      drivers/autotune: fix computation of gravity limit · 553881db
      Philippe Gerum authored
      A wrongly computed gravity limit value caused the calibration to end
      too early on some platforms (e.g. arm64).
      
      This value should be the max. among the set of min. latencies observed
      while running the warmup steps. In the same move, run more warmup
      steps to increase the likeliness of reaching such max.
      553881db
    • Philippe Gerum's avatar
      drivers/autotune: fix calibration with low frequency timers · 262cdf25
      Philippe Gerum authored
      When a single timer tick last less than the adjustment step time
      (i.e. < 500 ns), we end up with a zero adjustment value which either
      leads to a spurious early shot detection due to a rounding error, or a
      null gravity value at the end of a lengthy but useless calibration
      process.
      
      Make sure to adjust by at least one timer tick, and mitigate rounding
      errors when checking for early shots when the timer frequency is lower
      than 1e9 / ADJUSTMENT_STEP.
      262cdf25
  2. 28 Aug, 2018 1 commit
    • Philippe Gerum's avatar
      cobalt/arm64: calibrate: prevent excessive delay of next host tick · abd64d98
      Philippe Gerum authored
      The calibration procedure overwrites the current value of the timer
      counter for a pending oneshot tick event, which is admittedly ok in
      the context of initializing Cobalt. However, the previous
      implementation maxed the counter value, potentially causing excessive
      delay to the host waiting for the overwritten timer event.
      
      Use a shorter delay value when calibrating so that the next shot does
      not occur later than one jiffy after we left the calibration
      routine. One jiffy is also long enough for preventing the timer to
      ever fire while running the calibration loop.
      abd64d98
  3. 25 Aug, 2018 1 commit
  4. 22 Aug, 2018 1 commit
    • Philippe Gerum's avatar
      cobalt/arm: calibrate: prevent excessive delay of next host tick · 630f0a33
      Philippe Gerum authored
      The calibration procedure overwrites the current value of the timer
      counter for a pending oneshot tick event, which is admittedly ok in
      the context of initializing Cobalt. However, the previous
      implementation maxed the counter value, potentially causing excessive
      delay to the host waiting for the overwritten timer event.
      
      Use a shorter delay value when calibrating so that the next shot does
      not occur later than one jiffy after we left the calibration
      routine. One jiffy is also long enough for preventing the timer to
      ever fire while running the calibration loop.
      630f0a33
  5. 20 Aug, 2018 1 commit
  6. 01 Aug, 2018 6 commits
  7. 14 Jul, 2018 1 commit
  8. 03 Jul, 2018 27 commits