[PATCH v1 0/1] can: ctucanfd: Update CTU CAN FD IP core registers to match version 3.x.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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




[Index of Archives]     [Automotive Discussions]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [CAN Bus]

  Powered by Linux