Home
last modified time | relevance | path

Searched full:timestamps (Results 1 – 25 of 473) sorted by relevance

12345678910>>...19

/openbmc/phosphor-fan-presence/sensor-monitor/
H A Dalarm_timestamps.hpp41 * This class keeps track of the timestamps at which the shutdown
59 * Loads any saved timestamps
67 * @brief Adds an entry to the timestamps map and persists it.
77 auto result = timestamps.emplace(key, timestamp); in add()
91 size_t removed = timestamps.erase(key); in erase()
103 timestamps.erase(entry); in erase()
112 if (!timestamps.empty()) in clear()
114 timestamps.clear(); in clear()
130 auto size = timestamps.size(); in prune()
145 auto it = timestamps.begin(); in prune()
[all …]
H A Dshutdown_alarm_monitor.cpp116 // Get rid of any previous saved timestamps that don't in ShutdownAlarmMonitor()
118 timestamps.prune(alarms); in ShutdownAlarmMonitor()
122 timestamps.clear(); in ShutdownAlarmMonitor()
279 auto previousStartTime = timestamps.get().find(alarmKey); in startTimer()
280 if (previousStartTime != timestamps.get().end()) in startTimer()
327 // Note that if this key is already in the timestamps map because in startTimer()
329 timestamps.add(alarmKey, now); in startTimer()
357 timestamps.erase(alarmKey); in stopTimer()
401 timestamps.erase(alarmKey); in timerExpired()
413 timestamps.clear(); in powerStateChanged()
/openbmc/linux/Documentation/networking/
H A 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
62 Its struct timespec allows for higher resolution (ns) timestamps than the
68 SO_TIMESTAMPNS_OLD returns incorrect timestamps after the year 2038
91 Some bits are requests to the stack to try to generate timestamps. Any
94 is possible to selectively request timestamps for a subset of packets
97 Timestamps may also be generated for reasons other than being
102 Request rx timestamps generated by the network adapter.
[all …]
/openbmc/linux/drivers/gpu/drm/amd/display/dc/link/accessories/
H A Dlink_dp_trace.c111 link->dp_trace.detect_lt_trace.timestamps.start = dm_get_timestamp(link->dc->ctx); in dp_trace_set_lt_start_timestamp()
113 link->dp_trace.commit_lt_trace.timestamps.start = dm_get_timestamp(link->dc->ctx); in dp_trace_set_lt_start_timestamp()
120 link->dp_trace.detect_lt_trace.timestamps.end = dm_get_timestamp(link->dc->ctx); in dp_trace_set_lt_end_timestamp()
122 link->dp_trace.commit_lt_trace.timestamps.end = dm_get_timestamp(link->dc->ctx); in dp_trace_set_lt_end_timestamp()
129 return link->dp_trace.detect_lt_trace.timestamps.end; in dp_trace_get_lt_end_timestamp()
131 return link->dp_trace.commit_lt_trace.timestamps.end; in dp_trace_get_lt_end_timestamp()
/openbmc/openbmc-tools/dbus-vis/
H A Ddbus_pcap_loader.js14 // 2. Launch "dbus-pcap" to get the timestamps of each DBus message
30 ShowBlocker('Running dbus-pcap (Pass 1/2, packet timestamps) ...');
35 let timestamps = [];
59 …ShowBlocker('Running dbus-pcap (Pass 1/2, packet timestamps): ' + count1 + '/' + num_packets + ' (…
105 // Parse timestamps
114 timestamps.push(ts_usec);
148 Timestamps_DBus = timestamps;
157 let preproc = Preprocess_DBusPcap(packets, timestamps);
181 // Input: data and timestamps obtained from
188 function Preprocess_DBusPcap(data, timestamps) { argument
[all …]
/openbmc/linux/Documentation/sound/designs/
H A 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
/openbmc/linux/Documentation/devicetree/bindings/timestamp/
H A Dhte-consumer.yaml15 timestamps:
30 timestamp-names: [ timestamps ]
37 timestamps = <&tegra_hte_aon 0x9>, <&tegra_hte_lic 0x19>;
/openbmc/linux/drivers/net/ethernet/intel/ice/
H A Dice_ptp.c261 * @on: bool value for whether timestamps are enabled or disabled
294 * @on: bool value for whether timestamps are enabled or disabled
458 * @sts: Optional parameter for holding a pair of system timestamps from
482 * system timestamps in ice_ptp_read_src_clk_reg()
498 * Hardware captures timestamps which contain only 32 bits of nominal
499 * nanoseconds, as opposed to the 64bit timestamps that the stack expects.
565 * The Tx and Rx timestamps are 40 bits wide, including 32 bits of nominal
603 * ice_ptp_is_tx_tracker_up - Check if Tx tracker is ready for new timestamps
620 * ice_ptp_process_tx_tstamp - Process Tx timestamps for a port
623 * Process timestamps captured by the PHY associated with this port. To do
[all …]
H A Dice_ptp.h36 /* The ice hardware captures Tx hardware timestamps in the PHY. The timestamp
54 * devices. In E810 devices, each port has its own block of timestamps, while in
102 * been captured. This avoids reporting stale timestamps to the stack. This is
114 * @ICE_TX_TSTAMP_WORK_PENDING: More Tx timestamps are pending
126 * @stale: bitmap of len to indicate slots which have stale timestamps
127 * @block: which memory block (quad or port) the timestamps are captured in
132 * window, timestamps are temporarily disabled.
/openbmc/linux/tools/testing/selftests/tty/
H A Dtty_tstamp_update.c78 /* We wrote to the terminal so timestamps should have been updated */ in main()
81 ksft_test_result_fail("tty timestamps not updated\n"); in main()
86 "timestamps of terminal '%s' updated after write to /dev/tty\n", tty); in main()
/openbmc/linux/include/linux/platform_data/
H A Dcros_ec_sensorhub.h134 * 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
/openbmc/linux/drivers/net/dsa/sja1105/
H A Dsja1105_ptp.h11 /* 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
/openbmc/linux/Documentation/kbuild/
H A Dreproducible-builds.rst16 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
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-ptp111 timestamps. To enable external timestamps, write the
113 To disable external timestamps, write the channel
120 This file provides timestamps on external events, in
/openbmc/linux/block/
H A Dbfq-wf2q.c12 * 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 …]
/openbmc/linux/tools/testing/selftests/bpf/progs/
H A Dtest_time_tai.c14 /* Get TAI timestamps */ in time_tai()
18 /* Save TAI timestamps (Note: skb->hwtstamp is read-only) */ in time_tai()
/openbmc/linux/include/linux/usb/
H A Dmidi-v2.h41 …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 */
/openbmc/linux/drivers/staging/media/meson/vdec/
H A 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()
/openbmc/u-boot/arch/x86/include/asm/arch-coreboot/
H A Dtimestamp.h41 * timestamp_add_to_bootstage - Add important coreboot timestamps to bootstage
43 * @return 0 if ok, -1 if no timestamps were found
/openbmc/linux/Documentation/driver-api/hte/
H A Dhte.rst16 in obtaining timestamps than using software counterparts i.e. ktime and
49 - Converts timestamps in nanoseconds.
77 The dropped timestamps for a given line.
/openbmc/linux/Documentation/driver-api/
H A Dioctl.rst84 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
/openbmc/linux/tools/perf/Documentation/
H A Dperf-inject.txt86 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
/openbmc/linux/drivers/net/ethernet/sfc/siena/
H A Dptp.c19 * 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 …]
/openbmc/linux/include/uapi/linux/
H A Derrqueue.h47 * struct scm_timestamping - timestamps exposed through cmsg
50 * communicate network timestamps by passing this struct in a cmsg with
/openbmc/linux/tools/testing/selftests/net/
H A Dtxtimestamp.sh4 # Send packets with transmit timestamps over loopback with netem
5 # Verify that timestamps correspond to netem delay

12345678910>>...19