All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: hongzha1 <hongzhan.chen@intel.com>, xenomai@xenomai.org
Subject: Re: [PATCH V2 3/3] testsuite/latmus: introduce latmus benchmark
Date: Fri, 16 Apr 2021 14:05:14 +0200	[thread overview]
Message-ID: <17adb9ac-7510-f1f6-9805-67ef8353b536@siemens.com> (raw)
In-Reply-To: <20210416053133.23412-4-hongzhan.chen@intel.com>

On 16.04.21 07:31, hongzha1 via Xenomai wrote:
> Measure response time to GPIO events sent by a remote Zephyr-based
> latency monitor (latmon). This monitor collects then sends the latency
> data over a network connection to the latmus front-end which displays
> the results received:
> 
> [Linux device under test running latmus]  <--+
>                                              |
>         ^                 | (GPIO ack)       |
>         |                 |                  |  TCP/IP network connection
>         |                 |                  |  (control & data samples)
>         | (GPIO pulse)    v                  |
>                                              |
> [Zephyr-based device running latmon]      <--+
> 
> The generic latency monitor code running the measurement loop is
> available from the zephyr/ directory. This support comes with a Zephyr
> device tree patch for enabling this monitor on NXP's FRDM-K64F
> development board.

Where is all this?

BTW, would some cheap Arduino board and sketch be an alternative? They
could expose the recorded data via USB to the host (even the DUT).
Provided they have enough free RAM to compensate the transfer delay.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux


  reply	other threads:[~2021-04-16 12:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  5:31 [PATCH V2 0/3] introduce latmus hongzha1
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 [this message]
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=17adb9ac-7510-f1f6-9805-67ef8353b536@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=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.