/linux/drivers/gpu/drm/amd/display/dc/link/accessories/ |
H A D | link_dp_trace.c | 110 link->dp_trace.detect_lt_trace.timestamps.start = dm_get_timestamp(link->dc->ctx); in dp_trace_set_lt_start_timestamp() 112 link->dp_trace.commit_lt_trace.timestamps.start = dm_get_timestamp(link->dc->ctx); in dp_trace_set_lt_start_timestamp() 119 link->dp_trace.detect_lt_trace.timestamps.end = dm_get_timestamp(link->dc->ctx); in dp_trace_set_lt_end_timestamp() 121 link->dp_trace.commit_lt_trace.timestamps.end = dm_get_timestamp(link->dc->ctx); in dp_trace_set_lt_end_timestamp() 128 return link->dp_trace.detect_lt_trace.timestamps.end; in dp_trace_get_lt_end_timestamp() 130 return link->dp_trace.commit_lt_trace.timestamps.end; in dp_trace_get_lt_end_timestamp()
|
/linux/Documentation/sound/designs/ |
H A D | timestamping.rst | 5 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
|
/linux/drivers/net/ethernet/intel/ice/ |
H A D | ice_ptp.c | 232 * @on: bool value for whether timestamps are enabled or disabled 288 /* Trigger an immediate software interrupt to ensure that timestamps in ice_ptp_restore_timestamp_mode() 298 * @sts: Optional parameter for holding a pair of system timestamps from 323 * system timestamps in ice_ptp_read_src_clk_reg() 339 * Hardware captures timestamps which contain only 32 bits of nominal 340 * nanoseconds, as opposed to the 64bit timestamps that the stack expects. 406 * The Tx and Rx timestamps are 40 bits wide, including 32 bits of nominal 444 * ice_ptp_is_tx_tracker_up - Check if Tx tracker is ready for new timestamps 482 /* Count the number of Tx timestamps that timed out */ in ice_ptp_req_tx_single_tstamp() 596 * ice_ptp_process_tx_tstamp - Process Tx timestamps for a port [all …]
|
H A D | ice_ptp.h | 12 /* The ice hardware captures Tx hardware timestamps in the PHY. The timestamp 30 * devices. In E810 devices, each port has its own block of timestamps, while in 78 * been captured. This avoids reporting stale timestamps to the stack. This is 90 * @ICE_TX_TSTAMP_WORK_PENDING: More Tx timestamps are pending 102 * @stale: bitmap of len to indicate slots which have stale timestamps 103 * @block: which memory block (quad or port) the timestamps are captured in 108 * window, timestamps are temporarily disabled.
|
/linux/Documentation/devicetree/bindings/timestamp/ |
H A D | hte-consumer.yaml | 15 timestamps: 30 timestamp-names: [ timestamps ] 37 timestamps = <&tegra_hte_aon 0x9>, <&tegra_hte_lic 0x19>;
|
/linux/block/ |
H A D | bfq-wf2q.c | 12 * bfq_gt - compare two timestamps. 104 * entity, then compare timestamps to decide whether in bfq_update_next_in_service() 783 * NOTE: this can be optimized, as the timestamps of upper level entities 871 * (virtual) finish timestamps may happen to become lower and in bfq_update_fin_time_enqueue() 875 * higher timestamps happen to be busy, then the backshifted in bfq_update_fin_time_enqueue() 876 * timestamps of the former queues can become much lower than in bfq_update_fin_time_enqueue() 878 * higher timestamps while the ones with lower timestamps are in bfq_update_fin_time_enqueue() 880 * higher values than the finish timestamps of the idle in bfq_update_fin_time_enqueue() 881 * queues. As a consequence, the finish timestamps of all new in bfq_update_fin_time_enqueue() 883 * those of lucky queues with backshifted timestamps. The in bfq_update_fin_time_enqueue() [all …]
|
/linux/include/linux/platform_data/ |
H A D | cros_ec_sensorhub.h | 134 * The timestamps reported from the EC have low jitter. 135 * Timestamps also come before every sample. Set either 139 * time to AP time accidentally puts timestamps in 140 * the future. These timestamps are clamped to
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-ptp | 111 timestamps. To enable external timestamps, write the 113 To disable external timestamps, write the channel 120 This file provides timestamps on external events, in
|
/linux/drivers/net/dsa/sja1105/ |
H A D | sja1105_ptp.h | 11 /* Timestamps are in units of 8 ns clock ticks (equivalent to 72 u64 corrclk4ts; /* use the corrected clock for timestamps */ 78 /* Used only on SJA1105 to reconstruct partial timestamps */ 81 * 2-step TX timestamps
|
/linux/Documentation/kbuild/ |
H A D | reproducible-builds.rst | 16 Timestamps chapter 19 The kernel embeds timestamps in three places: 24 * File timestamps in the embedded initramfs 26 * If enabled via ``CONFIG_IKHEADERS``, file timestamps of kernel
|
/linux/tools/testing/selftests/tty/ |
H A D | tty_tstamp_update.c | 91 /* We wrote to the terminal so timestamps should have been updated */ in main() 94 ksft_print_msg("tty timestamps not updated\n"); in main() 99 "timestamps of terminal '%s' updated after write to /dev/tty\n", tty); in main()
|
/linux/drivers/staging/media/meson/vdec/ |
H A D | vdec_helpers.c | 246 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()
|
H A D | vdec.h | 220 * @timestamps: chronological list of src timestamps 221 * @ts_spinlock: spinlock for the timestamps list 273 struct list_head timestamps; member
|
/linux/include/linux/usb/ |
H A D | midi-v2.h | 41 …ne USB_MS_MIDI_PROTO_1_0_64_JRTS 0x02 /* MIDI 1.0, UMP up to 64bits, Jitter Reduction Timestamps */ 43 … USB_MS_MIDI_PROTO_1_0_128_JRTS 0x04 /* MIDI 1.0, UMP up to 128bits, Jitter Reduction Timestamps */ 45 #define USB_MS_MIDI_PROTO_2_0_JRTS 0x12 /* MIDI 2.0, Jitter Reduction Timestamps */
|
/linux/drivers/net/ethernet/sfc/siena/ |
H A D | ptp.c | 19 * Packets not matching are delivered without timestamps (MCDI events will 214 * @rx_ts_inline: Flag for whether RX timestamps are inline (else they are 216 * @rxq: Receive SKB queue (awaiting timestamps) 248 * timestamps 250 * timestamps 252 * @ts_corrections.pps_in: Required driver correction of PPS input timestamps 254 * transmit timestamps 256 * receive timestamps 364 * if PTP uses MAC TX timestamps, not if PTP uses the MC directly to transmit. 593 * we can deal with the (unlikely) case of sync timestamps in efx_ptp_mac_nic_to_ktime_correction() [all …]
|
/linux/tools/testing/selftests/bpf/progs/ |
H A D | test_time_tai.c | 14 /* Get TAI timestamps */ in time_tai() 18 /* Save TAI timestamps (Note: skb->hwtstamp is read-only) */ in time_tai()
|
/linux/Documentation/driver-api/hte/ |
H A D | hte.rst | 16 in obtaining timestamps than using software counterparts i.e. ktime and 49 - Converts timestamps in nanoseconds. 77 The dropped timestamps for a given line.
|
H A D | tegra-hte.rst | 17 This GTE instance timestamps GPIO in real time. For that to happen GPIO 37 This GTE instance timestamps LIC IRQ lines in real time. The hte devicetree
|
/linux/Documentation/driver-api/ |
H A D | ioctl.rst | 84 Timestamps chapter 87 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
|
/linux/drivers/net/ethernet/sfc/ |
H A D | ptp.c | 19 * Packets not matching are delivered without timestamps (MCDI events will 229 * @rxq: Receive SKB queue (awaiting timestamps) 257 * timestamps 259 * timestamps 261 * @ts_corrections.pps_in: Required driver correction of PPS input timestamps 263 * transmit timestamps 265 * receive timestamps 370 * if PTP uses MAC TX timestamps, not if PTP uses the MC directly to transmit. 586 * we can deal with the (unlikely) case of sync timestamps in efx_ptp_mac_nic_to_ktime_correction() 1126 struct skb_shared_hwtstamps timestamps; in efx_ptp_xmit_skb_mc() local [all …]
|
/linux/tools/perf/Documentation/ |
H A D | perf-inject.txt | 86 Some architectures may capture AUX area data which contains timestamps 87 affected by virtualization. This option will update those timestamps 88 in place, to correlate with host timestamps. The in-place update means
|
/linux/include/uapi/linux/ |
H A D | errqueue.h | 47 * struct scm_timestamping - timestamps exposed through cmsg 50 * communicate network timestamps by passing this struct in a cmsg with
|
/linux/fs/xfs/libxfs/ |
H A D | xfs_format.h | 392 #define XFS_SB_FEAT_INCOMPAT_BIGTIME (1 << 3) /* large timestamps */ 771 * XFS Timestamps 774 * Traditional ondisk inode timestamps consist of signed 32-bit counters for 778 * constrain the incore timestamps on a Unix system. Note that we actually 781 * When the bigtime feature is enabled, ondisk inode timestamps become an 786 * timestamps. 797 * Smallest possible ondisk seconds value with traditional timestamps. This 803 * Largest possible ondisk seconds value with traditional timestamps. This 809 * Smallest possible ondisk seconds value with bigtime timestamps. This 816 * Largest supported ondisk seconds value with bigtime timestamps. This [all …]
|
/linux/Documentation/core-api/ |
H A D | timekeeping.rst | 20 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.
|
/linux/drivers/gpu/drm/ |
H A D | drm_vblank.c | 167 MODULE_PARM_DESC(timestamp_precision_usec, "Max. error on timestamps [usecs]"); 322 * on the difference in the timestamps and the in drm_update_vblank_count() 344 * might reset at some point in that interval and vblank timestamps in drm_update_vblank_count() 420 "This function requires support for accurate vblank timestamps."); in drm_crtc_accurate_vblank_count() 460 * so no updates of timestamps or count can happen after we've in drm_vblank_disable_and_save() 665 * @max_error: Desired maximum allowable error in timestamps (nanosecs) 676 * Implements calculation of exact vblank timestamps from given drm_display_mode 744 * and bounding timestamps stime, etime, pre/post query. in drm_crtc_vblank_helper_get_vblank_timestamp_internal() 810 * @max_error: Desired maximum allowable error in timestamps (nanosecs) 818 * Implements calculation of exact vblank timestamps from given drm_display_mode [all …]
|