Lines Matching full:vsync
32 // DispSync maintains a model of the periodic hardware-based vsync events of a
34 // offsets from the hardware vsync events. The model is constructed by
40 // timestamps should correspond to a hardware vsync event, but they need not
41 // be consecutive hardware vsync times. If this method determines that the
60 // addPresentFence adds a fence for use in validating the current vsync
63 // should correspond to a hardware vsync event. Unlike the
65 // correspond to consecutive hardware vsync events.
72 // synchronize the DispSync's model to the hardware vsync events. The re-
74 // calling addResyncSample with a sequence of consecutive hardware vsync
81 // from the hardware vsync events.
86 // The setPreiod method sets the vsync event model's period to a specific
92 // given phase offset from the hardware vsync events. The callback is
113 // mPeriod is the computed period of the modeled vsync events in
117 // mPhase is the phase offset of the modeled vsync events. It is the
118 // number of nanoseconds from time 0 to the first vsync event.
122 // between the estimated vsync event times and those observed in the
127 // process to store information about the hardware vsync event times used
