diff options
| author | John Stultz <john.stultz@linaro.org> | 2015-05-13 15:13:04 -0700 |
|---|---|---|
| committer | Shuah Khan <shuahkh@osg.samsung.com> | 2015-05-26 15:58:07 -0600 |
| commit | acd5705d2d17a229b1aa0e549951ec66164b9379 (patch) | |
| tree | fbd21c4157f1c9697fb519eb338239791849c50a /tools | |
| parent | 859b1bebe1e0e2e1fdfec77b019b9d7c27588e02 (diff) | |
| download | linux-acd5705d2d17a229b1aa0e549951ec66164b9379.tar.gz linux-acd5705d2d17a229b1aa0e549951ec66164b9379.tar.bz2 linux-acd5705d2d17a229b1aa0e549951ec66164b9379.zip | |
kselftests: timers: Ease alarmtimer-suspend unreasonable latency value
On the hardware I have, resume latency from an alarm is often
2-3 seconds (with a fair amount of variability due to the RTC's
single second granularity). Having four seconds be the pass/fail
bar is maybe a little too tight, so extend this to 5 seconds.
Cc: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Richard Cochran <richardcochran@gmail.com>
Signed-off-by: John Stultz <john.stultz@linaro.org>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
Diffstat (limited to 'tools')
| -rw-r--r-- | tools/testing/selftests/timers/alarmtimer-suspend.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/testing/selftests/timers/alarmtimer-suspend.c b/tools/testing/selftests/timers/alarmtimer-suspend.c index 99a1ad331ac8..13586b68ef51 100644 --- a/tools/testing/selftests/timers/alarmtimer-suspend.c +++ b/tools/testing/selftests/timers/alarmtimer-suspend.c @@ -57,7 +57,7 @@ static inline int ksft_exit_fail(void) #define NSEC_PER_SEC 1000000000ULL -#define UNREASONABLE_LAT (NSEC_PER_SEC * 4) /* hopefully we resume in 4secs */ +#define UNREASONABLE_LAT (NSEC_PER_SEC * 5) /* hopefully we resume in 5 secs */ #define SUSPEND_SECS 15 int alarmcount; |