From: patchwork-bot+linux-arm-msm@kernel.org
To: Rob Clark <robdclark@gmail.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/msm/a6xx: Clear shadow on suspend
Date: Tue, 29 Dec 2020 20:15:33 +0000 [thread overview]
Message-ID: <160927293366.13751.177629542188411248.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201110184401.282982-1-robdclark@gmail.com>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Tue, 10 Nov 2020 10:43:59 -0800 you wrote:
> From: Rob Clark <robdclark@chromium.org>
>
> Clear the shadow rptr on suspend. Otherwise, when we resume, we can
> have a stale value until CP_WHERE_AM_I executes. If we suspend near
> the ringbuffer wraparound point, this can lead to a chicken/egg
> situation where we are waiting for ringbuffer space to write the
> CP_WHERE_AM_I (or CP_INIT) packet, because we mistakenly believe that
> the ringbuffer is full (due to stale rptr value in the shadow).
>
> [...]
Here is the summary with links:
- [1/2] drm/msm/a6xx: Clear shadow on suspend
https://git.kernel.org/qcom/c/e8b0b994c3a5
- [2/2] drm/msm/a5xx: Clear shadow on suspend
https://git.kernel.org/qcom/c/5771de5d5b3b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-12-29 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 18:43 [PATCH 1/2] drm/msm/a6xx: Clear shadow on suspend Rob Clark
2020-11-10 18:43 ` Rob Clark
2020-11-10 18:44 ` [PATCH 2/2] drm/msm/a5xx: " Rob Clark
2020-11-10 18:44 ` Rob Clark
2020-11-10 18:46 ` Jordan Crouse
2020-11-10 18:46 ` Jordan Crouse
2020-11-10 18:46 ` [PATCH 1/2] drm/msm/a6xx: " Jordan Crouse
2020-11-10 18:46 ` Jordan Crouse
2020-12-29 20:15 ` 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=160927293366.13751.177629542188411248.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@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 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.