Searched refs:drift (Results 1 – 14 of 14) sorted by relevance
549 int drift, ret = 0; in kvm_mips_restore_hrtimer() local562 drift = count - before_count; in kvm_mips_restore_hrtimer()563 if (drift < min_drift) { in kvm_mips_restore_hrtimer()565 vcpu->arch.count_bias += drift; in kvm_mips_restore_hrtimer()566 ret = drift; in kvm_mips_restore_hrtimer()578 drift = count - now_count; in kvm_mips_restore_hrtimer()579 if (drift > 0) { in kvm_mips_restore_hrtimer()581 vcpu->arch.count_bias += drift; in kvm_mips_restore_hrtimer()582 ret = drift; in kvm_mips_restore_hrtimer()
109 drift (noise) calibration occurs.111 IBM Trackpoints have a feature to compensate for drift by
34 so the residual offset error temperature drift is extremely low.
132 for long term drift. For more information see
82 Description: (RO) Contains the current drift value used by the firmware
7 signals - can compensate the drift between the two ws signal.
1390 u32 drift; in vc4_hdmi_recenter_fifo() local1399 drift = HDMI_READ(HDMI_FIFO_CTL); in vc4_hdmi_recenter_fifo()1400 drift &= VC4_HDMI_FIFO_VALID_WRITE_MASK; in vc4_hdmi_recenter_fifo()1403 drift & ~VC4_HDMI_FIFO_CTL_RECENTER); in vc4_hdmi_recenter_fifo()1405 drift | VC4_HDMI_FIFO_CTL_RECENTER); in vc4_hdmi_recenter_fifo()1414 drift & ~VC4_HDMI_FIFO_CTL_RECENTER); in vc4_hdmi_recenter_fifo()1416 drift | VC4_HDMI_FIFO_CTL_RECENTER); in vc4_hdmi_recenter_fifo()
119 The calibration of these devices does drift over time. If ghosts or contact
56 clocksource without (NTP) adjustments for clock drift. This is
166 allows the PID controller to compensate for long term drift and for
155 drift between the CPUs on the system. The kernel can work around this by
392 cause the CPU clocks, and thus the TSCs to drift over time. Depending on the393 exact clock and bus design, the drift may or may not be fixed in absolute
419 long-running conversations can drift away from the original subject
210 drift between the video and system clock. For output streams that