summaryrefslogtreecommitdiffstats
path: root/scripts/gdb/linux/utils.py
diff options
context:
space:
mode:
authorJordan Crouse <jcrouse@codeaurora.org>2019-04-19 13:46:15 -0600
committerRob Clark <robdclark@chromium.org>2019-04-21 07:37:17 -0700
commitabccb9fe326743b72c8099d5cc039e9038bc50da (patch)
tree8a02408b086360b867d8088eb2fc0239d3386b82 /scripts/gdb/linux/utils.py
parenta9e2559c931d7c44ae7d677b12093956ffa864b9 (diff)
downloadlinux-stable-abccb9fe326743b72c8099d5cc039e9038bc50da.tar.gz
linux-stable-abccb9fe326743b72c8099d5cc039e9038bc50da.tar.bz2
linux-stable-abccb9fe326743b72c8099d5cc039e9038bc50da.zip
drm/msm/a6xx: Add zap shader load
The a6xx GPU powers on in secure mode which restricts what memory it can write to. To get out of secure mode the GPU driver can write to REG_A6XX_RBBM_SECVID_TRUST_CNTL but on targets that are "secure" that register region is blocked and writes will cause the system to go down. For those targets we need to execute a special sequence that involves loadinga special shader that clears the GPU registers and use a PM4 sequence to pull the GPU out of secure. Add support for loading the zap shader and executing the secure sequence. For targets that do not support SCM or the specific SCM sequence this should fail and we would fall back to writing the register. Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org> Signed-off-by: Rob Clark <robdclark@chromium.org>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions