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: <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>,
Marijn Suijten <marijn.suijten@somainline.org>
Subject: Re: [PATCH 4/6] drm/msm/mdss: populate missing data
Date: Wed, 26 Jul 2023 15:30:31 -0700 [thread overview]
Message-ID: <61b0792d-aa62-03ea-bb2c-aa9392251519@quicinc.com> (raw)
In-Reply-To: <20230521171026.4159495-5-dmitry.baryshkov@linaro.org>
On 5/21/2023 10:10 AM, Dmitry Baryshkov wrote:
> As we are going to use MDSS data for DPU programming, populate missing
> MDSS data. The UBWC 1.0 and no UBWC cases do not require MDSS
> programming, so skip them.
>
Can you pls point me to the downstream references you used for msm8998?
Was that just taken from catalog? If so I would ask for the reference
for the catalog too.
As per the register the decoder version is 0x0 and not 1.
Even encoder version is 0 from what i see and not 1. Thats why a
dec_version of UBWC_1_0 is not doing anything i assume.
Some additional questions:
1) Does the whole chunk in dpu_hw_sspp_setup_format() which handles ubwc
programming need to be protected by if (ctx->ubwc) now ?
2) 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.
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> drivers/gpu/drm/msm/msm_mdss.c | 21 +++++++++++++++++++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/msm/msm_mdss.c b/drivers/gpu/drm/msm/msm_mdss.c
> index ed836c659688..9bb7be4b9ebb 100644
> --- a/drivers/gpu/drm/msm/msm_mdss.c
> +++ b/drivers/gpu/drm/msm/msm_mdss.c
> @@ -264,6 +264,10 @@ static int msm_mdss_enable(struct msm_mdss *msm_mdss)
> * UBWC_n and the rest of params comes from hw data.
> */
> switch (msm_mdss->mdss_data->ubwc_dec_version) {
> + case 0: /* no UBWC */
> + case UBWC_1_0:
> + /* do nothing */
> + break;
> case UBWC_2_0:
> msm_mdss_setup_ubwc_dec_20(msm_mdss);
> break;
> @@ -502,10 +506,22 @@ static int mdss_remove(struct platform_device *pdev)
> return 0;
> }
>
> +static const struct msm_mdss_data msm8998_data = {
> + .ubwc_enc_version = UBWC_1_0,
> + .ubwc_dec_version = UBWC_1_0,
> + .highest_bank_bit = 1,
> +};
> +
> +static const struct msm_mdss_data qcm2290_data = {
> + /* no UBWC */
> + .highest_bank_bit = 0x2,
> +};
> +
> static const struct msm_mdss_data sc7180_data = {
> .ubwc_enc_version = UBWC_2_0,
> .ubwc_dec_version = UBWC_2_0,
> .ubwc_static = 0x1e,
> + .highest_bank_bit = 0x3,
> };
>
> static const struct msm_mdss_data sc7280_data = {
> @@ -550,6 +566,7 @@ static const struct msm_mdss_data sm6115_data = {
> .ubwc_dec_version = UBWC_2_0,
> .ubwc_swizzle = 7,
> .ubwc_static = 0x11f,
> + .highest_bank_bit = 0x1,
> };
>
> static const struct msm_mdss_data sm8250_data = {
> @@ -574,8 +591,8 @@ static const struct msm_mdss_data sm8550_data = {
>
> static const struct of_device_id mdss_dt_match[] = {
> { .compatible = "qcom,mdss" },
> - { .compatible = "qcom,msm8998-mdss" },
> - { .compatible = "qcom,qcm2290-mdss" },
> + { .compatible = "qcom,msm8998-mdss", .data = &msm8998_data },
> + { .compatible = "qcom,qcm2290-mdss", .data = &qcm2290_data },
> { .compatible = "qcom,sdm845-mdss", .data = &sdm845_data },
> { .compatible = "qcom,sc7180-mdss", .data = &sc7180_data },
> { .compatible = "qcom,sc7280-mdss", .data = &sc7280_data },
next prev parent reply other threads:[~2023-07-26 22:30 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 [this message]
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
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=61b0792d-aa62-03ea-bb2c-aa9392251519@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=andersson@kernel.org \
--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