From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Vinod Polimera <quic_vpolimer@quicinc.com>,
dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, robdclark@gmail.com,
dianders@chromium.org, swboyd@chromium.org,
quic_kalyant@quicinc.com, quic_khsieh@quicinc.com,
quic_vproddut@quicinc.com, quic_bjorande@quicinc.com,
quic_abhinavk@quicinc.com, quic_sbillaka@quicinc.com
Subject: Re: [PATCH v1 3/3] msm: skip the atomic commit of self refresh while PSR running
Date: Mon, 3 Apr 2023 18:28:53 +0300 [thread overview]
Message-ID: <0e75e04d-fc07-2f60-bfb9-ee092075fae6@linaro.org> (raw)
In-Reply-To: <1680271114-1534-4-git-send-email-quic_vpolimer@quicinc.com>
On 31/03/2023 16:58, Vinod Polimera wrote:
> In certain CPU stress conditions, there can be a delay in scheduling commit
> work and it was observed that PSR commit from a different work queue was
> scheduled. Avoid these commits as display is already in PSR mode.
>
> Signed-off-by: Vinod Polimera <quic_vpolimer@quicinc.com>
> ---
> drivers/gpu/drm/msm/msm_atomic.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/msm/msm_atomic.c b/drivers/gpu/drm/msm/msm_atomic.c
> index 645fe53..f8141bb 100644
> --- a/drivers/gpu/drm/msm/msm_atomic.c
> +++ b/drivers/gpu/drm/msm/msm_atomic.c
> @@ -192,6 +192,9 @@ int msm_atomic_check(struct drm_device *dev, struct drm_atomic_state *state)
The corresponding patch is not yet applied. I wonder how this was tested.
> new_crtc_state->mode_changed = true;
> state->allow_modeset = true;
> }
> +
> + if (old_crtc_state->self_refresh_active && new_crtc_state->self_refresh_active)
> + return -EINVAL;
> }
>
> return drm_atomic_helper_check(dev, state);
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-04-03 15:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 13:58 [PATCH v1 0/3] Fixes for PSR Vinod Polimera
2023-03-31 13:58 ` [PATCH v1 1/3] drm/msm/dpu: set dirty_fb flag while in self refresh mode Vinod Polimera
2023-03-31 14:45 ` Dmitry Baryshkov
2023-04-03 14:53 ` Vinod Polimera
2023-04-03 16:18 ` Dmitry Baryshkov
2023-04-05 1:43 ` Doug Anderson
2023-03-31 13:58 ` [PATCH v1 2/3] msm/disp/dpu: allow atomic_check in PSR usecase Vinod Polimera
2023-03-31 14:46 ` Dmitry Baryshkov
2023-04-05 1:43 ` Doug Anderson
2023-03-31 13:58 ` [PATCH v1 3/3] msm: skip the atomic commit of self refresh while PSR running Vinod Polimera
2023-03-31 14:58 ` Dmitry Baryshkov
2023-04-03 12:01 ` Vinod Polimera
2023-04-03 16:11 ` Dmitry Baryshkov
2023-05-19 16:42 ` Dmitry Baryshkov
2023-04-03 15:28 ` Dmitry Baryshkov [this message]
2023-04-05 11:38 ` [PATCH v1 0/3] Fixes for PSR Dmitry Baryshkov
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=0e75e04d-fc07-2f60-bfb9-ee092075fae6@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_bjorande@quicinc.com \
--cc=quic_kalyant@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=quic_sbillaka@quicinc.com \
--cc=quic_vpolimer@quicinc.com \
--cc=quic_vproddut@quicinc.com \
--cc=robdclark@gmail.com \
--cc=swboyd@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).