All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Iskren Chernev <iskren.chernev@gmail.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] drm/msm/mdp5: Fix wait-for-commit for cmd panels
Date: Mon, 01 Mar 2021 19:59:43 +0000	[thread overview]
Message-ID: <161462878376.6187.17290908038432112193.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210127152442.533468-1-iskren.chernev@gmail.com>

Hello:

This patch was applied to qcom/linux.git (refs/heads/for-next):

On Wed, 27 Jan 2021 17:24:40 +0200 you wrote:
> Before the offending commit in msm_atomic_commit_tail wait_flush was
> called once per frame, after the commit was submitted. After it
> wait_flush is also called at the beginning to ensure previous
> potentially async commits are done.
> 
> For cmd panels the source of wait_flush is a ping-pong irq notifying
> a completion. The completion needs to be notified with complete_all so
> multiple waiting parties (new async committers) can proceed.
> 
> [...]

Here is the summary with links:
  - drm/msm/mdp5: Fix wait-for-commit for cmd panels
    https://git.kernel.org/qcom/c/68e4f01fddb4

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-03-01 20:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 15:24 [PATCH] drm/msm/mdp5: Fix wait-for-commit for cmd panels Iskren Chernev
2021-01-27 15:24 ` Iskren Chernev
2021-01-31 22:53 ` Brian Masney
2021-01-31 22:53   ` Brian Masney
2021-01-31 23:06 ` Luca Weiss
2021-01-31 23:06   ` Luca Weiss
2021-02-01  5:57 ` Alexey Minnekhanov
2021-02-01  5:57   ` Alexey Minnekhanov
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm [this message]

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=161462878376.6187.17290908038432112193.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=iskren.chernev@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.