Re: [Patch v3 ] drm/msm/dpu: Correct dpu destroy and disable order

2018-11-19 Thread Rajendra Nayak
On 11/19/2018 11:55 AM, Jayant Shekhar wrote: In case of msm drm bind failure, pm runtime put sync is called from dsi driver which issues an asynchronous put on mdss device. Subsequently when dpu_mdss_destroy is triggered the change will make sure to put the mdss device in suspend and clearing

Re: [Patch v3 ] drm/msm/dpu: Correct dpu destroy and disable order

2018-11-19 Thread Rajendra Nayak
On 11/19/2018 11:55 AM, Jayant Shekhar wrote: In case of msm drm bind failure, pm runtime put sync is called from dsi driver which issues an asynchronous put on mdss device. Subsequently when dpu_mdss_destroy is triggered the change will make sure to put the mdss device in suspend and clearing

[Patch v3 ] drm/msm/dpu: Correct dpu destroy and disable order

2018-11-18 Thread Jayant Shekhar
In case of msm drm bind failure, pm runtime put sync is called from dsi driver which issues an asynchronous put on mdss device. Subsequently when dpu_mdss_destroy is triggered the change will make sure to put the mdss device in suspend and clearing pending work if not scheduled. Changes in v2:

[Patch v3 ] drm/msm/dpu: Correct dpu destroy and disable order

2018-11-18 Thread Jayant Shekhar
In case of msm drm bind failure, pm runtime put sync is called from dsi driver which issues an asynchronous put on mdss device. Subsequently when dpu_mdss_destroy is triggered the change will make sure to put the mdss device in suspend and clearing pending work if not scheduled. Changes in v2: