drm: msm: sde: reorder call sequence in splash release thread

When splash releases resource, kernel blob property should
be updated at first, and then uevent sending follows.
This sequence can ensure user can always get the correct
information after kernel blob property is updated in
splash handoff thread.

Change-Id: I7b6493943c6eb1624da75dff5252dd3a71dea657
Signed-off-by: Guchun Chen <guchunc@codeaurora.org>
This commit is contained in:
Guchun Chen 2018-12-11 16:36:02 +08:00
parent bfe77429f9
commit d40b2726e8

View file

@ -857,12 +857,12 @@ int sde_splash_free_resource(struct msm_kms *kms,
sde_power_resource_enable(phandle, sde_power_resource_enable(phandle,
sde_kms->core_client, false); sde_kms->core_client, false);
/* send uevent to notify user to recycle resource */
_sde_splash_sent_pipe_update_uevent(sde_kms);
/* update impacted crtc and plane property by splash */ /* update impacted crtc and plane property by splash */
_sde_splash_update_property(sde_kms); _sde_splash_update_property(sde_kms);
/* send uevent to notify user to recycle resource */
_sde_splash_sent_pipe_update_uevent(sde_kms);
/* set display's splash status to false after handoff is done */ /* set display's splash status to false after handoff is done */
_sde_splash_update_display_splash_status(sde_kms); _sde_splash_update_display_splash_status(sde_kms);