Lines Matching defs:vblank
573 * start of vblank:
576 * generate start of vblank interrupt (gen4+)
579 * | generate frame start interrupt (aka. vblank interrupt) (gmch)
608 * (depending on PIPECONF settings) after the start of vblank
619 struct drm_vblank_crtc *vblank = &dev_priv->drm.vblank[drm_crtc_index(crtc)];
620 const struct drm_display_mode *mode = &vblank->hwmode;
630 * vblank wait before enabling the TV encoder and so we
631 * have to enable vblank interrupts while the frame counter
632 * is still in a working state. However the core vblank code
637 if (!vblank->max_vblank_count)
649 /* Start of vblank event occurs at start of hsync */
676 * Cook up a vblank counter by also checking the pixel
677 * counter against vblank start.
701 struct drm_vblank_crtc *vblank =
702 &crtc->base.dev->vblank[drm_crtc_index(&crtc->base)];
703 const struct drm_display_mode *mode = &vblank->hwmode;
712 * next vblank just between the PIPE_FRMTMSTMP and TIMESTAMP_CTR
752 struct drm_vblank_crtc *vblank;
759 vblank = &crtc->base.dev->vblank[drm_crtc_index(&crtc->base)];
760 mode = &vblank->hwmode;
776 * read it just before the start of vblank. So try it again
777 * so we don't accidentally end up spanning a vblank frame
781 * bit and return the vblank start value; nor can we use the scanline
885 * Start of vblank interrupt is triggered at start of hsync,
886 * just prior to the first active line of vblank. However we
889 * the horizontal active of the first line in vblank, we would
905 * While in vblank, position will be negative
907 * vblank, position will be positive counting
1221 * bonkers. So let's just wait for the next vblank and read
2591 * only when vblank interrupts are actually enabled.