Home
last modified time | relevance | path

Searched refs:vblanks (Results 1 – 11 of 11) sorted by relevance

/linux-5.19.10/drivers/gpu/drm/nouveau/nvkm/engine/disp/
Dhead.c58 args->v0.vblanks = head->arm.vblanks; in nvkm_head_mthd_scanoutpos()
Dheadnv04.c54 state->vblanks = nvkm_rd32(device, 0x680800 + hoff) & 0x0000ffff; in nv04_head_state()
Dhead.h21 u16 vblanks; member
Dheadnv50.c68 state->vblanks = (data & 0xffff0000) >> 16; in nv50_head_state()
Dheadgf119.c66 state->vblanks = (data & 0xffff0000) >> 16; in gf119_head_state()
Dheadgv100.c65 state->vblanks = (data & 0xffff0000) >> 16; in gv100_head_state()
Dnv50.c344 v = head->asy.vblanks - head->asy.vblanke - 25; in nv50_disp_super_2_2_dp()
/linux-5.19.10/drivers/gpu/drm/nouveau/include/nvif/
Dcl0046.h20 __u16 vblanks; member
Dcl5070.h19 __u16 vblanks; member
/linux-5.19.10/Documentation/gpu/
Dvkms.rst113 - VKMS already has support for vblanks simulated via hrtimers, which can be
174 boolean to ensure vblanks. Probably, when these operations work together,
/linux-5.19.10/drivers/gpu/drm/nouveau/
Dnouveau_display.c113 *vpos = calc(args.scan.vblanks, args.scan.vblanke, in nouveau_display_scanoutpos_head()