diff options
| author | 2019-01-30 11:32:12 -0500 | |
|---|---|---|
| committer | 2019-04-18 10:04:10 -0700 | |
| commit | f98baa3109cea46083d2361ab14a0207d1b1bd16 (patch) | |
| tree | 220feba8068d6a5b03b0ebd5c4cd9d78bdf9ec6e /scripts/patch-kernel | |
| parent | drm/msm: dpu: Don't queue the frame_done watchdog for cursor (diff) | |
drm/msm: dpu: Don't set frame_busy_mask for async updates
The frame_busy mask is used in frame_done event handling, which is not
invoked for async commits. So an async commit will leave the
frame_busy mask populated after it completes and future commits will start
with the busy mask incorrect.
This showed up on disable after cursor move. I was hitting the "this should
not happen" comment in the frame event worker since frame_busy was set,
we queued the event, but there were no frames pending (since async
also doesn't set that).
Reviewed-by: Fritz Koenig <frkoenig@google.com>
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Link: https://patchwork.freedesktop.org/patch/msgid/20190130163220.138637-1-sean@poorly.run
Signed-off-by: Rob Clark <robdclark@chromium.org>
Diffstat (limited to 'scripts/patch-kernel')
0 files changed, 0 insertions, 0 deletions
