| /linux/drivers/iio/common/inv_sensors/ |
| H A D | inv_sensors_timestamp.c | 13 /* compute jitter, min and max following jitter in per mille */ 48 ts->min_period = INV_SENSORS_TIMESTAMP_MIN(chip->clock_period, chip->jitter); in inv_sensors_timestamp_init() 49 ts->max_period = INV_SENSORS_TIMESTAMP_MAX(chip->clock_period, chip->jitter); in inv_sensors_timestamp_init() 115 int64_t delta, jitter; in inv_align_timestamp_it() local 121 /* adjust timestamp while respecting jitter */ in inv_align_timestamp_it() 124 jitter = INV_SENSORS_TIMESTAMP_JITTER((int64_t)ts->period, ts->chip.jitter); in inv_align_timestamp_it() 125 if (delta > jitter) in inv_align_timestamp_it() 127 else if (delta < -jitter) in inv_align_timestamp_it()
|
| /linux/tools/testing/selftests/rcutorture/bin/ |
| H A D | jitterstart.sh | 4 # Start up the specified number of jitter.sh scripts in the background. 8 # n: Number of jitter.sh scripts to start up. 21 echo jitterstart.sh: Missing count of jitter.sh scripts to start. 36 jitter.sh $jitter_i "${jittering_dir}/jittering" "$@" &
|
| H A D | kvm.sh | 58 jitter="-1" 79 echo " --jitter N [ maxsleep (us) [ maxspin (us) ] ]" 189 --jitter) 190 …checkarg --jitter "(# threads [ sleep [ spin ] ])" $# "$2" '^-\{,1\}[0-9]\+\( \+[0-9]\+\)\{,2\} *$… 191 jitter="$2" 261 # If you really want jitter for refscale or 263 # or the refscale. (But why jitter in these cases?) 264 jitter=0 467 split(jitter, ja); 527 print "echo Build-only run, so suppressing jitter | tee -a " rd "log" [all …]
|
| H A D | jitter.sh | 5 # of this script is to inflict random OS jitter on a concurrently running 8 # Usage: jitter.sh me jittering-path duration [ sleepmax [ spinmax ] ]
|
| H A D | kvm-transform.sh | 10 # jitter_dir: Jitter directory for TORTURE_JITTER_START and 42 echo "Need valid jitter directory: '$jitter_dir'"
|
| H A D | jitterstop.sh | 4 # Remove the "jittering" file, signaling the jitter.sh scripts to stop,
|
| /linux/Documentation/timers/ |
| H A D | no_hz.rst | 8 efficiency and reducing OS jitter. Reducing OS jitter is important for 202 So you enable all the OS-jitter features described in this document, 204 your workload isn't affected that much by OS jitter, or is it because 206 by providing a simple OS-jitter test suite, which is available on branch 213 whether or not you have succeeded in removing OS jitter from your system. 214 If this trace shows that you have removed OS jitter as much as is 216 sensitive to OS jitter. 219 We do not currently have a good way to remove OS jitter from single-CPU 286 of OS jitter, including interrupts and system-utility tasks 290 * Some sources of OS jitter can currently be eliminated only by [all …]
|
| /linux/include/uapi/linux/ |
| H A D | timex.h | 81 __kernel_long_t jitter; /* pps jitter (us) (ro) */ member 84 __kernel_long_t jitcnt; /* jitter limit exceeded (ro) */ 120 long long jitter; /* pps jitter (us) (ro) */ member 124 long long jitcnt; /* jitter limit exceeded (ro) */ 182 #define STA_PPSJITTER 0x0200 /* PPS signal jitter exceeded (ro) */
|
| /linux/kernel/time/ |
| H A D | ntp.c | 46 * @pps_jitter: PPS current jitter in nanoseconds 53 * @pps_jitcnt: PPS monitor: jitter limit exceeded 187 * PPS jitter exceeded when PPS time synchronization in is_error_status() 204 txc->jitter = ntpdata->pps_jitter; in pps_fill_timex() 206 txc->jitter = ntpdata->pps_jitter / NSEC_PER_USEC; in pps_fill_timex() 236 txc->jitter = 0; in pps_fill_timex() 885 /* Get current phase correction and jitter */ 886 static inline long pps_phase_filter_get(struct ntp_data *ntpdata, long *jitter) in pps_phase_filter_get() argument 888 *jitter = ntpdata->pps_tf[0] - ntpdata->pps_tf[1]; in pps_phase_filter_get() 889 if (*jitter < 0) in pps_phase_filter_get() [all …]
|
| /linux/crypto/ |
| H A D | Kconfig | 1224 tristate "CPU Jitter Non-Deterministic RNG (Random Number Generator)" 1228 CPU Jitter RNG (Random Number Generator) from the Jitterentropy library 1242 prompt "CPU Jitter RNG Memory Size" 1245 The Jitter RNG measures the execution time of memory accesses. 1254 the entropy rate produced by the Jitter RNG can be modified. 1284 int "CPU Jitter RNG Oversampling Rate" 1288 The Jitter RNG allows the specification of an oversampling rate (OSR). 1289 The Jitter RNG operation requires a fixed amount of timing 1293 by the OSR factor. The oversampling allows the Jitter RNG to operate 1296 trade-off, however, is that the Jitter RNG now requires more time [all …]
|
| /linux/include/linux/usb/ |
| H A D | midi-v2.h | 41 #define USB_MS_MIDI_PROTO_1_0_64_JRTS 0x02 /* MIDI 1.0, UMP up to 64bits, Jitter Reduction Timestam… 43 #define USB_MS_MIDI_PROTO_1_0_128_JRTS 0x04 /* MIDI 1.0, UMP up to 128bits, Jitter Reduction Timest… 45 #define USB_MS_MIDI_PROTO_2_0_JRTS 0x12 /* MIDI 2.0, Jitter Reduction Timestamps */
|
| /linux/net/sched/ |
| H A D | sch_netem.c | 44 packets and add random jitter (and correlation). The random 78 /* a linear queue; reduces rbtree rebalancing when jitter is low */ 90 s64 jitter; member 482 if (q->latency || q->jitter || q->rate) in netem_enqueue() 558 delay = tabledist(q->latency, q->jitter, in netem_enqueue() 1064 q->jitter = PSCHED_TICKS2NS(qopt->jitter); in netem_change() 1102 q->jitter = nla_get_s64(tb[TCA_NETEM_JITTER64]); in netem_change() 1110 /* capping jitter to the range acceptable by tabledist() */ in netem_change() 1111 q->jitter = min_t(s64, abs(q->jitter), INT_MAX); in netem_change() 1220 qopt.jitter = min_t(psched_time_t, PSCHED_NS2TICKS(q->jitter), in netem_dump() [all …]
|
| /linux/include/net/ |
| H A D | ieee8021q.h | 17 * @IEEE8021Q_TT_VI: Video, < 100 ms latency and jitter 18 * @IEEE8021Q_TT_VO: Voice, < 10 ms latency and jitter
|
| /linux/Documentation/sound/cards/ |
| H A D | img-spdif-in.rst | 43 This control is used to modify the locking/jitter rejection characteristics 44 of the block. Larger values increase the locking range, but reduce jitter
|
| /linux/drivers/iio/frequency/ |
| H A D | Kconfig | 15 tristate "Analog Devices AD9523 Low Jitter Clock Generator" 18 Say yes here to build support for Analog Devices AD9523 Low Jitter
|
| /linux/drivers/media/pci/mantis/ |
| H A D | mantis_pcmcia.c | 28 * again, definitely it is jitter alone 52 * again, definitely it is jitter alone
|
| /linux/kernel/trace/ |
| H A D | trace_clock.c | 11 * - medium: scalable global clock with some jitter 54 * jitter between CPUs. So it's a pretty scalable clock, but there
|
| /linux/drivers/input/touchscreen/ |
| H A D | mk712.c | 21 * 1999-12-19: added anti-jitter code, report pen-up events, fixed mk712_poll 24 * 2000-01-05: checked in new anti-jitter code, changed mouse protocol, fixed
|
| /linux/include/linux/ |
| H A D | trace_clock.h | 10 * - medium: scalable global clock with some jitter
|
| H A D | mISDNdsp.h | 35 int unclocked; /* data is not clocked (has jitter/loss) */
|
| /linux/drivers/hte/ |
| H A D | Kconfig | 10 less jitter. This framework provides a generic interface to such HTE
|
| /linux/drivers/clk/ |
| H A D | clk-max77686.c | 258 /* MAX77802: Enable low-jitter mode on the 32khz clocks. */ in max77686_clk_probe() 264 dev_err(dev, "Failed to config low-jitter: %d\n", ret); in max77686_clk_probe()
|
| H A D | Kconfig | 54 tristate "Ti LMK04832 JESD204B Compliant Clock Jitter Cleaner" 59 Low-Noise JESD204B Compliant Clock Jitter Cleaner With Dual Loop PLLs 451 and jitter attenuator ICs with fractional and integer dividers.
|
| /linux/Documentation/devicetree/bindings/clock/ |
| H A D | starfive,jh7110-pll.yaml | 10 These PLLs are high speed, low jitter frequency synthesizers in the JH7110.
|
| /linux/drivers/net/wireguard/ |
| H A D | timers.c | 14 * `REKEY_TIMEOUT + jitter` ms. 21 * jitter` ms.
|