diff options
| author |   Rob Clark <robdclark@chromium.org> | 2022-06-18 09:11:19 -0700 |
|---|---|---|
| committer | Rob Clark <robdclark@chromium.org> | 2022-06-18 09:13:33 -0700 |
| commit | c8af219d18502c52319df8d4e3dcfe29a3ca31ab (patch) | |
| tree | e52b401b786a0aa0595f978be77603a5d9cf6723 /scripts/generate_rust_analyzer.py | |
| parent | drm/msm: Drop update_fences() (diff) | |
| download | linux-dev-c8af219d18502c52319df8d4e3dcfe29a3ca31ab.tar.xz linux-dev-c8af219d18502c52319df8d4e3dcfe29a3ca31ab.zip | |
drm/msm: Don't overwrite hw fence in hw_init
Prior to the last commit, this could result in setting the GPU
written fence value back to an older value, if we had missed
updating completed_fence prior to suspend. This was mostly
harmless as the GPU would eventually overwrite it again with
the correct value. But we should just not do this. Instead
just leave a sanity check that the fence looks plausible (in
case the GPU scribbled on memory).
Reported-by: Steev Klimaszewski <steev@kali.org>
Fixes: 95d1deb02a9c ("drm/msm/gem: Add fenced vma unpin")
Signed-off-by: Rob Clark <robdclark@chromium.org>
Tested-by: Steev Klimaszewski <steev@kali.org>
Patchwork: https://patchwork.freedesktop.org/patch/490138/
Link: https://lore.kernel.org/r/20220618161120.3451993-2-robdclark@gmail.com
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions