Lines Matching full:vblank

158 	 * Reflects the ability of a CRTC to send VBLANK events. This state
160 	 * atomic helpers will send out a fake VBLANK event during display
164 	 * One usage is for drivers and/or hardware without support for VBLANK
168 	 * drm_atomic_helper_check_modeset(), and a fake VBLANK event will be
173 	 * oneshot mode. In this case the fake VBLANK event is only generated
175 	 * core to fake VBLANK events when this part of the pipeline hasn't
186 	 * this case the driver will send the VBLANK event on its own when the
331 	 *    last vblank before the display pipeline was shut off. The simplest
336 	 *    undergoes an full modeset) the vblank timestamp and counter must
337 	 *    be for the vblank right before the first frame that scans out the
344 	 * For very simple hardware without VBLANK interrupt, enabling
346 	 * send a fake VBLANK event at the end of the display update after all
353 	 * the atomic commit. Note that if the driver supports vblank signalling
354 	 * and timestamping the vblank counters and timestamps must agree with
355 	 * the ones returned from page flip events. With the current vblank
356 	 * helper infrastructure this can be achieved by holding a vblank
359 	 * Drivers are free to implement their own vblank counter and timestamp
363 	 * For hardware which supports some means to synchronize vblank
547 	 * the driver supports vblank signalling and timestamping the vblank
549 	 * flip events. With the current vblank helper infrastructure this can
550 	 * be achieved by holding a vblank reference while the page flip is
552 	 * drm_crtc_vblank_put(). Drivers are free to implement their own vblank
840 	 * Driver callback for fetching a raw hardware vblank counter for the
846 	 * will account for missed vblank events while interrupts where disabled
859 	 * Raw vblank counter value.
866 	 * Enable vblank interrupts for the CRTC. It's meant to be used by
871 	 * Zero on success, appropriate errno if the vblank interrupt cannot
879 	 * Disable vblank interrupts for the CRTC. It's meant to be used by
888 	 * timestamp when the most recent vblank interval ended or will end.
892 	 * the video frame after the end of vblank will start scanning out,
893 	 * the time immediately after end of the vblank interval. If the
894 	 * @crtc is currently inside vblank, this will be a time in the future.
909 	 *     Target location for returned vblank timestamp.
912 	 *     need to apply some workarounds for gpu-specific vblank irq quirks
1030 	 * precision vblank timestamps in