From: David Riley <davidriley@chromium.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: John Stultz <john.stultz@linaro.org>,
Doug Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org,
David Riley <davidriley@chromium.org>
Subject: [PATCH v2 0/2] Add test to validate udelay
Date: Wed, 14 May 2014 15:30:15 -0700 [thread overview]
Message-ID: <1400106617-17085-1-git-send-email-davidriley@chromium.org> (raw)
In-Reply-To: <1399421543-7751-1-git-send-email-davidriley@chromium.org>
This change adds a module and a script that makes use of it to
validate that udelay delays for at least as long as requested
(as compared to ktime).
Changes since v1:
- allow udelay() to be 0.5% faster than requested as per feedback
David Riley (2):
kernel: time: Add udelay_test module to validate udelay
tools: add script to test udelay
kernel/time/Kconfig | 7 ++
kernel/time/Makefile | 1 +
kernel/time/udelay_test.c | 169 +++++++++++++++++++++++++++++++++++++++++++++
tools/time/udelay_test.sh | 66 ++++++++++++++++++
4 files changed, 243 insertions(+)
create mode 100644 kernel/time/udelay_test.c
create mode 100644 tools/time/udelay_test.sh
--
1.7.9.5
next prev parent reply other threads:[~2014-05-14 22:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 0:12 [PATCH " David Riley
2014-05-07 0:12 ` [PATCH 1/2] kernel: time: Add udelay_test module " David Riley
2014-05-07 0:12 ` [PATCH 2/2] tools: add script to test udelay David Riley
2014-05-14 22:49 ` Doug Anderson
2014-05-07 0:25 ` [PATCH 0/2] Add test to validate udelay John Stultz
2014-05-07 4:19 ` Doug Anderson
2014-05-07 17:02 ` David Riley
2014-05-07 18:10 ` John Stultz
2014-05-07 18:32 ` Doug Anderson
2014-05-07 22:46 ` John Stultz
2014-05-07 23:54 ` Doug Anderson
2014-05-14 22:30 ` David Riley [this message]
2014-05-14 22:30 ` [PATCH v2 1/2] kernel: time: Add udelay_test module " David Riley
2014-05-14 22:30 ` [PATCH v2 2/2] tools: add script to test udelay David Riley
2014-06-09 23:41 ` [PATCH v2 0/2] Add test to validate udelay David Riley
2014-06-11 16:59 ` John Stultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1400106617-17085-1-git-send-email-davidriley@chromium.org \
--to=davidriley@chromium.org \
--cc=dianders@chromium.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®