From: kalyan_t@codeaurora.org
To: Rob Clark <robdclark@gmail.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Krishna Manikandan <mkrishn@codeaurora.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Raviteja Tamatam <travitej@codeaurora.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Douglas Anderson <dianders@chromium.org>,
nganji@codeaurora.org, Sean Paul <seanpaul@chromium.org>,
Abhinav Kumar <abhinavk@codeaurora.org>,
Drew Davenport <ddavenport@chromium.org>,
"Kristian H. Kristensen" <hoegsberg@chromium.org>,
Stephen Boyd <swboyd@chromium.org>,
freedreno <freedreno@lists.freedesktop.org>
Subject: Re: [Freedreno] [v1] drm/msm/dpu: update reservations in commit path
Date: Wed, 05 Aug 2020 19:48:13 +0530 [thread overview]
Message-ID: <37bbf6e41a844f681e263bc13bd6e7ef@codeaurora.org> (raw)
In-Reply-To: <CAF6AEGtpPU+ALcpQMuy-MpLF_ZwjD+k=aN7gkoBFjJPq1++9qQ@mail.gmail.com>
On 2020-08-05 01:02, Rob Clark wrote:
> On Tue, Aug 4, 2020 at 4:32 AM Kalyan Thota <kalyan_t@codeaurora.org>
> wrote:
>>
>> DPU resources reserved in the atomic_check path gets unwinded
>> during modeset operation before commit happens in a non seamless
>> transition.
>>
>> Update the reservations in the commit path to avoid resource
>> failures. Secondly have dummy reservations in atomic_check path
>> so that we can gracefully fail the composition if resources are
>> not available.
>>
>> Signed-off-by: Kalyan Thota <kalyan_t@codeaurora.org>
>> ---
>> drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 15 +++++++++++----
>> 1 file changed, 11 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>> b/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>> index 63976dc..c6b8254 100644
>> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>> @@ -565,7 +565,7 @@ static int dpu_encoder_virt_atomic_check(
>> const struct drm_display_mode *mode;
>> struct drm_display_mode *adj_mode;
>> struct msm_display_topology topology;
>> - struct dpu_global_state *global_state;
>> + struct dpu_global_state tmp_resv_state;
>> int i = 0;
>> int ret = 0;
>>
>> @@ -582,7 +582,7 @@ static int dpu_encoder_virt_atomic_check(
>> dpu_kms = to_dpu_kms(priv->kms);
>> mode = &crtc_state->mode;
>> adj_mode = &crtc_state->adjusted_mode;
>> - global_state = dpu_kms_get_existing_global_state(dpu_kms);
>> + memset(&tmp_resv_state, 0, sizeof(tmp_resv_state));
>
> I think what you want to do is dpu_kms_get_global_state().. that will
> clone/duplicate the existing global state (or return the already
> duplicated global state if it is called multiple times).
>
Thanks Rob, realized the same after posting patch. Made changes in the
new patch
accordingly.
> It is safe to modify this global state in the atomic_check() path.. in
> fact that is the intention. For a TEST_ONLY atomic commit, or if any
> of the atomic_check()'s fail, this new duplicated global state is
> discarded. If all the checks succeed and the atomic update is
> committed to hw, this new global state replaces the existing global
> state.
>
Posted a new change kindly review.
> BR,
> -R
>
>> trace_dpu_enc_atomic_check(DRMID(drm_enc));
>>
>> /*
>> @@ -621,7 +621,7 @@ static int dpu_encoder_virt_atomic_check(
>> * info may not be available to complete reservation.
>> */
>> if (drm_atomic_crtc_needs_modeset(crtc_state)) {
>> - ret = dpu_rm_reserve(&dpu_kms->rm,
>> global_state,
>> + ret = dpu_rm_reserve(&dpu_kms->rm,
>> &tmp_resv_state,
>> drm_enc, crtc_state,
>> topology);
>> }
>> }
>> @@ -966,7 +966,7 @@ static void dpu_encoder_virt_mode_set(struct
>> drm_encoder *drm_enc,
>> struct dpu_hw_blk *hw_lm[MAX_CHANNELS_PER_ENC];
>> struct dpu_hw_blk *hw_dspp[MAX_CHANNELS_PER_ENC] = { NULL };
>> int num_lm, num_ctl, num_pp, num_dspp;
>> - int i, j;
>> + int i, j, rc;
>>
>> if (!drm_enc) {
>> DPU_ERROR("invalid encoder\n");
>> @@ -1006,6 +1006,13 @@ static void dpu_encoder_virt_mode_set(struct
>> drm_encoder *drm_enc,
>>
>> topology = dpu_encoder_get_topology(dpu_enc, dpu_kms,
>> adj_mode);
>>
>> + rc = dpu_rm_reserve(&dpu_kms->rm, global_state, drm_enc,
>> + drm_crtc->state, topology);
>> + if (rc) {
>> + DPU_ERROR_ENC(dpu_enc, "Failed to reserve
>> resources\n");
>> + return;
>> + }
>> +
>> /* Query resource that have been reserved in atomic check
>> step. */
>> num_pp = dpu_rm_get_assigned_resources(&dpu_kms->rm,
>> global_state,
>> drm_enc->base.id, DPU_HW_BLK_PINGPONG, hw_pp,
>> --
>> 1.9.1
>>
> _______________________________________________
> Freedreno mailing list
> Freedreno@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/freedreno
prev parent reply other threads:[~2020-08-05 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 11:32 [v1] drm/msm/dpu: update reservations in commit path Kalyan Thota
2020-08-04 19:32 ` Rob Clark
2020-08-05 14:18 ` kalyan_t [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=37bbf6e41a844f681e263bc13bd6e7ef@codeaurora.org \
--to=kalyan_t@codeaurora.org \
--cc=abhinavk@codeaurora.org \
--cc=ddavenport@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=hoegsberg@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkrishn@codeaurora.org \
--cc=nganji@codeaurora.org \
--cc=robdclark@gmail.com \
--cc=seanpaul@chromium.org \
--cc=swboyd@chromium.org \
--cc=travitej@codeaurora.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).