From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>,
Kuogee Hsieh <quic_khsieh@quicinc.com>,
dri-devel@lists.freedesktop.org, robdclark@gmail.com,
sean@poorly.run, swboyd@chromium.org, dianders@chromium.org,
vkoul@kernel.org, daniel@ffwll.ch, airlied@gmail.com,
agross@kernel.org, andersson@kernel.org
Cc: quic_jesszhan@quicinc.com, quic_sbillaka@quicinc.com,
marijn.suijten@somainline.org, freedreno@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 6/8] drm/msm/dpu: separate DSC flush update out of interface
Date: Fri, 12 May 2023 21:50:37 +0300 [thread overview]
Message-ID: <e3579cea-1764-26ff-ba9d-6eb23a0aaef0@linaro.org> (raw)
In-Reply-To: <5319b87a-9a4c-1786-9ea9-b9015ee56357@quicinc.com>
On 12/05/2023 21:47, Abhinav Kumar wrote:
>
>
> On 5/12/2023 11:21 AM, Dmitry Baryshkov wrote:
>> On 12/05/2023 21:00, Kuogee Hsieh wrote:
>>> Current DSC flush update is piggyback inside dpu_hw_ctl_intf_cfg_v1().
>>> This patch separates DSC flush away from dpu_hw_ctl_intf_cfg_v1() by
>>> adding dpu_hw_ctl_update_pending_flush_dsc_v1() to handle both per
>>> DSC engine and DSC flush bits at same time to make it consistent with
>>> the location of flush programming of other dpu sub blocks.
>>>
>>> Signed-off-by: Kuogee Hsieh <quic_khsieh@quicinc.com>
>>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>> ---
>>> drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 14 ++++++++++++--
>>> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_ctl.c | 22
>>> ++++++++++++++++------
>>> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_ctl.h | 10 ++++++++++
>>> 3 files changed, 38 insertions(+), 8 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>>> b/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>>> index ffa6f04..5cae70e 100644
>>> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>>> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>>> @@ -1834,12 +1834,18 @@ dpu_encoder_dsc_initial_line_calc(struct
>>> drm_dsc_config *dsc,
>>> return DIV_ROUND_UP(total_pixels, dsc->slice_width);
>>> }
>>> -static void dpu_encoder_dsc_pipe_cfg(struct dpu_hw_dsc *hw_dsc,
>>> +static void dpu_encoder_dsc_pipe_cfg(struct dpu_encoder_virt *dpu_enc,
>>> + struct dpu_hw_dsc *hw_dsc,
>>> struct dpu_hw_pingpong *hw_pp,
>>> struct drm_dsc_config *dsc,
>>> u32 common_mode,
>>> u32 initial_lines)
>>> {
>>> + struct dpu_encoder_phys *cur_master = dpu_enc->cur_master;
>>> + struct dpu_hw_ctl *ctl;
>>> +
>>> + ctl = cur_master->hw_ctl;
>>
>> Just for my understanding: if we have a bonded DSI @ sdm845, should
>> both flashes go to the master CTL or each flush should go to the
>> corresponding CTL?
>>
>
> Is this question for DSC or just general question about flush?
>
> I dont see an explicit DSC flush needed in sdm845 at the ctl level.
>
> If the question is about general flush involving two control paths, we
> need to combine the flushes and they goto the master only. Please refer
> to below part in sde_encoder.c
And this is because we have a single CTL to flush on sm8150+, isn't it?
>
> 4243 /* for split flush, combine pending flush masks and send to
> master */
> 4244 if (pending_flush.pending_flush_mask && sde_enc->cur_master) {
> 4245 ctl = sde_enc->cur_master->hw_ctl;
> 4246 if (config_changed && ctl->ops.reg_dma_flush)
> 4247 ctl->ops.reg_dma_flush(ctl, is_regdma_blocking);
> 4248 _sde_encoder_trigger_flush(&sde_enc->base,
> sde_enc->cur_master,
> 4249 &pending_flush,
> 4250 config_changed);
> 4251 }
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-05-12 18:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 18:00 [PATCH v8 0/8] add DSC 1.2 dpu supports Kuogee Hsieh
2023-05-12 18:00 ` [PATCH v8 1/8] drm/msm/dpu: add dsc blocks for remaining chipsets in catalog Kuogee Hsieh
2023-05-14 21:39 ` Marijn Suijten
2023-05-15 18:20 ` Abhinav Kumar
2023-05-15 20:07 ` Marijn Suijten
2023-05-15 20:58 ` Abhinav Kumar
2023-05-15 21:23 ` Marijn Suijten
2023-05-15 21:26 ` Abhinav Kumar
2023-05-12 18:00 ` [PATCH v8 2/8] drm/msm/dpu: add DPU_PINGPONG_DSC feature bit for DPU < 7.0.0 Kuogee Hsieh
2023-05-12 18:17 ` Dmitry Baryshkov
2023-05-13 19:26 ` Marijn Suijten
2023-05-12 18:00 ` [PATCH v8 3/8] drm/msm/dpu: test DPU_PINGPONG_DSC bit before assign DSC ops to PINGPONG Kuogee Hsieh
2023-05-14 21:43 ` Marijn Suijten
2023-05-12 18:00 ` [PATCH v8 4/8] drm/msm/dpu: Introduce PINGPONG_NONE to disconnect DSC from PINGPONG Kuogee Hsieh
2023-05-12 18:00 ` [PATCH v8 5/8] drm/msm/dpu: add support for DSC encoder v1.2 engine Kuogee Hsieh
2023-05-12 18:19 ` Dmitry Baryshkov
2023-05-12 20:48 ` Kuogee Hsieh
2023-05-12 21:04 ` Dmitry Baryshkov
2023-05-14 21:46 ` Marijn Suijten
2023-05-15 17:46 ` Kuogee Hsieh
2023-05-15 18:08 ` Dmitry Baryshkov
2023-05-15 20:11 ` Marijn Suijten
2023-05-14 22:18 ` Marijn Suijten
2023-05-15 17:06 ` Kuogee Hsieh
2023-05-15 20:17 ` Marijn Suijten
2023-05-15 17:36 ` Kuogee Hsieh
2023-05-12 18:00 ` [PATCH v8 6/8] drm/msm/dpu: separate DSC flush update out of interface Kuogee Hsieh
2023-05-12 18:21 ` Dmitry Baryshkov
2023-05-12 18:47 ` Abhinav Kumar
2023-05-12 18:50 ` Dmitry Baryshkov [this message]
2023-05-12 19:05 ` Abhinav Kumar
2023-05-15 21:52 ` Marijn Suijten
2023-05-12 18:00 ` [PATCH v8 7/8] drm/msm/dpu: add DSC 1.2 hw blocks for relevant chipsets Kuogee Hsieh
2023-05-15 21:21 ` Marijn Suijten
2023-05-15 22:03 ` Abhinav Kumar
2023-05-15 22:10 ` [Freedreno] " Abhinav Kumar
2023-05-15 22:23 ` Marijn Suijten
2023-05-15 23:58 ` Abhinav Kumar
2023-05-15 21:24 ` Marijn Suijten
2023-05-12 18:00 ` [PATCH v8 8/8] drm/msm/dpu: tear down DSC data path when DSC disabled Kuogee Hsieh
2023-05-14 21:31 ` [PATCH v8 0/8] add DSC 1.2 dpu supports 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=e3579cea-1764-26ff-ba9d-6eb23a0aaef0@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--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=marijn.suijten@somainline.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_jesszhan@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=quic_sbillaka@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®