Lines Matching refs:time

8   monotonic) system time. Reports the timestamp via recvmsg() in a
143   The counter starts at zero. It is initialized the first time that
144   the socket option is enabled. It is reset each time the option is
231 send time with the value returned for each timestamp. It can prevent
263 feature. Only one field is non-zero at any time. Most timestamps
266 ts[1] used to hold hardware timestamps converted to system time.
268 a HW PTP clock source, to allow time conversion in userspace and
269 optionally synchronize system time with a userspace PTP stack such
344 Hardware time stamping must also be initialized for each device driver
345 that is expected to do hardware time stamping. The parameter is defined in
359 supported, the driver may time stamp more than just the requested types
369 A driver which supports hardware time stamping shall update the struct
371 requested packets cannot be time stamped, then nothing should be
386 	 * no outgoing packet will need hardware time stamping;
388 	 * time stamping will be done
393 	 * enables hardware time stamping for outgoing packets;
395 	 * time stamped by setting SOF_TIMESTAMPING_TX_SOFTWARE
403 	/* time stamp no incoming packet at all */
406 	/* time stamp any incoming packet */
409 	/* return value: time stamp all packets requested plus some others */
422 A driver which supports hardware time stamping must support the
428 to the shared time stamp structure of the skb call skb_hwtstamps(). Then
429 set the time stamps in the structure:
432 	/* hardware time stamp transformed into duration
433 	 * since arbitrary point in time
440   is set no-zero. If yes, then the driver is expected to do hardware time
443   that the driver is doing the time stamping by setting the flag
449   and not free the skb. A driver not supporting hardware time stamping doesn't
451   software generated time stamps by the network subsystem.
453   as possible. skb_tx_timestamp() provides a software time stamp if requested
456   hardware time stamp for it, it passes the time stamp back by
458   hardware time stamp. skb_hwtstamp_tx() clones the original skb and
460   If obtaining the hardware time stamp somehow fails, then the driver
461   should not fall back to software time stamping. The rationale is that
462   this would occur at a later time in the processing pipeline than other
463   software time stamping and therefore could lead to unexpected deltas
464   between time stamps.