diff options
| author | Rob Clark <robdclark@chromium.org> | 2019-05-08 15:06:52 +0200 |
|---|---|---|
| committer | Sean Paul <seanpaul@chromium.org> | 2019-05-08 22:00:54 +0200 |
| commit | 15273ffd7efdf6e9f21c4e4beef6539229167343 (patch) | |
| tree | 7804ecce403c084defa63849bc82add84a9b4ae8 /drivers/gpu/drm/arm/display/komeda | |
| parent | drm/cma-helper: Fix drm_gem_cma_free_object() (diff) | |
| download | linux-15273ffd7efdf6e9f21c4e4beef6539229167343.tar.xz linux-15273ffd7efdf6e9f21c4e4beef6539229167343.zip | |
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
Diffstat (limited to 'drivers/gpu/drm/arm/display/komeda')
0 files changed, 0 insertions, 0 deletions