[PATCH v2 0/3] drm/msm/a6xx: Add support for zap shader
Jordan Crouse
jcrouse at codeaurora.org
Fri Apr 19 19:46:13 UTC 2019
This patch series adds support for loading the zap shader on a6xx and using it
to get the GPU out of secure mode.
The Adreno a5xx and a6xx GPUs boot in "secure" mode which restricts the memory
the GPU is allowed to use. To get the GPU out of secure mode we need to write
to a register. However some bootloaders block access to this register and
require that the GPU instead perform a sequence to pull the GPU out of secure
mode. This sequence requires a special "zap" shader that will execute in
secure mode, clear out all the internal GPU settings and then transition to
in-secure mode.
This series adds support for loading and using the zap shader on a6xx assuming
that the shader exists and that the bootloader supports the secure mode. If any
part of the sequence fails then fall back to writing the register. If we get it
wrong, then writing to the register will trigger a protection mode error and
the system will go down.
The actual zap shader works almost identically to the one on 5xx outside of
a minor workaround for system resume. The first patch moves the a5xx specific
support to the generic adreno driver. The second patch add support for the
zap shader and the final two patches add the DT bindings and DT settings for
setting up the reserved memory that the shader requires.
v2: Reduced the redundant log messages for targets that don't need the zap
shader
Jordan Crouse (3):
drm/msm/gpu: Move zap shader loading to adreno
drm/msm/a6xx: Add zap shader load
dt-bindings: drm/msm/gpu: Document a5xx / a6xx zap shader region
.../devicetree/bindings/display/msm/gpu.txt | 7 ++
drivers/gpu/drm/msm/adreno/a5xx_gpu.c | 111 +----------------
drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 38 +++++-
drivers/gpu/drm/msm/adreno/adreno_device.c | 1 +
drivers/gpu/drm/msm/adreno/adreno_gpu.c | 135 +++++++++++++++++++++
drivers/gpu/drm/msm/adreno/adreno_gpu.h | 6 +
6 files changed, 187 insertions(+), 111 deletions(-)
--
2.7.4
More information about the dri-devel
mailing list