linux-dev/kernel/time/udelay_test.c, branch linus/masterLinux kernel development work - see feature brancheshttps://git.zx2c4.com/linux-dev/atom/kernel/time/udelay_test.c?h=linus%2Fmaster2014-11-21T19:59:55Ztime: Rename udelay_test.c to test_udelay.c2014-11-21T19:59:55ZJohn Stultzjohn.stultz@linaro.org2014-08-04T18:30:56Zurn:sha1:fd866e2b116b01d42428491899fe9925c42c121c
Kees requested that this test module be renamed for consistency sake,
so this patch renames the udelay_test.c file (recently added to
tip/timers/core for 3.17) to test_udelay.c
Cc: Kees Cook <keescook@chromium.org>
Cc: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Linux-Next <linux-next@vger.kernel.org>
Cc: David Riley <davidriley@chromium.org>
Signed-off-by: John Stultz <john.stultz@linaro.org>
kernel: time: Add udelay_test module to validate udelay2014-07-23T17:16:35ZDavid Rileydavidriley@chromium.org2014-06-16T21:58:32Zurn:sha1:e704f93af5a083c07b8f722672d63a1d908daf55
Create a module that allows udelay() to be executed to ensure that
it is delaying at least as long as requested (with a little bit of
error allowed).
There are some configurations which don't have reliably udelay
due to using a loop delay with cpufreq changes which should use
a counter time based delay instead. This test aims to identify
those configurations where timing is unreliable.
Signed-off-by: David Riley <davidriley@chromium.org>
Signed-off-by: John Stultz <john.stultz@linaro.org>