From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>
Cc: 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 2/2] drm/msm/dpu: remove CRTC frame event callback registration
Date: Fri, 19 May 2023 19:11:24 +0300 [thread overview]
Message-ID: <7cbc5958-542a-9119-e16d-9967a2131f1d@linaro.org> (raw)
In-Reply-To: <bba66f67-8c9a-1372-a3a4-2f19e966b6a0@quicinc.com>
On 14/01/2023 02:49, Abhinav Kumar wrote:
>
>
> On 1/2/2023 7:47 AM, Dmitry Baryshkov wrote:
>> The frame event callback is always set to dpu_crtc_frame_event_cb() (or
>> to NULL) and the data is always either the CRTC itself or NULL
>> (correpondingly). Thus drop the event callback registration, call the
>> dpu_crtc_frame_event_cb() directly and gate on the dpu_enc->crtc
>> assigned using dpu_encoder_assign_crtc().
>
> I suggest you wait till we sort out the PSR series for this, especially
> this patch https://patchwork.freedesktop.org/patch/515787/
>
> There is going to be some change in this code when PSR is pushed again
> sometime early next week because PSR will touch the crtc assignment code
> (dpu_enc->crtc),
>
> Based on how we all like that patch, we can get back to this one as this
> one is a minor cleanup.
As the PSR series have landed, I'd like to point to this patch again.
>
>>
>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>> ---
>> drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 17 +--------
>> drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.h | 14 +++++++
>> drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 41 +++------------------
>> drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.h | 10 -----
>> drivers/gpu/drm/msm/disp/dpu1/dpu_trace.h | 4 --
>> 5 files changed, 21 insertions(+), 65 deletions(-)
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-05-19 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 15:47 [PATCH 1/2] drm/msm/dpu: remove dpu_encoder_virt_ops Dmitry Baryshkov
2023-01-02 15:47 ` [PATCH 2/2] drm/msm/dpu: remove CRTC frame event callback registration Dmitry Baryshkov
2023-01-14 0:49 ` Abhinav Kumar
2023-05-19 16:11 ` Dmitry Baryshkov [this message]
2023-01-14 0:32 ` [PATCH 1/2] drm/msm/dpu: remove dpu_encoder_virt_ops Abhinav Kumar
2023-01-18 2:06 ` 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=7cbc5958-542a-9119-e16d-9967a2131f1d@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