From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>,
Rob Clark <robdclark@gmail.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Kuogee Hsieh <quic_khsieh@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] drm/msm/dpu: Add missing DPU_DSC_OUTPUT_CTRL to SC7280
Date: Thu, 21 Sep 2023 09:04:39 +0200 [thread overview]
Message-ID: <ce67c10d-a589-dc2e-76cf-fb5cfaa48c66@linaro.org> (raw)
In-Reply-To: <444d125c-2a87-3bae-6ea0-b76dffeb63ef@quicinc.com>
On 9/21/23 02:01, Abhinav Kumar wrote:
>
>
> On 9/20/2023 3:46 PM, Konrad Dybcio wrote:
>> DPU_DSC_OUTPUT_CTRL should be enabled for all platforms with a CTL
>> CFG 1.0.0. SC7280 is one of them. Add it.
>>
>
> sc7280 and all other chipsets using DSC 1.2 use dpu_hw_dsc_init_1_2 and
> not dpu_hw_dsc_init.
>
> dpu_hw_dsc_init_1_2 assigns the dsc_bind_pingpong_blk op by default.
>
> So this change is not needed.
Gah, I don't like that we do it behind the scenes but I agree it's a NOP..
Konrad
next prev parent reply other threads:[~2023-09-21 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 22:46 [PATCH 0/3] SC7280 DPU fixups Konrad Dybcio
2023-09-20 22:46 ` [PATCH 1/3] drm/msm/dpu: Fix SC7280 PP length Konrad Dybcio
2023-09-20 23:41 ` Abhinav Kumar
2023-09-21 7:01 ` Konrad Dybcio
2023-09-20 22:46 ` [PATCH 2/3] drm/msm/dpu: Add missing DPU_DSC_OUTPUT_CTRL to SC7280 Konrad Dybcio
2023-09-21 0:01 ` Abhinav Kumar
2023-09-21 7:04 ` Konrad Dybcio [this message]
2023-09-20 22:46 ` [PATCH 3/3] drm/msm/dpu: Fix SC7280 DSC block length Konrad Dybcio
2023-09-21 0:10 ` Abhinav Kumar
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=ce67c10d-a589-dc2e-76cf-fb5cfaa48c66@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=airlied@gmail.com \
--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=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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®