Home
last modified time | relevance | path

Searched refs:timestamps (Results 1 – 25 of 78) sorted by relevance

1234

/kernel/linux/linux-5.10/Documentation/networking/
Dtimestamping.rst11 The interfaces for receiving network packages timestamps are:
37 Generates timestamps on reception, transmission or both. Supports
39 timestamps for stream sockets.
55 SO_TIMESTAMP_OLD returns incorrect timestamps after the year 2038
61 Its struct timespec allows for higher resolution (ns) timestamps than the
67 SO_TIMESTAMPNS_OLD returns incorrect timestamps after the year 2038
90 Some bits are requests to the stack to try to generate timestamps. Any
93 is possible to selectively request timestamps for a subset of packets
101 Request rx timestamps generated by the network adapter.
104 Request rx timestamps when data enters the kernel. These timestamps
[all …]
/kernel/linux/linux-5.10/tools/lib/traceevent/Documentation/
Dlibtraceevent-set_flag.txt60 /* Print timestamps in nanoseconds */
64 /* print timestamps in nanoseconds */
66 /* print timestamps in microseconds */
69 /* Print timestamps in microseconds */
Dlibtraceevent-header_page.txt29 The _tep_get_header_timestamp_size()_ function returns the size of timestamps,
41 The _tep_get_header_timestamp_size()_ function returns the size of timestamps,
67 printf("The timestamps size is %d bytes.\n", timesize);
/kernel/linux/linux-5.10/drivers/staging/media/meson/vdec/
Dvdec_helpers.c246 list_add_tail(&new_ts->list, &sess->timestamps); in amvdec_add_ts()
258 list_for_each_entry(tmp, &sess->timestamps, list) { in amvdec_remove_ts()
328 struct list_head *timestamps = &sess->timestamps; in amvdec_dst_buf_done() local
335 if (list_empty(timestamps)) { in amvdec_dst_buf_done()
344 tmp = list_first_entry(timestamps, struct amvdec_timestamp, list); in amvdec_dst_buf_done()
372 list_for_each_entry_safe(tmp, n, &sess->timestamps, list) { in amvdec_dst_buf_done_offset()
Dvdec.h264 struct list_head timestamps; member
/kernel/linux/linux-5.10/Documentation/sound/designs/
Dtimestamping.rst5 The ALSA API can provide two different system timestamps:
23 timestamps allow for applications to keep track of the 'fullness' of
33 When timestamps are enabled, the avail/delay information is reported
111 counter-intuitively not increase the precision of timestamps, e.g. if a
129 timestamps from hardware registers or from IPC takes time, the more
130 timestamps are read the more imprecise the combined measurements
132 timestamp is reported. Applications that need different timestamps
185 error. In example 3 where the timestamps are measured with the link
186 wallclock, the timestamps show a monotonic behavior and a lower
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-ptp91 timestamps. To enable external timestamps, write the
93 To disable external timestamps, write the channel
100 This file provides timestamps on external events, in
/kernel/linux/linux-5.10/Documentation/kbuild/
Dreproducible-builds.rst19 The kernel embeds timestamps in three places:
24 * File timestamps in the embedded initramfs
26 * If enabled via ``CONFIG_IKHEADERS``, file timestamps of kernel
/kernel/linux/linux-5.10/drivers/net/ethernet/sfc/
Dptp.c1136 struct skb_shared_hwtstamps timestamps; in efx_ptp_xmit_skb_mc() local
1165 memset(&timestamps, 0, sizeof(timestamps)); in efx_ptp_xmit_skb_mc()
1166 timestamps.hwtstamp = ptp_data->nic_to_kernel_time( in efx_ptp_xmit_skb_mc()
1171 skb_tstamp_tx(skb, &timestamps); in efx_ptp_xmit_skb_mc()
1234 struct skb_shared_hwtstamps *timestamps; in efx_ptp_match_rx() local
1237 timestamps = skb_hwtstamps(skb); in efx_ptp_match_rx()
1238 timestamps->hwtstamp = evt->hwtimestamp; in efx_ptp_match_rx()
2043 struct skb_shared_hwtstamps *timestamps; in __efx_rx_skb_attach_timestamp() local
2086 timestamps = skb_hwtstamps(skb); in __efx_rx_skb_attach_timestamp()
2087 timestamps->hwtstamp = in __efx_rx_skb_attach_timestamp()
/kernel/linux/linux-5.10/Documentation/core-api/
Dtimekeeping.rst20 Useful for reliable timestamps and measuring short time intervals
37 user space. This is used for all timestamps that need to
126 but can't easily use 'jiffies', e.g. for inode timestamps.
/kernel/linux/linux-5.10/drivers/net/ethernet/marvell/octeontx2/nic/
Dotx2_txrx.h94 struct qmem *timestamps; member
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/
Dstreaming-par.rst19 not augmented by timestamps or sequence counters, and to avoid
Dpixfmt-meta-uvc.rst18 timing information, required for precise interpretation of timestamps, contained
Drw.rst20 counters or timestamps are passed. This information is necessary to
/kernel/linux/linux-5.10/Documentation/filesystems/
Dcramfs.rst38 No timestamps are stored in a cramfs, so these default to the epoch
39 (1970 GMT). Recently-accessed files may have updated timestamps, but
/kernel/linux/linux-5.10/Documentation/driver-api/
Dioctl.rst87 Traditionally, timestamps and timeout values are passed as ``struct
104 Timeout values and timestamps should ideally use CLOCK_MONOTONIC time,
106 CLOCK_REALTIME, this makes the timestamps immune from jumping backwards
109 ktime_get_real_ns() can be used for CLOCK_REALTIME timestamps that
/kernel/linux/linux-5.10/tools/power/pm-graph/config/
Dstandby.cfg88 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dfreeze.cfg88 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dfreeze-callgraph.cfg89 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dsuspend-x2-proc.cfg88 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dsuspend-dev.cfg88 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dstandby-callgraph.cfg89 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dfreeze-dev.cfg88 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dsuspend-callgraph.cfg93 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
/kernel/linux/linux-5.10/fs/cramfs/
DKconfig10 16/32 bits uid/gid, hard links and timestamps.

1234