From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: "Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Rob Clark" <robdclark@gmail.com>, "Sean Paul" <sean@poorly.run>,
"Marijn Suijten" <marijn.suijten@somainline.org>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Barnabás Czémán" <barnabas.czeman@mainlining.org>,
"Konrad Dybcio" <konradybcio@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<freedreno@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 5/5] drm/msm/dpu: remove DSC feature bit for PINGPONG on SDM630
Date: Mon, 28 Apr 2025 19:01:55 -0700 [thread overview]
Message-ID: <c1587cf2-b389-45f4-9dc8-db29bbbe5eb0@quicinc.com> (raw)
In-Reply-To: <20250301-dpu-fix-catalog-v2-5-498271be8b50@linaro.org>
On 3/1/2025 1:24 AM, Dmitry Baryshkov wrote:
> The SDM630 platform doesn't have DSC blocks nor does have it DSC
> registers in the PINGPONG block. Drop the DPU_PINGPONG_DSC feature bit
> from the PINGPONG's feature mask, replacing PINGPONG_SDM845_MASK with
> BIT(DPU_PINGPONG_DITHER).
>
> Fixes: 7204df5e7e68 ("drm/msm/dpu: add support for SDM660 and SDM630 platforms")
> Reported-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>
> ---
> Note, Konrad pointed out that vendor DT doesn't define DIPTHER support
> for this platform, however I believe this is because support for this
> platform predates DITHER support in the vendor kernels.
> ---
Yes this is correct. This chipset has dither support in ping-pong.
> drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_3_3_sdm630.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_3_3_sdm630.h b/drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_3_3_sdm630.h
> index 3aed9aa4c533f167ece7b4a5eb84fe49c4929df5..99c0f824d8f00474812bde12e7d83ba3de1834f1 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_3_3_sdm630.h
> +++ b/drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_3_3_sdm630.h
> @@ -115,14 +115,14 @@ static const struct dpu_pingpong_cfg sdm630_pp[] = {
> {
> .name = "pingpong_0", .id = PINGPONG_0,
> .base = 0x70000, .len = 0xd4,
> - .features = PINGPONG_SDM845_MASK,
> + .features = BIT(DPU_PINGPONG_DITHER),
> .sblk = &sdm845_pp_sblk,
> .intr_done = DPU_IRQ_IDX(MDP_SSPP_TOP0_INTR, 8),
> .intr_rdptr = DPU_IRQ_IDX(MDP_SSPP_TOP0_INTR, 12),
> }, {
> .name = "pingpong_2", .id = PINGPONG_2,
> .base = 0x71000, .len = 0xd4,
> - .features = PINGPONG_SDM845_MASK,
> + .features = BIT(DPU_PINGPONG_DITHER),
> .sblk = &sdm845_pp_sblk,
> .intr_done = DPU_IRQ_IDX(MDP_SSPP_TOP0_INTR, 10),
> .intr_rdptr = DPU_IRQ_IDX(MDP_SSPP_TOP0_INTR, 14),
>
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
next prev parent reply other threads:[~2025-04-29 2:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 9:24 [PATCH v2 0/5] drm/msm/dpu: disable DSC on some of old DPU models Dmitry Baryshkov
2025-03-01 9:24 ` [PATCH v2 1/5] drm/msm/dpu: remove DSC feature bit for PINGPONG on MSM8937 Dmitry Baryshkov
2025-04-29 0:37 ` Abhinav Kumar
2025-03-01 9:24 ` [PATCH v2 2/5] drm/msm/dpu: remove DSC feature bit for PINGPONG on MSM8917 Dmitry Baryshkov
2025-04-29 1:00 ` Abhinav Kumar
2025-03-01 9:24 ` [PATCH v2 3/5] drm/msm/dpu: remove DSC feature bit for PINGPONG on MSM8953 Dmitry Baryshkov
2025-04-29 1:21 ` Abhinav Kumar
2025-03-01 9:24 ` [PATCH v2 4/5] drm/msm/dpu: drop TE2 definitions Dmitry Baryshkov
2025-04-29 1:33 ` Abhinav Kumar
2025-04-29 12:16 ` Dmitry Baryshkov
2025-04-29 18:27 ` Abhinav Kumar
2025-03-01 9:24 ` [PATCH v2 5/5] drm/msm/dpu: remove DSC feature bit for PINGPONG on SDM630 Dmitry Baryshkov
2025-04-29 2:01 ` Abhinav Kumar [this message]
2025-05-04 16:13 ` [PATCH v2 0/5] drm/msm/dpu: disable DSC on some of old DPU models Dmitry Baryshkov
2025-05-19 10:58 ` 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=c1587cf2-b389-45f4-9dc8-db29bbbe5eb0@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=airlied@gmail.com \
--cc=barnabas.czeman@mainlining.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
/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®