From: Marijn Suijten <marijn.suijten@somainline.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Sean Paul <sean@poorly.run>, David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>,
Archit Taneja <architt@codeaurora.org>,
Chandan Uddaraju <chandanu@codeaurora.org>,
Sravanthi Kollukuduru <skolluku@codeaurora.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Martin Botka <martin.botka@somainline.org>,
Jami Kettunen <jami.kettunen@somainline.org>,
phone-devel@vger.kernel.org
Subject: Re: [PATCH 0/3] drm/msm/dpu: Initialize SSPP scaler version (from register read)
Date: Thu, 16 Feb 2023 10:04:08 +0100 [thread overview]
Message-ID: <20230216090408.caekj2t2x6asb2jk@SoMainline.org> (raw)
In-Reply-To: <CAA8EJpqL-Vsq7dbK7tfJAGgg2_nV463QYv5zgvRLx_8T2bsXxA@mail.gmail.com>
On 2023-02-16 05:02:32, Dmitry Baryshkov wrote:
> On Thu, 16 Feb 2023 at 01:02, Marijn Suijten
> <marijn.suijten@somainline.org> wrote:
> >
> > Random inspection of the SSPP code surfaced that the version field of
> > dpu_scaler_blk was never assigned in the catalog, resulting in wrong
> > codepaths to be taken within dpu_hw_setup_scaler3 based on a 0 version.
> > Rectify this by reading an accurate value from a register (that is not
> > equal to the values represented by DPU_SSPP_SCALER_QSEEDx enum
> > variants) and deleting dead code around QSEED versioning.
> >
> > Future changes should likely get rid of the distinction between QSEED3
> > and up, as these are now purely determined from the register value.
> > Furthermore implementations could look at the scaler subblk .id field
> > rather than the SSPP feature bits, which currently hold redundant
> > information.
> >
> > ---
> > Marijn Suijten (3):
> > drm/msm/dpu: Read previously-uninitialized SSPP scaler version from hw
> > drm/msm/dpu: Drop unused get_scaler_ver callback from SSPP
> > drm/msm/dpu: Drop unused qseed_type from catalog dpu_caps
>
> The cleanup looks good. However as you are on it, maybe you can also
> add patch 4, dropping DPU_SSPP_SCALER_QSEED3LITE and
> DPU_SSPP_SCALER_QSEED4 in favour of using QSEED3 for all these
> scalers?
I surely can! Do you mind if I rename it to QSEED3_AND_UP for clarity?
How about the second question, dropping this redundant information from
the SSPP feature flags and only looking at the scaler_blk.id?
> As we are going to use scaler_version to distinguish between
> them, it would be logical not to duplicate that bit of information
> (not to mention all the possible troubles if scaler_version disagrees
> with the sblk->scaler_blk.id).
Note that we had a similar discussion for UBWC HW decoder version and it
was decided to go the opposite route [1]. That may have been for
technical reasons (unclocked register access), but it's an inconsistent
approach to say the least.
[1]: https://lore.kernel.org/linux-arm-msm/71f96910-e7b1-92f9-ae15-79bd1da40a0d@quicinc.com/
- Marijn
prev parent reply other threads:[~2023-02-16 9:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 23:02 Marijn Suijten
2023-02-15 23:02 ` [PATCH 1/3] drm/msm/dpu: Read previously-uninitialized SSPP scaler version from hw Marijn Suijten
2023-02-16 2:22 ` Dmitry Baryshkov
2023-02-16 8:31 ` Marijn Suijten
2023-02-16 16:34 ` Dmitry Baryshkov
2023-02-16 21:46 ` Marijn Suijten
2023-02-17 15:00 ` Dmitry Baryshkov
2023-02-15 23:02 ` [PATCH 2/3] drm/msm/dpu: Drop unused get_scaler_ver callback from SSPP Marijn Suijten
2023-02-16 2:23 ` Dmitry Baryshkov
2023-02-15 23:02 ` [PATCH 3/3] drm/msm/dpu: Drop unused qseed_type from catalog dpu_caps Marijn Suijten
2023-02-16 2:57 ` Dmitry Baryshkov
2023-02-16 3:02 ` [PATCH 0/3] drm/msm/dpu: Initialize SSPP scaler version (from register read) Dmitry Baryshkov
2023-02-16 9:04 ` Marijn Suijten [this message]
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=20230216090408.caekj2t2x6asb2jk@SoMainline.org \
--to=marijn.suijten@somainline.org \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@somainline.org \
--cc=architt@codeaurora.org \
--cc=chandanu@codeaurora.org \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jami.kettunen@somainline.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.botka@somainline.org \
--cc=phone-devel@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=skolluku@codeaurora.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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®