/linux-4.4.14/Documentation/networking/ |
D | timestamping.txt | 4 The interfaces for receiving network packages timestamps are: 20 Generates timestamps on reception, transmission or both. Supports 22 timestamps for stream sockets. 38 Its struct timespec allows for higher resolution (ns) timestamps than the 55 Some bits are requests to the stack to try to generate timestamps. Any 58 is possible to selectively request timestamps for a subset of packets 66 Request rx timestamps generated by the network adapter. 69 Request rx timestamps when data enters the kernel. These timestamps 74 Request tx timestamps generated by the network adapter. 77 Request tx timestamps when data leaves the kernel. These timestamps [all …]
|
D | packet_mmap.txt | 217 related meta-information like timestamps without requiring a system call. 1014 hardware timestamps to be used. Note: you may need to enable the generation 1015 of hardware timestamps with SIOCSHWTSTAMP (see related information from 1023 For the mmap(2)ed ring buffers, such timestamps are stored in the 1036 Getting timestamps for the TX_RING works as follows: i) fill the ring frames, 1039 through the frames to pick up the individual hw/sw timestamps. 1054 for more information on hardware timestamps.
|
D | stmmac.txt | 96 are used for saving the hardware timestamps and Extended Status.
|
D | ip-sysctl.txt | 595 Enable timestamps as defined in RFC1323.
|
/linux-4.4.14/drivers/iio/imu/inv_mpu6050/ |
D | inv_mpu_ring.c | 33 kfifo_reset(&st->timestamps); in inv_clear_kfifo() 111 kfifo_in_spinlocked(&st->timestamps, ×tamp, 1, in inv_mpu6050_irq_handler() 160 if (kfifo_len(&st->timestamps) > in inv_mpu6050_read_fifo() 170 result = kfifo_out(&st->timestamps, ×tamp, 1); in inv_mpu6050_read_fifo()
|
D | inv_mpu_iio.h | 127 DECLARE_KFIFO(timestamps, long long, TIMESTAMP_FIFO_SIZE);
|
D | inv_mpu_core.c | 837 INIT_KFIFO(st->timestamps); in inv_mpu_probe()
|
/linux-4.4.14/Documentation/sound/alsa/ |
D | timestamping.txt | 1 The ALSA API can provide two different system timestamps: 19 timestamps allow for applications to keep track of the 'fullness' of 29 When timestamps are enabled, the avail/delay information is reported 106 counter-intuitively not increase the precision of timestamps, e.g. if a 124 timestamps from hardware registers or from IPC takes time, the more 125 timestamps are read the more imprecise the combined measurements 127 timestamp is reported. Applications that need different timestamps 174 error. In example 3 where the timestamps are measured with the link 175 wallclock, the timestamps show a monotonic behavior and a lower
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-ptp | 91 timestamps. To enable external timestamps, write the 93 To disable external timestamps, write the channel 100 This file provides timestamps on external events, in
|
D | sysfs-bus-coresight-devices-etm4x | 116 Description: (RW) Controls the insertion of global timestamps in the trace
|
/linux-4.4.14/drivers/net/ethernet/sfc/ |
D | ptp.c | 882 struct skb_shared_hwtstamps timestamps; in efx_ptp_xmit_skb() local 911 memset(×tamps, 0, sizeof(timestamps)); in efx_ptp_xmit_skb() 912 timestamps.hwtstamp = ptp_data->nic_to_kernel_time( in efx_ptp_xmit_skb() 917 skb_tstamp_tx(skb, ×tamps); in efx_ptp_xmit_skb() 982 struct skb_shared_hwtstamps *timestamps; in efx_ptp_match_rx() local 985 timestamps = skb_hwtstamps(skb); in efx_ptp_match_rx() 986 timestamps->hwtstamp = evt->hwtimestamp; in efx_ptp_match_rx() 1750 struct skb_shared_hwtstamps *timestamps; in __efx_rx_skb_attach_timestamp() local 1792 timestamps = skb_hwtstamps(skb); in __efx_rx_skb_attach_timestamp() 1793 timestamps->hwtstamp = in __efx_rx_skb_attach_timestamp()
|
/linux-4.4.14/Documentation/filesystems/ |
D | cramfs.txt | 35 No timestamps are stored in a cramfs, so these default to the epoch 36 (1970 GMT). Recently-accessed files may have updated timestamps, but
|
D | vfat.txt | 107 tz=UTC -- Interpret timestamps as UTC rather than local time. 108 This option disables the conversion of timestamps 115 -- Set offset for conversion of timestamps from local time
|
D | relay.txt | 277 the need to bother with saving explicit timestamps for the purpose of
|
D | ext4.txt | 89 * nsec timestamps for mtime, atime, ctime, create time
|
/linux-4.4.14/fs/cramfs/ |
D | Kconfig | 10 16/32 bits uid/gid, hard links and timestamps.
|
/linux-4.4.14/Documentation/sysctl/ |
D | net.txt | 104 Allow processes to receive tx timestamps looped together with the original 180 If set to 0, RX packet timestamps can be sampled after RPS processing, when 181 the target CPU processes packets. It might give some delay on timestamps, but 184 If set to 1 (default), timestamps are sampled as soon as possible, before
|
/linux-4.4.14/Documentation/fmc/ |
D | parameters.txt | 42 golden gateware for the SPEC card, removing the leading timestamps to
|
/linux-4.4.14/drivers/media/rc/img-ir/ |
D | Kconfig | 16 less reliable (due to lack of timestamps) and consumes more
|
/linux-4.4.14/Documentation/device-mapper/ |
D | statistics.txt | 66 milliseconds. Precise timestamps are a little bit slower 67 to obtain than jiffies-based timestamps.
|
/linux-4.4.14/Documentation/timers/ |
D | timekeeping.txt | 119 for example. It is also used for printk timestamps when you have selected to 139 events on the system. However it may result in interesting timestamps in
|
/linux-4.4.14/tools/perf/Documentation/ |
D | perf-record.txt | 188 Record the sample timestamps. Use it with 'perf report -D' to see the 189 timestamps, for instance.
|
/linux-4.4.14/net/ipv4/ |
D | tcp_metrics.c | 580 bool paws_check, bool timestamps) in tcp_peer_is_proven() argument 594 !timestamps)) in tcp_peer_is_proven()
|
/linux-4.4.14/Documentation/video4linux/cx2341x/ |
D | fw-encoder-api.txt | 243 And in older firmwares the timestamps in the TS seem to be 690 4=generate DVD compatible PTS timestamps
|
/linux-4.4.14/fs/squashfs/ |
D | Kconfig | 13 timestamps.
|
/linux-4.4.14/Documentation/pps/ |
D | pps.txt | 52 useful besides(!) the gathering of timestamps as it is the central
|
/linux-4.4.14/Documentation/input/ |
D | input.txt | 228 generated in the kernel straight to the program, with timestamps. The
|
/linux-4.4.14/Documentation/ioctl/ |
D | botching-up-ioctls.txt | 130 v4l use by default nowadays. But let userspace know which timestamps are
|
/linux-4.4.14/include/net/ |
D | tcp.h | 420 bool paws_check, bool timestamps);
|
/linux-4.4.14/Documentation/filesystems/cifs/ |
D | CHANGES | 111 architectures. Fix problems with preserving timestamps on copying open
|
/linux-4.4.14/Documentation/trace/ |
D | ftrace.txt | 119 or events work (stack traces, timestamps, etc).
|