Lines Matching defs:vblank
542 * start of vblank:
545 * generate start of vblank interrupt (gen4+)
548 * | generate frame start interrupt (aka. vblank interrupt) (gmch)
577 * (depending on PIPECONF settings) after the start of vblank
588 struct drm_vblank_crtc *vblank = &dev_priv->drm.vblank[drm_crtc_index(crtc)];
589 const struct drm_display_mode *mode = &vblank->hwmode;
599 * vblank wait before enabling the TV encoder and so we
600 * have to enable vblank interrupts while the frame counter
601 * is still in a working state. However the core vblank code
606 if (!vblank->max_vblank_count)
618 /* Start of vblank event occurs at start of hsync */
645 * Cook up a vblank counter by also checking the pixel
646 * counter against vblank start.
670 struct drm_vblank_crtc *vblank =
671 &crtc->base.dev->vblank[drm_crtc_index(&crtc->base)];
672 const struct drm_display_mode *mode = &vblank->hwmode;
681 * next vblank just between the PIPE_FRMTMSTMP and TIMESTAMP_CTR
716 struct drm_vblank_crtc *vblank;
723 vblank = &crtc->base.dev->vblank[drm_crtc_index(&crtc->base)];
724 mode = &vblank->hwmode;
740 * read it just before the start of vblank. So try it again
741 * so we don't accidentally end up spanning a vblank frame
745 * bit and return the vblank start value; nor can we use the scanline
846 * Start of vblank interrupt is triggered at start of hsync,
847 * just prior to the first active line of vblank. However we
850 * the horizontal active of the first line in vblank, we would
866 * While in vblank, position will be negative
868 * vblank, position will be positive counting
1218 * bonkers. So let's just wait for the next vblank and read
2553 * Vblank interrupts fail to wake the device up from C2+.
2556 * only when vblank interrupts are actually enabled.
Indexes created Thu Oct 02 01:09:59 GMT 2025