Files
linux/drivers
Jayant Shekhar d4e98855d1 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>
2018-12-11 13:07:08 -05:00
..
2018-12-03 17:40:18 +01:00
2018-10-16 11:13:50 +02:00
2018-10-11 12:12:55 +02:00
2018-11-09 17:56:44 +01:00
2018-11-29 10:34:03 +10:00
2018-11-23 22:35:38 -08:00
2018-10-31 08:54:16 -07:00
2018-11-29 10:34:03 +10:00
2018-10-11 09:16:44 -07:00
2018-11-11 09:21:46 -08:00