From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
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 5/6] drm/msm/dpu: use MDSS data for programming SSPP
Date: Wed, 26 Jul 2023 16:20:16 -0700 [thread overview]
Message-ID: <4e35dabb-640e-8de6-d98a-619b2f80cfb6@quicinc.com> (raw)
In-Reply-To: <20230521171026.4159495-6-dmitry.baryshkov@linaro.org>
On 5/21/2023 10:10 AM, Dmitry Baryshkov wrote:
> Switch to using data from MDSS driver to program the SSPP fetch and UBWC
> configuration.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c | 18 +++++++++++-------
> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.h | 7 +++++--
> drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 16 +++++++++++++++-
> drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 1 +
> drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c | 3 ++-
> drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h | 2 ++
> 6 files changed, 36 insertions(+), 11 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 cf70a9bd1034..bfd82c2921af 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c
> @@ -8,6 +8,8 @@
> #include "dpu_hw_sspp.h"
> #include "dpu_kms.h"
>
> +#include "msm_mdss.h"
> +
> #include <drm/drm_file.h>
>
> #define DPU_FETCH_CONFIG_RESET_VALUE 0x00000087
> @@ -308,26 +310,26 @@ static void dpu_hw_sspp_setup_format(struct dpu_sw_pipe *pipe,
> DPU_REG_WRITE(c, SSPP_FETCH_CONFIG,
> DPU_FETCH_CONFIG_RESET_VALUE |
> ctx->ubwc->highest_bank_bit << 18);
Does this needs to be protected with if ctx->ubwc check?
> - switch (ctx->ubwc->ubwc_version) {
> - case DPU_HW_UBWC_VER_10:
> + switch (ctx->ubwc->ubwc_enc_version) {
> + case UBWC_1_0:
The values of UBWC_x_x dont match the values of DPU_HW_UBWC_VER_xx.
What was the reason for the catalog to go with DPU_HW_UBWC_VER_xx in the
catalog for the encoder version in the first place? Because looking at
the registers UBWC_x_x is the correct value.
If we cannot find the reason why, it should be noted in the commit text
that the values we are using did change.
> fast_clear = fmt->alpha_enable ? BIT(31) : 0;
> DPU_REG_WRITE(c, SSPP_UBWC_STATIC_CTRL,
> fast_clear | (ctx->ubwc->ubwc_swizzle & 0x1) |
> BIT(8) |
> (ctx->ubwc->highest_bank_bit << 4));
> break;
> - case DPU_HW_UBWC_VER_20:
> + case UBWC_2_0:
> fast_clear = fmt->alpha_enable ? BIT(31) : 0;
> DPU_REG_WRITE(c, SSPP_UBWC_STATIC_CTRL,
> fast_clear | (ctx->ubwc->ubwc_swizzle) |
> (ctx->ubwc->highest_bank_bit << 4));
> break;
> - case DPU_HW_UBWC_VER_30:
> + case UBWC_3_0:
> DPU_REG_WRITE(c, SSPP_UBWC_STATIC_CTRL,
> BIT(30) | (ctx->ubwc->ubwc_swizzle) |
> (ctx->ubwc->highest_bank_bit << 4));
> break;
> - case DPU_HW_UBWC_VER_40:
> + case UBWC_4_0:
> DPU_REG_WRITE(c, SSPP_UBWC_STATIC_CTRL,
> DPU_FORMAT_IS_YUV(fmt) ? 0 : BIT(30));
> break;
> @@ -793,7 +795,9 @@ static const struct dpu_sspp_cfg *_sspp_offset(enum dpu_sspp sspp,
> }
>
> struct dpu_hw_sspp *dpu_hw_sspp_init(enum dpu_sspp idx,
> - void __iomem *addr, const struct dpu_mdss_cfg *catalog)
> + void __iomem *addr,
> + const struct dpu_mdss_cfg *catalog,
> + const struct msm_mdss_data *mdss_data)
> {
> struct dpu_hw_sspp *hw_pipe;
> const struct dpu_sspp_cfg *cfg;
> @@ -813,7 +817,7 @@ struct dpu_hw_sspp *dpu_hw_sspp_init(enum dpu_sspp idx,
>
> /* Assign ops */
> hw_pipe->catalog = catalog;
> - hw_pipe->ubwc = catalog->ubwc;
> + hw_pipe->ubwc = mdss_data;
> hw_pipe->idx = idx;
> hw_pipe->cap = cfg;
> _setup_layer_ops(hw_pipe, hw_pipe->cap->features);
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.h b/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.h
> index 74b98b6b3bc3..8d4ae9d24674 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.h
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.h
> @@ -351,7 +351,7 @@ struct dpu_hw_sspp {
> struct dpu_hw_blk base;
> struct dpu_hw_blk_reg_map hw;
> const struct dpu_mdss_cfg *catalog;
> - const struct dpu_ubwc_cfg *ubwc;
> + const struct msm_mdss_data *ubwc;
>
> /* Pipe */
> enum dpu_sspp idx;
> @@ -368,9 +368,12 @@ struct dpu_kms;
> * @idx: Pipe index for which driver object is required
> * @addr: Mapped register io address of MDP
> * @catalog : Pointer to mdss catalog data
> + * @mdss_data: UBWC / MDSS configuration data
> */
> struct dpu_hw_sspp *dpu_hw_sspp_init(enum dpu_sspp idx,
> - void __iomem *addr, const struct dpu_mdss_cfg *catalog);
> + void __iomem *addr,
> + const struct dpu_mdss_cfg *catalog,
> + const struct msm_mdss_data *mdss_data);
>
> /**
> * dpu_hw_sspp_destroy(): Destroys SSPP driver context
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
> index 0e7a68714e9e..a4293dc0b61b 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
> @@ -22,6 +22,7 @@
>
> #include "msm_drv.h"
> #include "msm_mmu.h"
> +#include "msm_mdss.h"
> #include "msm_gem.h"
> #include "disp/msm_disp_snapshot.h"
>
> @@ -1066,7 +1067,20 @@ static int dpu_kms_hw_init(struct msm_kms *kms)
> goto power_error;
> }
>
> - rc = dpu_rm_init(&dpu_kms->rm, dpu_kms->catalog, dpu_kms->mmio);
> + dpu_kms->mdss = msm_mdss_get_mdss_data(dpu_kms->pdev->dev.parent);
> + if (IS_ERR(dpu_kms->mdss)) {
> + rc = PTR_ERR(dpu_kms->mdss);
> + DPU_ERROR("failed to get MDSS data: %d\n", rc);
> + goto power_error;
> + }
> +
> + if (!dpu_kms->mdss) {
> + rc = -EINVAL;
> + DPU_ERROR("NULL MDSS data\n");
> + goto power_error;
> + }
> +
> + rc = dpu_rm_init(&dpu_kms->rm, dpu_kms->catalog, dpu_kms->mdss, dpu_kms->mmio);
> if (rc) {
> DPU_ERROR("rm init failed: %d\n", rc);
> goto power_error;
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h
> index aca39a4689f4..797b4ff3e806 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h
> @@ -69,6 +69,7 @@ struct dpu_kms {
> struct msm_kms base;
> struct drm_device *dev;
> const struct dpu_mdss_cfg *catalog;
> + const struct msm_mdss_data *mdss;
>
> /* io/register spaces: */
> void __iomem *mmio, *vbif[VBIF_MAX], *reg_dma;
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c
> index f4dda88a73f7..9ee493465c4b 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c
> @@ -100,6 +100,7 @@ int dpu_rm_destroy(struct dpu_rm *rm)
>
> int dpu_rm_init(struct dpu_rm *rm,
> const struct dpu_mdss_cfg *cat,
> + const struct msm_mdss_data *mdss_data,
> void __iomem *mmio)
> {
> int rc, i;
> @@ -268,7 +269,7 @@ int dpu_rm_init(struct dpu_rm *rm,
> continue;
> }
>
> - hw = dpu_hw_sspp_init(sspp->id, mmio, cat);
> + hw = dpu_hw_sspp_init(sspp->id, mmio, cat, mdss_data);
> if (IS_ERR(hw)) {
> rc = PTR_ERR(hw);
> DPU_ERROR("failed sspp object creation: err %d\n", rc);
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h b/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h
> index d62c2edb2460..2b551566cbf4 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h
> @@ -40,11 +40,13 @@ struct dpu_rm {
> * for all HW blocks.
> * @rm: DPU Resource Manager handle
> * @cat: Pointer to hardware catalog
> + * @mdss_data: Pointer to MDSS / UBWC configuration
> * @mmio: mapped register io address of MDP
> * @Return: 0 on Success otherwise -ERROR
> */
> int dpu_rm_init(struct dpu_rm *rm,
> const struct dpu_mdss_cfg *cat,
> + const struct msm_mdss_data *mdss_data,
> void __iomem *mmio);
>
> /**
next prev parent reply other threads:[~2023-07-26 23:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 17:10 [PATCH 0/6] drm/msm/dpu: use UBWC data from MDSS driver Dmitry Baryshkov
2023-05-21 17:10 ` [PATCH 1/6] drm/msm/mdss: correct UBWC programming for SM8550 Dmitry Baryshkov
2023-05-21 17:10 ` [PATCH 2/6] drm/msm/mdss: rename ubwc_version to ubwc_enc_version Dmitry Baryshkov
2023-07-26 21:07 ` Abhinav Kumar
2023-05-21 17:10 ` [PATCH 3/6] drm/msm/mdss: export UBWC data Dmitry Baryshkov
2023-07-26 21:21 ` Abhinav Kumar
2023-07-26 21:32 ` Dmitry Baryshkov
2023-05-21 17:10 ` [PATCH 4/6] drm/msm/mdss: populate missing data Dmitry Baryshkov
2023-07-26 22:30 ` Abhinav Kumar
2023-07-26 22:58 ` Dmitry Baryshkov
2023-07-26 23:14 ` Abhinav Kumar
2023-07-27 8:37 ` Dmitry Baryshkov
2023-05-21 17:10 ` [PATCH 5/6] drm/msm/dpu: use MDSS data for programming SSPP Dmitry Baryshkov
2023-07-26 23:20 ` Abhinav Kumar [this message]
2023-07-27 8:39 ` Dmitry Baryshkov
2023-07-27 15:24 ` Abhinav Kumar
2023-07-27 15:26 ` Dmitry Baryshkov
2023-07-28 19:24 ` Abhinav Kumar
2023-07-28 19:29 ` Dmitry Baryshkov
2023-05-21 17:10 ` [PATCH 6/6] drm/msm/dpu: drop UBWC configuration Dmitry Baryshkov
2023-07-26 23:23 ` Abhinav Kumar
2023-05-21 21:50 ` [PATCH 0/6] drm/msm/dpu: use UBWC data from MDSS driver Steev Klimaszewski
2023-05-21 21:51 ` 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=4e35dabb-640e-8de6-d98a-619b2f80cfb6@quicinc.com \
--to=quic_abhinavk@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=marijn.suijten@somainline.org \
--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