From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
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@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org
Subject: [PATCH v2 0/4] drm/msm: rework MDSS drivers
Date: Thu, 20 Jan 2022 01:40:01 +0300 [thread overview]
Message-ID: <20220119224005.3104578-1-dmitry.baryshkov@linaro.org> (raw)
These patches coninue work started by AngeloGioacchino Del Regno in the
previous cycle by further decoupling and dissecting MDSS and MDP drivers
probe/binding paths.
This removes code duplication between MDP5 and DPU1 MDSS drivers, by
merging them and moving to the top level.
This patchset depends on the patches 1 and 2 from [1]
Changes since v1:
- Rebased on top of [2] and [1]
[1] https://patchwork.freedesktop.org/series/99066/
[2] https://patchwork.freedesktop.org/series/98521/
Dmitry Baryshkov (4):
drm/msm: unify MDSS drivers
drm/msm: remove extra indirection for msm_mdss
drm/msm: split the main platform driver
drm/msm: stop using device's match data pointer
drivers/gpu/drm/msm/Makefile | 3 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 10 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c | 260 -------------
drivers/gpu/drm/msm/disp/mdp4/mdp4_kms.c | 68 +++-
drivers/gpu/drm/msm/disp/mdp5/mdp5_kms.c | 11 +-
drivers/gpu/drm/msm/disp/mdp5/mdp5_mdss.c | 252 -------------
drivers/gpu/drm/msm/msm_drv.c | 260 +++----------
drivers/gpu/drm/msm/msm_drv.h | 16 +
drivers/gpu/drm/msm/msm_kms.h | 18 -
drivers/gpu/drm/msm/msm_mdss.c | 438 ++++++++++++++++++++++
10 files changed, 578 insertions(+), 758 deletions(-)
delete mode 100644 drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
delete mode 100644 drivers/gpu/drm/msm/disp/mdp5/mdp5_mdss.c
create mode 100644 drivers/gpu/drm/msm/msm_mdss.c
base-commit: 6ed95285382d6f90a3c3a11d5806a5eb7db715c3
prerequisite-patch-id: b5572c353efa8ebefb32fc70e54bc537f78ff2bd
prerequisite-patch-id: 40a854aee69b6ddf5b1c33cac3647efae3e3ebf1
prerequisite-patch-id: 8b687a19047983e26262a1bb2feda8a9fd5bc97f
prerequisite-patch-id: e2d7f768b4b287c80797635f3ed5b6353b12adb5
prerequisite-patch-id: cac9fb235e3510b5bcb713f602658e6233cd308b
--
2.34.1
next reply other threads:[~2022-01-19 22:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 22:40 Dmitry Baryshkov [this message]
2022-01-19 22:40 ` [PATCH v2 1/4] drm/msm: unify MDSS drivers Dmitry Baryshkov
2022-03-03 22:50 ` Stephen Boyd
2022-01-19 22:40 ` [PATCH v2 2/4] drm/msm: remove extra indirection for msm_mdss Dmitry Baryshkov
2022-03-03 22:54 ` Stephen Boyd
2022-03-03 23:44 ` Dmitry Baryshkov
2022-01-19 22:40 ` [PATCH v2 3/4] drm/msm: split the main platform driver Dmitry Baryshkov
2022-03-03 23:00 ` Stephen Boyd
2022-03-03 23:46 ` Dmitry Baryshkov
2022-01-19 22:40 ` [PATCH v2 4/4] drm/msm: stop using device's match data pointer Dmitry Baryshkov
2022-03-03 23:04 ` Stephen Boyd
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=20220119224005.3104578-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.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;
as well as URLs for NNTP newsgroup(s).