drm/msm/a6xx: No zap shader is not an error
authorRob Clark <robdclark@chromium.org>
Wed, 8 May 2019 13:06:52 +0000 (06:06 -0700)
committerSean Paul <seanpaul@chromium.org>
Wed, 8 May 2019 20:00:54 +0000 (16:00 -0400)
commit15273ffd7efdf6e9f21c4e4beef6539229167343
tree7804ecce403c084defa63849bc82add84a9b4ae8
parent23e35c0eb81a23d40c079a7eb187fc321fa1deb7
drm/msm/a6xx: No zap shader is not an error

Depending on platform firmware, a zap shader may not be required to take
the GPU out of secure mode on boot, in which case we can just write
RBBM_SECVID_TRUST_CNTL directly.  Which we *mostly* handled, but missed
clearing 'ret' resulting that hw_init() returned an error on these
devices.

Fixes: abccb9fe3267 ("drm/msm/a6xx: Add zap shader load")
Acked-by: Jordan Crouse <jcrouse@codeaurora.org>
Reviewed-by: Sean Paul <sean@poorly.run>
Signed-off-by: Rob Clark <robdclark@chromium.org>
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Link: https://patchwork.freedesktop.org/patch/msgid/20190508130726.27557-1-robdclark@gmail.com
drivers/gpu/drm/msm/adreno/a6xx_gpu.c