drivers/autotune: fix computation of gravity limit
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.
Showing with 11 additions and 11 deletions