Lines Matching full:vblank

779  *              USE_REAL_VBLANKSTART to use the real start of vblank instead
780  *              of a fudged earlier start of vblank.
783  *              fudged earlier start of vblank in *vpos and the distance
784  *              to true start of vblank in *hpos.
794  * Returns vpos as a negative number inside vblank, counting the number
795  * of scanlines to go until end of vblank, e.g., -1 means "one scanline
796  * until start of active scanout / end of vblank."
801  * DRM_SCANOUTPOS_INVBL = Inside vblank.
837 	/* Valid vblank area boundaries from gpu retrieved? */  in amdgpu_display_get_crtc_scanoutpos()
850 	/* Called from driver internal vblank counter query code? */  in amdgpu_display_get_crtc_scanoutpos()
856 	/* Fudge vblank to start a few scanlines earlier to handle the  in amdgpu_display_get_crtc_scanoutpos()
857 	 * problem that vblank irqs fire a few scanlines before start  in amdgpu_display_get_crtc_scanoutpos()
858 	 * of vblank. Some driver internal callers need the true vblank  in amdgpu_display_get_crtc_scanoutpos()
861 	 * The cause of the "early" vblank irq is that the irq is triggered  in amdgpu_display_get_crtc_scanoutpos()
863 	 * the vblank, whereas our crtc scanout position naturally lags the  in amdgpu_display_get_crtc_scanoutpos()
869 	/* Test scanout position against vblank region. */  in amdgpu_display_get_crtc_scanoutpos()
873 	/* In vblank? */  in amdgpu_display_get_crtc_scanoutpos()
877 	/* Called from driver internal vblank counter query code? */  in amdgpu_display_get_crtc_scanoutpos()
884 	/* Check if inside vblank area and apply corrective offsets:  in amdgpu_display_get_crtc_scanoutpos()
886 	 * within vblank area, counting down the number of lines until  in amdgpu_display_get_crtc_scanoutpos()
890 	/* Inside "upper part" of vblank area? Apply corrective offset if so: */  in amdgpu_display_get_crtc_scanoutpos()