From: hongzha1 <hongzhan.chen@intel.com>
To: xenomai@xenomai.org
Subject: [PATCH V2 0/3] introduce latmus
Date: Fri, 16 Apr 2021 01:31:30 -0400 [thread overview]
Message-ID: <20210416053133.23412-1-hongzhan.chen@intel.com> (raw)
Latmus is a backport from EVL to Cobalt, the procedure is fully
described here: https://evlproject.org/core/benchmarks/
I verified all functions of latmus on hardware environment under which
Rock PI X board connect GPIOs with FRDM K64F.But actually Rock PI X V1.4
board's GPIO I/O voltage is 1.8V does not match 3.3V of FRDM K64F board.
Even though I tried to set up IO shifter board to bridge two boards,
still can not get correct latecny data because of bad IO signal. So I
have to work around to loopback Input/Output GPIOs on both boards to do
verify functions.
Hardware setup:
---------------------------------------------------
eth| |eth
+ +
FRDM K64F board Rock PI X board
| | | |
+_________+ +___________+
GPIO Loopback GPIO Loopback
hongzha1 (3):
rtdm/testing: latmus: introduce latmus driver
drivers/gpio: core: introduce helper to find gpiochip
testsuite/latmus: introduce latmus benchmark
configure.ac | 1 +
include/cobalt/kernel/rtdm/gpio.h | 3 +
include/rtdm/uapi/testing.h | 79 ++
kernel/drivers/gpio/gpio-core.c | 23 +
kernel/drivers/testing/Kconfig | 10 +
kernel/drivers/testing/Makefile | 1 +
kernel/drivers/testing/latmus.c | 1237 ++++++++++++++++++++++++
testsuite/Makefile.am | 4 +-
testsuite/latmus/Makefile.am | 18 +
testsuite/latmus/latmus.c | 1446 +++++++++++++++++++++++++++++
10 files changed, 2821 insertions(+), 1 deletion(-)
create mode 100644 kernel/drivers/testing/latmus.c
create mode 100644 testsuite/latmus/Makefile.am
create mode 100644 testsuite/latmus/latmus.c
--
2.17.1
next reply other threads:[~2021-04-16 5:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 5:31 hongzha1 [this message]
2021-04-16 5:31 ` [PATCH V2 1/3] rtdm/testing: latmus: introduce latmus driver hongzha1
2021-04-16 5:31 ` [PATCH V2 2/3] drivers/gpio: core: introduce helper to find gpiochip hongzha1
2021-04-16 5:31 ` [PATCH V2 3/3] testsuite/latmus: introduce latmus benchmark hongzha1
2021-04-16 12:05 ` Jan Kiszka
2021-04-20 1:02 ` Chen, Hongzhan
2021-04-20 6:47 ` Jan Kiszka
2021-04-20 7:30 ` Chen, Hongzhan
2021-04-20 8:27 ` Philippe Gerum
2021-04-16 12:03 ` [PATCH V2 0/3] introduce latmus Jan Kiszka
2021-04-20 1:10 ` Chen, Hongzhan
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=20210416053133.23412-1-hongzhan.chen@intel.com \
--to=hongzhan.chen@intel.com \
--cc=xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.