On Fri, May 19, 2017 at 11:52 AM, Miroslav Lichvar <mlich...@redhat.com> wrote: > Add SOF_TIMESTAMPING_OPT_TX_SWHW option to allow an outgoing packet to > be looped to the socket's error queue with a software timestamp even > when a hardware transmit timestamp is expected to be provided by the > driver. > > Applications using this option will receive two separate messages from > the error queue, one with a software timestamp and the other with a > hardware timestamp. As the hardware timestamp is saved to the shared skb > info, which may happen before the first message with software timestamp > is received by the application, the hardware timestamp is copied to the > SCM_TIMESTAMPING control message only when the skb has no software > timestamp or it is an incoming packet. > > While changing sw_tx_timestamp(), inline it in skb_tx_timestamp() as > there are no other users. > > CC: Richard Cochran <richardcoch...@gmail.com> > CC: Willem de Bruijn <will...@google.com> > Signed-off-by: Miroslav Lichvar <mlich...@redhat.com>
Acked-by: Willem de Bruijn <will...@google.com>
