On 18.07.2022 11:55:17, Pavel Pisa wrote: > 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. Can you model this as a standard clock 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. Ack, or via ACPI (but that's a different topic). regards, Marc -- Pengutronix e.K. | Marc Kleine-Budde | Embedded Linux | https://www.pengutronix.de | Vertretung West/Dortmund | Phone: +49-231-2826-924 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Attachment:
signature.asc
Description: PGP signature
