diff options
| author | Jayant Shekhar <jshekhar@codeaurora.org> | 2018-11-02 18:19:17 +0530 |
|---|---|---|
| committer | Rob Clark <robdclark@gmail.com> | 2018-12-11 13:07:08 -0500 |
| commit | d4e98855d170dc808e7f52c478f1beb18b700139 (patch) | |
| tree | e78f73afde1a5fa9003e14a01c1adaee23aade41 /tools/perf/scripts/python/exported-sql-viewer.py | |
| parent | c1866d44d149a1ea5c303632114fb6aa08cfd263 (diff) | |
drm/msm/dpu: Correct dpu destroy and disable order
In case of msm drm bind failure, dpu_mdss_destroy is triggered.
In this function, resources are freed and pm runtime disable is
called, which triggers dpu_mdss_disable. Now in dpu_mdss_disable,
driver tries to access a memory which is already freed. This
results in kernel panic. Fix this by ensuring proper sequence
of dpu destroy and disable calls.
Changes in v2:
- Removed double spacings [Jeykumar]
Tested-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: Jayant Shekhar <jshekhar@codeaurora.org>
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Signed-off-by: Rob Clark <robdclark@gmail.com>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions