diff options
author | Marc Kleine-Budde <mkl@pengutronix.de> | 2023-01-11 11:48:16 +0100 |
---|---|---|
committer | Marc Kleine-Budde <mkl@pengutronix.de> | 2024-06-28 23:48:11 +0200 |
commit | e793c724b48ca8cae9693bc3be528e85284c126a (patch) | |
tree | 61809529d0d6046354a4bf441c657bbe3d82861c /drivers/nvme | |
parent | a7801540f325d104de5065850a003f1d9bdc6ad3 (diff) |
can: mcp251xfd: clarify the meaning of timestamp
The mcp251xfd chip is configured to provide a timestamp with each
received and transmitted CAN frame. The timestamp is derived from the
internal free-running timer, which can also be read from the TBC
register via SPI. The timer is 32 bits wide and is clocked by the
external oscillator (typically 20 or 40 MHz).
To avoid confusion, we call this timestamp "timestamp_raw" or "ts_raw"
for short.
Using the timecounter framework, the "ts_raw" is converted to 64 bit
nanoseconds since the epoch. This is what we call "timestamp".
This is a preparation for the next patches which use the "timestamp"
to work around a bug where so far only the "ts_raw" is used.
Tested-by: Stefan Althöfer <Stefan.Althoefer@janztec.com>
Tested-by: Thomas Kopp <thomas.kopp@microchip.com>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'drivers/nvme')
0 files changed, 0 insertions, 0 deletions