From: Pavel Pisa <pisa@cmp.felk.cvut.cz>
To: linux-can@vger.kernel.org,
"Marc Kleine-Budde" <mkl@pengutronix.de>,
Matej Vasilevski <matej.vasilevski@seznam.cz>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
David Miller <davem@davemloft.net>,
Carsten Emde <c.emde@osadl.org>,
Marin Jerabek <martin.jerabek01@gmail.com>,
Ondrej Ille <ondrej.ille@gmail.com>,
Jiri Novak <jnovak@fel.cvut.cz>,
Pavel Pisa <pisa@cmp.felk.cvut.cz>
Subject: [PATCH v1 0/1] can: ctucanfd: Update CTU CAN FD IP core registers to match version 3.x.
Date: Mon, 18 Jul 2022 11:55:17 +0200 [thread overview]
Message-ID: <cover.1658136506.git.pisa@cmp.felk.cvut.cz> (raw)
The 3.x CTU CAN FD IP core version provides informative fields
with number of Tx registers count and most significant active
(toggling) timestamp base bit.
The fields are read as zero for older 2.x IP core version.
The 4 Tx buffers and bit 63 MSB can be considered in such
case and compatibility with 2.x core version is preserved.
This change allows to update Matej Vasilevski's patch series
[RFC] can: ctucanfd: RX timestamping implementation
to work with the platform bus and PCIe core integration
without need of additional mandatory parameters.
Only optional one for timestamp clock frequency can be
used when bitrate base clock and timestamp clocks differ.
ts-frequency:
description: |
Frequency of the timestamping counter. Set this if you want to get
timestamps, but you didn't set the timestamping clock in clocks property.
The information about clocks frequencies on PCIe integration
has to be provided by other means but we expect that it can
be directly deduced from Vendor and Device IDs and corresponding
device table.
Pavel Pisa (1):
can: ctucanfd: Update CTU CAN FD IP core registers to match version
3.x.
This patch is intended for 5.20 kernel version but possible postpone
to 5.21 is not big problem.
It would be ideal to include even ctucanfd timestamping in 5.20
but timing for updates and reviews is probably quite tight.
drivers/net/can/ctucanfd/ctucanfd_kregs.h | 32 ++++++++++++++++++++---
1 file changed, 28 insertions(+), 4 deletions(-)
--
2.20.1
next reply other threads:[~2022-07-18 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 9:55 Pavel Pisa [this message]
2022-07-18 9:55 ` [PATCH v1 1/1] can: ctucanfd: Update CTU CAN FD IP core registers to match version 3.x Pavel Pisa
2022-07-18 10:02 ` Marc Kleine-Budde
2022-07-18 10:00 ` [PATCH v1 0/1] " Marc Kleine-Budde
2022-07-18 10:26 ` [PATCH v2 1/1] " Pavel Pisa
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=cover.1658136506.git.pisa@cmp.felk.cvut.cz \
--to=pisa@cmp.felk.cvut.cz \
--cc=c.emde@osadl.org \
--cc=davem@davemloft.net \
--cc=jnovak@fel.cvut.cz \
--cc=linux-can@vger.kernel.org \
--cc=martin.jerabek01@gmail.com \
--cc=matej.vasilevski@seznam.cz \
--cc=mkl@pengutronix.de \
--cc=ondrej.ille@gmail.com \
--cc=socketcan@hartkopp.net \
/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