diff options
author | 2019-05-07 13:18:11 -0600 | |
---|---|---|
committer | 2019-06-18 13:52:49 -0700 | |
commit | 03b7af1ef4992bd0dc2b758e94698054fbbb19eb (patch) | |
tree | 29d90f70b25f4af408b422daa357f0981c4ba29f /tools/perf/scripts/python/export-to-postgresql.py | |
parent | drm/msm/dpu: Avoid a null de-ref while recovering from kms init fail (diff) | |
download | linux-rng-03b7af1ef4992bd0dc2b758e94698054fbbb19eb.tar.xz linux-rng-03b7af1ef4992bd0dc2b758e94698054fbbb19eb.zip |
drm/msm/adreno: Call pm_runtime_force_suspend() during unbind
The GPU specific pm_suspend code assumes that the hardware is active
when the function is called, which it usually is when called as part
of pm_runtime. But during unbind, the pm_suspend functions are called
blindly resulting in a bit of a when the hardware wasn't already
active (or booted, in the case of the GMU).
Instead of calling the pm_suspend function directly, use
pm_runtime_force_suspend() which should check the correct state of
runtime and call the functions on our behalf or skip them if they are
not needed.
Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
Signed-off-by: Rob Clark <robdclark@chromium.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions