From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Abhinav Kumar <quic_abhinavk@quicinc.com>
Cc: 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: [PATCH v2 0/3] drm/msm/dpu: drop _sspp_subblk_offset()
Date: Sat, 29 Apr 2023 04:23:50 +0300 [thread overview]
Message-ID: <20230429012353.2569481-1-dmitry.baryshkov@linaro.org> (raw)
Rework dpu_hw_sspp.c to access sblk base address directly rather than
getting the sblk address through indirect function call.
Changes since v1:
- Dropped DPU_SSPP_SRC feature, making SRC-related functions mandatory
(suggested by Jeykumar)
Dmitry Baryshkov (3):
drm/msm/dpu: drop SSPP's SRC subblock
drm/msm/dpu: access QSEED registers directly
drm/msm/dpu: access CSC/CSC10 registers directly
.../gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c | 14 +-
.../gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h | 14 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c | 198 +++++++-----------
3 files changed, 76 insertions(+), 150 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-29 1:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 1:23 Dmitry Baryshkov [this message]
2023-04-29 1:23 ` [PATCH v2 1/3] drm/msm/dpu: drop SSPP's SRC subblock Dmitry Baryshkov
2023-05-18 19:14 ` Marijn Suijten
2023-05-18 21:06 ` Dmitry Baryshkov
2023-05-18 21:39 ` Marijn Suijten
2023-05-18 21:40 ` Dmitry Baryshkov
2023-05-19 12:05 ` Marijn Suijten
2023-04-29 1:23 ` [PATCH v2 2/3] drm/msm/dpu: access QSEED registers directly Dmitry Baryshkov
2023-05-18 19:18 ` Marijn Suijten
2023-04-29 1:23 ` [PATCH v2 3/3] drm/msm/dpu: access CSC/CSC10 " Dmitry Baryshkov
2023-05-18 19:20 ` Marijn Suijten
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=20230429012353.2569481-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--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