Home
last modified time | relevance | path

Searched refs:ctxprog (Results 1 – 3 of 3) sorted by relevance

/linux/drivers/gpu/drm/nouveau/nvkm/engine/gr/
H A Dctxnv40.h27 u32 *ctxprog = ctx->ucode; in cp_out() local
33 ctxprog[ctx->ctxprog_len++] = inst; in cp_out()
61 u32 *ctxprog = ctx->ucode; in cp_name() local
69 if ((ctxprog[i] & 0xfff00000) != 0xff400000) in cp_name()
71 if ((ctxprog[i] & CP_BRA_IP) != ((name) << CP_BRA_IP_SHIFT)) in cp_name()
73 ctxprog[i] = (ctxprog[i] & 0x00ff00ff) | in cp_name()
H A Dctxnv40.c41 * and then the ctxprog is aborted. It looks like a complicated NOP,
673 u32 *ctxprog = kmalloc(256 * 4, GFP_KERNEL), i; in nv40_grctx_init() local
677 .ucode = ctxprog, in nv40_grctx_init()
681 if (!ctxprog) in nv40_grctx_init()
688 nvkm_wr32(device, 0x400328, ctxprog[i]); in nv40_grctx_init()
691 kfree(ctxprog); in nv40_grctx_init()
H A Dctxnv50.c120 * further known as ctxprog, as well as the initial context values, known
123 * Without ctxprog, you cannot switch contexts. Not even in software, since
132 * Nouveau will just disable acceleration if not given ctxprog + ctxvals, since
133 * it's too much hassle to handle no-ctxprog as a special case.
139 * The ctxprog is written in its own kind of microcode, with very small and
143 * to ctxprog consists of: PGRAPH MMIO registers, PGRAPH context strands,
148 * When ctxprog runs, it's supposed to check what operations are asked of it,
174 /* Main function: construct the ctxprog skeleton, call the other functions. */
268 u32 *ctxprog = kmalloc(512 * 4, GFP_KERNEL), i; in nv50_grctx_init() local
272 .ucode = ctxprog, in nv50_grctx_init()
[all...]