aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/patch-kernel
diff options
context:
space:
mode:
authorSean Paul <seanpaul@chromium.org>2018-10-30 12:00:08 -0400
committerRob Clark <robdclark@gmail.com>2018-12-11 13:07:08 -0500
commit5f79e03b1f7c1b2cf0019ce6365fe5d52629813d (patch)
tree746f2635436d5ecd47176aedb6f9163f944081b8 /scripts/patch-kernel
parentdrm/msm/dpu: Correct dpu destroy and disable order (diff)
downloadlinux-5f79e03b1f7c1b2cf0019ce6365fe5d52629813d.tar.gz
linux-5f79e03b1f7c1b2cf0019ce6365fe5d52629813d.zip
drm/msm: dpu: Only check flush register against pending flushes
There exists a case where a flush of a plane/dma may have been triggered & started from an async commit. If that plane/dma is subsequently disabled by the next commit, the flush register will continue to hold the flush bit for the disabled plane. Since the bit remains active, pending_kickoff_cnt will never decrement and we'll miss frame_done events. This patch limits the check of flush_register to include only those bits which have been updated with the latest commit. Changes in v2: - None Reviewed-by: Jeykumar Sankaran <jsanka@codeaurora.org> Signed-off-by: Sean Paul <seanpaul@chromium.org> Signed-off-by: Rob Clark <robdclark@gmail.com>
Diffstat (limited to 'scripts/patch-kernel')
0 files changed, 0 insertions, 0 deletions