diff options
| author | Willem de Bruijn <willemb@google.com> | 2014-07-14 23:55:30 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2014-07-16 01:32:45 +0200 |
| commit | 26c4fdb0528ae7c4be9fbc8a8210f3b410e6b5aa (patch) | |
| tree | fdbf59a354779f01dac0732fa033d5d8a721c399 /drivers/net/can | |
| parent | net-timestamp: SOCK_RAW and PING timestamping (diff) | |
| download | linux-26c4fdb0528ae7c4be9fbc8a8210f3b410e6b5aa.tar.xz linux-26c4fdb0528ae7c4be9fbc8a8210f3b410e6b5aa.zip | |
net-timestamp: document deprecated syststamp
The SO_TIMESTAMPING API defines option SOF_TIMESTAMPING_SYS_HW.
This feature is deprecated. It should not be implemented by new
device drivers. Existing drivers do not implement it, either --
with one exception.
Driver developers are encouraged to expose the NIC hw clock as a
PTP HW clock source, instead, and synchronize system time to the
HW source.
The control flag cannot be removed due to being part of the ABI, nor
can the structure scm_timestamping that is returned. Due to the one
legacy driver, the internal datapath and structure are not removed.
This patch only clearly marks the interface as deprecated. Device
drivers should always return a syststamp value of zero.
Signed-off-by: Willem de Bruijn <willemb@google.com>
----
We can consider adding a WARN_ON_ONCE in__sock_recv_timestamp
if non-zero syststamp is encountered
Acked-by: Richard Cochran <richardcochran@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/can')
0 files changed, 0 insertions, 0 deletions