From: Pavel Pisa <pisa@cmp.felk.cvut.cz>
To: "Marc Kleine-Budde" <mkl@pengutronix.de>,
Oliver Hartkopp <socketcan@hartkopp.net>,
linux-can@vger.kernel.org
Cc: "Matej Vasilevski" <vasilmat@fel.cvut.cz>,
"Michal Simek" <michal.simek@xilinx.com>,
"Martin Jeřábek" <martin.jerabek01@gmail.com>
Subject: Query for status of timestamping for XCAN driver and possible project
Date: Wed, 20 Oct 2021 13:17:50 +0200 [thread overview]
Message-ID: <202110201317.50743.pisa@cmp.felk.cvut.cz> (raw)
Hello Oliver and Marc,
our student, Matej Vasilevski, has chosen to continue
on CAN latency tester which we done for Oliver years
ago.
We want to continue on the CAN-BENCH project started
by Martin Jerabek
https://gitlab.fel.cvut.cz/canbus/zynq/zynq-can-sja1000-top/-/wikis/home
https://gitlab.fel.cvut.cz/canbus/zynq/zynq-can-sja1000-top/-/wikis/uploads/56b4d27d8f81ae390fc98bdce803398f/F3-BP-2016-Jerabek-Martin-Jerabek-thesis-2016.pd
We want to use XCAN on Xilinx Zynq 7010 with timestamping
in the first iteration, then switch to our CTU CAN FD core
and add timestamping to its driver.
Is there some more recent attempt to add timestamping
to XCAN driver than that original work of Martin Jerabek?
Is there some suggestion which driver is the right
example to implement timestamping now?
Our intention is to implement feature in state ready
for mainlining and we hope that with your feedback
we succeed this time.
Best wishes,
Pavel Pisa
phone: +420 603531357
e-mail: pisa@cmp.felk.cvut.cz
Department of Control Engineering FEE CVUT
Karlovo namesti 13, 121 35, Prague 2
university: http://dce.fel.cvut.cz/
personal: http://cmp.felk.cvut.cz/~pisa
projects: https://www.openhub.net/accounts/ppisa
CAN related:http://canbus.pages.fel.cvut.cz/
next reply other threads:[~2021-10-20 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 11:17 Pavel Pisa [this message]
2021-10-20 11:34 ` Query for status of timestamping for XCAN driver and possible project Marc Kleine-Budde
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=202110201317.50743.pisa@cmp.felk.cvut.cz \
--to=pisa@cmp.felk.cvut.cz \
--cc=linux-can@vger.kernel.org \
--cc=martin.jerabek01@gmail.com \
--cc=michal.simek@xilinx.com \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--cc=vasilmat@fel.cvut.cz \
/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