From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Marijn Suijten <marijn.suijten@somainline.org>
Cc: Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Stephen Boyd <swboyd@chromium.org>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Bjorn Andersson <andersson@kernel.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org
Subject: Re: [PATCH 7/7] drm/msm/dpu: move INTF tearing checks to dpu_encoder_phys_cmd_init
Date: Sun, 30 Jul 2023 03:16:59 +0300 [thread overview]
Message-ID: <4f0da76f-7b73-130f-e787-8fd8425da62a@linaro.org> (raw)
In-Reply-To: <b2uzkzfoj4sfg3fx3ufjd7i2x5dbbnsccodrgk7cnfvjf3yak4@tbesdrg2tke4>
On 27/07/2023 23:25, Marijn Suijten wrote:
> On 2023-07-27 22:22:20, Marijn Suijten wrote:
>> On 2023-07-27 19:21:04, Dmitry Baryshkov wrote:
>>> As the INTF is fixed at the encoder creation time, we can move the
>>> check whether INTF supports tearchck to dpu_encoder_phys_cmd_init().
>>> This function can return an error if INTF doesn't have required feature.
>>> Performing this check in dpu_encoder_phys_cmd_tearcheck_config() is less
>>> useful, as this function returns void.
>>>
>>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>> ---
>>> .../drm/msm/disp/dpu1/dpu_encoder_phys_cmd.c | 37 +++++++++++--------
>>> 1 file changed, 21 insertions(+), 16 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys_cmd.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys_cmd.c
>>> index 04a1106101a7..e1dd0e1b4793 100644
>>> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys_cmd.c
>>> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys_cmd.c
>>> @@ -325,24 +325,17 @@ static void dpu_encoder_phys_cmd_tearcheck_config(
>>> unsigned long vsync_hz;
>>> struct dpu_kms *dpu_kms;
>>>
>>> - if (phys_enc->has_intf_te) {
>>> - if (!phys_enc->hw_intf ||
>>> - !phys_enc->hw_intf->ops.enable_tearcheck) {
>>> - DPU_DEBUG_CMDENC(cmd_enc, "tearcheck not supported\n");
>>> - return;
>>> - }
>>> -
>>> - DPU_DEBUG_CMDENC(cmd_enc, "");
>>> - } else {
>>> - if (!phys_enc->hw_pp ||
>>> - !phys_enc->hw_pp->ops.enable_tearcheck) {
>>> - DPU_DEBUG_CMDENC(cmd_enc, "tearcheck not supported\n");
>>> - return;
>>> - }
>>> -
>>> - DPU_DEBUG_CMDENC(cmd_enc, "pp %d\n", phys_enc->hw_pp->idx - PINGPONG_0);
>>> + if (!phys_enc->has_intf_te &&
>>> + (!phys_enc->hw_pp ||
>>> + !phys_enc->hw_pp->ops.enable_tearcheck)) {
>>
>> when is hw_pp assigned? Can't we also check that somewhere in an init
>> phase?
>
> It would happen right before dpu_encoder_phys_cmd_atomic_mode_set()
> where we already happen to check has_intf_te to switch on PP
> intr_readptr vs INTF intr_tear_rd_ptr. Might be the perfect place for
> the pingpong callback checks?
The problem is that mode_set doesn't return an error (by design). I'd
put a TODO here, so that if we ever move/change resource allocation,
this check can be done next to it (atomic_check isn't a good place,
since phys_enc.atomic_check happens before resource reallocation).
>
> - Marijn
>
>>
>> Also, you won't go over 100 chars (not even 80) by having the (!... ||
>> !...) on a single line.
>>
>>> + DPU_DEBUG_CMDENC(cmd_enc, "tearcheck not supported\n");
>>> + return;
>>> }
>>>
>>> + DPU_DEBUG_CMDENC(cmd_enc, "intf %d pp %d\n",
>>> + phys_enc->hw_intf->idx - INTF_0,
>>> + phys_enc->hw_pp->idx - PINGPONG_0);
>>> +
>>> mode = &phys_enc->cached_mode;
>>>
>>> dpu_kms = phys_enc->dpu_kms;
>>> @@ -768,9 +761,21 @@ struct dpu_encoder_phys *dpu_encoder_phys_cmd_init(
>>> phys_enc->intf_mode = INTF_MODE_CMD;
>>> cmd_enc->stream_sel = 0;
>>>
>>> + if (!phys_enc->hw_intf) {
>>> + DPU_ERROR_CMDENC(cmd_enc, "no INTF provided\n");
>>> +
>>> + return ERR_PTR(-EINVAL);
>>> + }
>>> +
>>> if (phys_enc->dpu_kms->catalog->mdss_ver->core_major_ver >= 5)
>>> phys_enc->has_intf_te = true;
>>>
>>> + if (phys_enc->has_intf_te && !phys_enc->hw_intf->ops.enable_tearcheck) {
>>
>> Any other callbacks we could check here, and remove the checks
>> elsewhere?
>>
>> As with enable_tearcheck() though, it does make the code less consistent
>> with its PP counterpart, which is checked ad-hoc everywhere (but maybe
>> that is fixable too).
>>
>> - Marijn
>>
>>> + DPU_ERROR_CMDENC(cmd_enc, "tearcheck not supported\n");
>>> +
>>> + return ERR_PTR(-EINVAL);
>>> + }
>>> +
>>> atomic_set(&cmd_enc->pending_vblank_cnt, 0);
>>> init_waitqueue_head(&cmd_enc->pending_vblank_wq);
>>>
>>> --
>>> 2.39.2
>>>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-07-30 0:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 16:20 [PATCH 0/7] drm/msm/dpu: drop DPU_INTF_TE and DPU_PINGPONG_TE Dmitry Baryshkov
2023-07-27 16:20 ` [PATCH 1/7] drm/msm/dpu: enable PINGPONG TE operations only when supported by HW Dmitry Baryshkov
2023-07-27 20:03 ` Marijn Suijten
2023-07-28 23:59 ` Dmitry Baryshkov
2023-07-29 18:31 ` Marijn Suijten
2023-07-29 23:18 ` Dmitry Baryshkov
2023-07-30 19:26 ` Marijn Suijten
2023-07-27 20:05 ` Marijn Suijten
2023-07-28 23:46 ` Dmitry Baryshkov
2023-07-27 16:20 ` [PATCH 2/7] drm/msm/dpu: drop the DPU_PINGPONG_TE flag Dmitry Baryshkov
2023-07-27 20:08 ` Marijn Suijten
2023-07-27 16:21 ` [PATCH 3/7] drm/msm/dpu: inline _setup_intf_ops() Dmitry Baryshkov
2023-07-27 20:10 ` Marijn Suijten
2023-07-28 23:45 ` Dmitry Baryshkov
2023-07-29 18:28 ` Marijn Suijten
2023-07-29 18:45 ` Dmitry Baryshkov
2023-07-27 16:21 ` [PATCH 4/7] drm/msm/dpu: enable INTF TE operations only when supported by HW Dmitry Baryshkov
2023-07-27 20:12 ` Marijn Suijten
2023-07-30 0:22 ` Dmitry Baryshkov
2023-07-30 19:29 ` Marijn Suijten
2023-07-27 16:21 ` [PATCH 5/7] drm/msm/dpu: drop DPU_INTF_TE feature flag Dmitry Baryshkov
2023-07-27 20:14 ` Marijn Suijten
2023-07-27 20:16 ` Dmitry Baryshkov
2023-07-27 20:24 ` Marijn Suijten
2023-07-27 16:21 ` [PATCH 6/7] drm/msm/dpu: drop useless check from dpu_encoder_phys_cmd_te_rd_ptr_irq() Dmitry Baryshkov
2023-07-27 20:16 ` Marijn Suijten
2023-07-27 16:21 ` [PATCH 7/7] drm/msm/dpu: move INTF tearing checks to dpu_encoder_phys_cmd_init Dmitry Baryshkov
2023-07-27 20:22 ` Marijn Suijten
2023-07-27 20:25 ` Marijn Suijten
2023-07-30 0:16 ` Dmitry Baryshkov [this message]
2023-07-30 19:28 ` Marijn Suijten
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=4f0da76f-7b73-130f-e787-8fd8425da62a@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--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