From: Jeykumar Sankaran <quic_jeykumar@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Abhinav Kumar <quic_abhinavk@quicinc.com>
Cc: <freedreno@lists.freedesktop.org>,
<linux-arm-msm@vger.kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
<dri-devel@lists.freedesktop.org>,
"Stephen Boyd" <swboyd@chromium.org>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>
Subject: Re: [Freedreno] [PATCH 2/3] drm/msm/dpu: access QSEED registers directly
Date: Wed, 26 Apr 2023 09:57:22 -0700 [thread overview]
Message-ID: <06f52002-c99a-a582-1308-6e8a4560a541@quicinc.com> (raw)
In-Reply-To: <20230422000839.1921358-3-dmitry.baryshkov@linaro.org>
On 4/21/2023 5:08 PM, Dmitry Baryshkov wrote:
> Stop using _sspp_subblk_offset() to get offset of the scaler_blk. Inline
> this function and use ctx->cap->sblk->scaler_blk.base directly.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c | 27 +++++++--------------
> 1 file changed, 9 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c
> index fce135f010d4..22c59f2250be 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c
> @@ -149,11 +149,6 @@ static int _sspp_subblk_offset(struct dpu_hw_sspp *ctx,
> sblk = ctx->cap->sblk;
>
> switch (s_id) {
> - case DPU_SSPP_SCALER_QSEED2:
> - case DPU_SSPP_SCALER_QSEED3:
> - case DPU_SSPP_SCALER_RGB:
> - *idx = sblk->scaler_blk.base;
> - break;
> case DPU_SSPP_CSC:
> case DPU_SSPP_CSC_10BIT:
> *idx = sblk->csc_blk.base;
> @@ -195,22 +190,21 @@ static void dpu_hw_sspp_setup_multirect(struct dpu_sw_pipe *pipe)
> static void _sspp_setup_opmode(struct dpu_hw_sspp *ctx,
> u32 mask, u8 en)
> {
> - u32 idx;
> + const struct dpu_sspp_sub_blks *sblk = ctx->cap->sblk;
> u32 opmode;
>
> if (!test_bit(DPU_SSPP_SCALER_QSEED2, &ctx->cap->features) ||
> - _sspp_subblk_offset(ctx, DPU_SSPP_SCALER_QSEED2, &idx) ||
> !test_bit(DPU_SSPP_CSC, &ctx->cap->features))
> return;
>
> - opmode = DPU_REG_READ(&ctx->hw, SSPP_VIG_OP_MODE + idx);
> + opmode = DPU_REG_READ(&ctx->hw, sblk->scaler_blk.base + SSPP_VIG_OP_MODE);
>
> if (en)
> opmode |= mask;
> else
> opmode &= ~mask;
>
> - DPU_REG_WRITE(&ctx->hw, SSPP_VIG_OP_MODE + idx, opmode);
> + DPU_REG_WRITE(&ctx->hw, sblk->scaler_blk.base + SSPP_VIG_OP_MODE, opmode);
> }
>
> static void _sspp_setup_csc10_opmode(struct dpu_hw_sspp *ctx,
> @@ -416,25 +410,22 @@ static void _dpu_hw_sspp_setup_scaler3(struct dpu_hw_sspp *ctx,
> struct dpu_hw_scaler3_cfg *scaler3_cfg,
> const struct dpu_format *format)
> {
> - u32 idx;
> -
> - if (_sspp_subblk_offset(ctx, DPU_SSPP_SCALER_QSEED3, &idx)
> - || !scaler3_cfg)
> + if (!ctx || !scaler3_cfg)
> return;
>
> - dpu_hw_setup_scaler3(&ctx->hw, scaler3_cfg, idx,
> + dpu_hw_setup_scaler3(&ctx->hw, scaler3_cfg,
> + ctx->cap->sblk->scaler_blk.base,
> ctx->cap->sblk->scaler_blk.version,
> format);
> }
>
> static u32 _dpu_hw_sspp_get_scaler3_ver(struct dpu_hw_sspp *ctx)
> {
> - u32 idx;
> -
> - if (!ctx || _sspp_subblk_offset(ctx, DPU_SSPP_SCALER_QSEED3, &idx))
> + if (!ctx)
> return 0;
>
> - return dpu_hw_get_scaler3_ver(&ctx->hw, idx);
> + return dpu_hw_get_scaler3_ver(&ctx->hw,
> + ctx->cap->sblk->scaler_blk.base);
> }
>
> /*
Reviewed-by: Jeykumar Sankaran <quic_jeykumar@quicinc.com>
next prev parent reply other threads:[~2023-04-26 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 0:08 [PATCH 0/3] drm/msm/dpu: drop _sspp_subblk_offset() Dmitry Baryshkov
2023-04-22 0:08 ` [PATCH 1/3] drm/msm/dpu: drop SSPP's SRC subblock Dmitry Baryshkov
2023-04-26 16:53 ` [Freedreno] " Jeykumar Sankaran
2023-04-22 0:08 ` [PATCH 2/3] drm/msm/dpu: access QSEED registers directly Dmitry Baryshkov
2023-04-26 16:57 ` Jeykumar Sankaran [this message]
2023-04-22 0:08 ` [PATCH 3/3] drm/msm/dpu: access CSC/CSC10 " Dmitry Baryshkov
2023-04-26 16:58 ` [Freedreno] " Jeykumar Sankaran
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=06f52002-c99a-a582-1308-6e8a4560a541@quicinc.com \
--to=quic_jeykumar@quicinc.com \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.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