From: Hai Li <hali@codeaurora.org>
To: dri-devel@lists.freedesktop.org
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
robdclark@gmail.com, Hai Li <hali@codeaurora.org>
Subject: [PATCH v2 0/2] drm/msm: Customize wait for atomic commit done function
Date: Tue, 28 Apr 2015 19:35:36 -0400 [thread overview]
Message-ID: <1430264138-31349-1-git-send-email-hali@codeaurora.org> (raw)
The current way to wait for atomic commit done may cause unnecessary wait for
another vsync for video mode path. Also, for command mode path, we need to wait
for PP_DONE event other than vsync before finish. This patch series is to fix
these issues.
v2: Replace function pointer with a cmd mode flag to differentiate cmd mode wait
function from video mode. (From Rob Clark)
Hai Li (2):
drm/msm: Use customized function to wait for atomic commit done
drm/msm/mdp5: Wait for PP_DONE irq for command mode CRTC atomic commit
drivers/gpu/drm/msm/mdp/mdp4/mdp4_crtc.c | 39 ++++++++
drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.c | 7 ++
drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.h | 1 +
drivers/gpu/drm/msm/mdp/mdp5/mdp5_cmd_encoder.c | 4 -
drivers/gpu/drm/msm/mdp/mdp5/mdp5_crtc.c | 125 +++++++++++++++++++++---
drivers/gpu/drm/msm/mdp/mdp5/mdp5_ctl.c | 11 ++-
drivers/gpu/drm/msm/mdp/mdp5/mdp5_ctl.h | 3 +-
drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c | 7 ++
drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.h | 1 +
drivers/gpu/drm/msm/msm_atomic.c | 30 +++++-
drivers/gpu/drm/msm/msm_kms.h | 3 +
11 files changed, 206 insertions(+), 25 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2015-04-28 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 23:35 Hai Li [this message]
2015-04-28 23:35 ` [PATCH v2 1/2] drm/msm: Use customized function to wait for atomic commit done Hai Li
2015-04-28 23:35 ` [PATCH v2 2/2] drm/msm/mdp5: Wait for PP_DONE irq for command mode CRTC atomic commit Hai Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1430264138-31349-1-git-send-email-hali@codeaurora.org \
--to=hali@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox