-
- Downloads
drm/panfrost: add initial MMU implementation
This is a rather simple implementation currently. There's only one
address space (48-bit though) and we don't support page faults. That
appears to be good enough for other GPU drivers. Currently the MMU
mapping is done when GEM object is created. This could be done when
BOs are submitted, but going with a simple implementation for now.
Mappings are also all inner and outer non-cacheable. The vendor driver
is inner cacheable. We'll need to revisit that.
Signed-off-by:
Rob Herring <robh@kernel.org>
Showing
- drivers/gpu/drm/panfrost/Kconfig 3 additions, 0 deletionsdrivers/gpu/drm/panfrost/Kconfig
- drivers/gpu/drm/panfrost/panfrost_device.h 13 additions, 0 deletionsdrivers/gpu/drm/panfrost/panfrost_device.h
- drivers/gpu/drm/panfrost/panfrost_drv.c 4 additions, 0 deletionsdrivers/gpu/drm/panfrost/panfrost_drv.c
- drivers/gpu/drm/panfrost/panfrost_gem.c 5 additions, 0 deletionsdrivers/gpu/drm/panfrost/panfrost_gem.c
- drivers/gpu/drm/panfrost/panfrost_mmu.c 262 additions, 1 deletiondrivers/gpu/drm/panfrost/panfrost_mmu.c
- drivers/gpu/drm/panfrost/panfrost_mmu.h 4 additions, 0 deletionsdrivers/gpu/drm/panfrost/panfrost_mmu.h
Loading
Please register or sign in to comment