409c188c57
Currently, some CAN drivers support hardware timestamping, some do not. But userland has no method to query which features are supported (aside maybe of getting RX messages and observe whether or not hardware timestamps stay at zero). The canonical way for a network driver to advertised what kind of timestamping it supports is to implement ethtool_ops::get_ts_info(). This patch only targets the CAN drivers which *do not* support hardware timestamping. For each of those CAN drivers, implement the get_ts_info() using the generic ethtool_op_get_ts_info(). This way, userland can do: | $ ethtool --show-time-stamping canX to confirm the device timestamping capacities. N.B. the drivers which support hardware timestamping will be migrated in separate patches. Signed-off-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr> Link: https://lore.kernel.org/all/20220727101641.198847-6-mailhol.vincent@wanadoo.fr [mkl: mscan: add missing mscan_ethtool_ops] Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| ems_pci.c | ||
| ems_pcmcia.c | ||
| f81601.c | ||
| kvaser_pci.c | ||
| peak_pci.c | ||
| peak_pcmcia.c | ||
| plx_pci.c | ||
| sja1000.c | ||
| sja1000.h | ||
| sja1000_isa.c | ||
| sja1000_platform.c | ||
| tscan1.c | ||