Lines Matching full:nanoseconds

19  * nanoseconds the cyclecounter and timecounter structures are
84 * which contain measurements of seconds and nanoseconds respectively. This
89 * represents units of 2^-32 nanoseconds, and uses 31 bits for this, with the
92 * of 12 to 13 nanoseconds adjustment. Unlike the 82599 and X540 devices, the
103 * seconds, 32 bits for nanoseconds (largest value is 0d999999999 or just under
125 * 12.5 nanoseconds. This means that the Max ppb is 39999999
127 * register can only hold slightly under 0.5 nanoseconds.
136 * proper mult and shift to convert the cycles into nanoseconds of time.
203 /* Figure out how many nanoseconds to add to round the clock edge up in ixgbe_ptp_setup_sdp_X540()
286 /* Figure out how many nanoseconds to add to round the clock edge up in ixgbe_ptp_setup_sdp_X550()
296 * nanoseconds. However, we can use the math from a timespec64 to in ixgbe_ptp_setup_sdp_X550()
321 * structure to convert from internal representation into nanoseconds. We need
324 * "cycles", rather than seconds and nanoseconds.
335 * cycles are not guaranteed to be nanoseconds. The timespec64 created in ixgbe_ptp_read_X550()
405 * and nanoseconds counter, instead of raw 64bits nanoseconds. We need in ixgbe_ptp_convert_to_hwtstamp()
409 * not represent seconds/nanoseconds. Instead it can be thought of as in ixgbe_ptp_convert_to_hwtstamp()
1173 * to nanoseconds using only a multiplier and a right-shift, in ixgbe_ptp_link_speed_adjust()
1235 * designed to represent seconds and nanoseconds when this is in ixgbe_ptp_start_cyclecounter()