drm/nouveau: kick vram functions out into an "engine"
NVC0 will be able to share some of nv50's paths this way. This also makes
it the card-specific vram code responsible for deciding if a given set
of tile_flags is valid, rather than duplicating the allowed types in
nv50_vram.c and nouveau_gem.c
Signed-off-by:
Ben Skeggs <bskeggs@redhat.com>
Showing
- drivers/gpu/drm/nouveau/nouveau_drv.h 12 additions, 0 deletionsdrivers/gpu/drm/nouveau/nouveau_drv.h
- drivers/gpu/drm/nouveau/nouveau_gem.c 3 additions, 27 deletionsdrivers/gpu/drm/nouveau/nouveau_gem.c
- drivers/gpu/drm/nouveau/nouveau_mem.c 26 additions, 21 deletionsdrivers/gpu/drm/nouveau/nouveau_mem.c
- drivers/gpu/drm/nouveau/nouveau_mm.h 1 addition, 0 deletionsdrivers/gpu/drm/nouveau/nouveau_mm.h
- drivers/gpu/drm/nouveau/nouveau_state.c 16 additions, 0 deletionsdrivers/gpu/drm/nouveau/nouveau_state.c
- drivers/gpu/drm/nouveau/nv50_instmem.c 6 additions, 3 deletionsdrivers/gpu/drm/nouveau/nv50_instmem.c
- drivers/gpu/drm/nouveau/nv50_vram.c 10 additions, 0 deletionsdrivers/gpu/drm/nouveau/nv50_vram.c
Loading
Please register or sign in to comment