From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Marijn Suijten <marijn.suijten@somainline.org>
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/7] drm/msm/dpu: use UBWC data from MDSS driver
Date: Sat, 29 Jul 2023 00:33:13 +0300 [thread overview]
Message-ID: <20230728213320.97309-1-dmitry.baryshkov@linaro.org> (raw)
Both DPU and MDSS programming requires knowledge of some of UBWC
parameters. This results in duplication of UBWC data between MDSS and
DPU drivers. To remove such duplication and make the driver more
error-prone, export respective configuration from the MDSS driver and
make DPU use it, instead of bundling a copy of such data.
Changes since v1:
- Rebased on top of msm-next-lumag
- Reworked commit message by patch #5, following the request by Abhinav
- Dropped DPU_HW_UBWC_VER_xx values
- Also removed DPU_MDP_*BWC* defines
Dmitry Baryshkov (7):
drm/msm/mdss: correct UBWC programming for SM8550
drm/msm/mdss: rename ubwc_version to ubwc_enc_version
drm/msm/mdss: export UBWC data
drm/msm/mdss: populate missing data
drm/msm/dpu: use MDSS data for programming SSPP
drm/msm/dpu: drop UBWC configuration
drm/msm/dpu: drop BWC features from DPU_MDP_foo namespace
.../msm/disp/dpu1/catalog/dpu_3_0_msm8998.h | 6 --
.../msm/disp/dpu1/catalog/dpu_4_0_sdm845.h | 6 --
.../msm/disp/dpu1/catalog/dpu_5_0_sm8150.h | 6 --
.../msm/disp/dpu1/catalog/dpu_5_1_sc8180x.h | 6 --
.../msm/disp/dpu1/catalog/dpu_5_4_sm6125.h | 7 --
.../msm/disp/dpu1/catalog/dpu_6_0_sm8250.h | 7 --
.../msm/disp/dpu1/catalog/dpu_6_2_sc7180.h | 6 --
.../msm/disp/dpu1/catalog/dpu_6_3_sm6115.h | 7 --
.../msm/disp/dpu1/catalog/dpu_6_4_sm6350.h | 7 --
.../msm/disp/dpu1/catalog/dpu_6_5_qcm2290.h | 5 -
.../msm/disp/dpu1/catalog/dpu_6_9_sm6375.h | 7 --
.../msm/disp/dpu1/catalog/dpu_7_0_sm8350.h | 6 --
.../msm/disp/dpu1/catalog/dpu_7_2_sc7280.h | 7 --
.../msm/disp/dpu1/catalog/dpu_8_0_sc8280xp.h | 7 --
.../msm/disp/dpu1/catalog/dpu_8_1_sm8450.h | 7 --
.../msm/disp/dpu1/catalog/dpu_9_0_sm8550.h | 6 --
.../gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h | 32 -------
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c | 18 ++--
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.h | 6 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 16 +++-
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 1 +
drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c | 3 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h | 2 +
drivers/gpu/drm/msm/msm_mdss.c | 94 ++++++++++++-------
drivers/gpu/drm/msm/msm_mdss.h | 27 ++++++
25 files changed, 121 insertions(+), 181 deletions(-)
create mode 100644 drivers/gpu/drm/msm/msm_mdss.h
--
2.39.2
next reply other threads:[~2023-07-28 21:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 21:33 Dmitry Baryshkov [this message]
2023-07-28 21:33 ` [PATCH v2 1/7] drm/msm/mdss: correct UBWC programming for SM8550 Dmitry Baryshkov
2023-07-28 21:33 ` [PATCH v2 2/7] drm/msm/mdss: rename ubwc_version to ubwc_enc_version Dmitry Baryshkov
2023-07-28 21:33 ` [PATCH v2 3/7] drm/msm/mdss: export UBWC data Dmitry Baryshkov
2023-07-28 21:33 ` [PATCH v2 4/7] drm/msm/mdss: populate missing data Dmitry Baryshkov
2023-08-02 1:20 ` Abhinav Kumar
2023-07-28 21:33 ` [PATCH v2 5/7] drm/msm/dpu: use MDSS data for programming SSPP Dmitry Baryshkov
2023-07-28 21:36 ` Abhinav Kumar
2023-07-28 21:39 ` Dmitry Baryshkov
2023-07-28 22:03 ` Abhinav Kumar
2023-07-28 21:33 ` [PATCH v2 6/7] drm/msm/dpu: drop UBWC configuration Dmitry Baryshkov
2023-07-28 21:33 ` [PATCH v2 7/7] drm/msm/dpu: drop BWC features from DPU_MDP_foo namespace Dmitry Baryshkov
2023-07-29 23:45 ` Abhinav Kumar
2023-08-02 9:55 ` [PATCH v2 0/7] drm/msm/dpu: use UBWC data from MDSS driver 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=20230728213320.97309-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=marijn.suijten@somainline.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