Lines Matching full:vsync
36 // DispSync maintains a model of the periodic hardware-based vsync events of a
38 // offsets from the hardware vsync events. The model is constructed by
44 // timestamps should correspond to a hardware vsync event, but they need not
45 // be consecutive hardware vsync times. If this method determines that the
67 // addPresentFence adds a fence for use in validating the current vsync
70 // should correspond to a hardware vsync event. Unlike the
72 // correspond to consecutive hardware vsync events.
79 // synchronize the DispSync's model to the hardware vsync events. The re-
81 // calling addResyncSample with a sequence of consecutive hardware vsync
88 // from the hardware vsync events.
93 // The setPeriod method sets the vsync event model's period to a specific
98 // The getPeriod method returns the current vsync period.
108 // given phase offset from the hardware vsync events. The callback is
142 // mPeriod is the computed period of the modeled vsync events in
146 // mPhase is the phase offset of the modeled vsync events. It is the
147 // number of nanoseconds from time 0 to the first vsync event.
150 // mReferenceTime is the reference time of the modeled vsync events.
151 // It is the nanosecond timestamp of the first vsync event after a resync.
155 // between the estimated vsync event times and those observed in the
164 // Whether we have updated the vsync event model since the last resync.
168 // process to store information about the hardware vsync event times used
190 // vsync event.
