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 <abhinavk@codeaurora.org>
Cc: Jonathan Marek <jonathan@marek.ca>,
Stephen Boyd <sboyd@kernel.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 v3 0/3] drm/msm/dpu: simplify dpu_hw_blk handling
Date: Sat, 15 May 2021 22:09:05 +0300 [thread overview]
Message-ID: <20210515190909.1809050-1-dmitry.baryshkov@linaro.org> (raw)
Drop most of "extra" features of dpu_hw_blk.
Changes since v2:
- Include a patch to fix compilation issue with merge3d id handling
Changes since v1:
- Make dpu_hw_blk an empty structure
- Split this into separate patchset
----------------------------------------------------------------
Dmitry Baryshkov (4):
drm/msm/dpu: remove unused dpu_hw_blk features
drm/msm/dpu: drop dpu_hw_blk_destroy function
drm/msm/dpu: use struct dpu_hw_merge_3d in dpu_hw_pingpong
drm/msm/dpu: hw_blk: make dpu_hw_blk empty opaque structure
drivers/gpu/drm/msm/Makefile | 1 -
.../gpu/drm/msm/disp/dpu1/dpu_encoder_phys_vid.c | 11 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_blk.c | 139 ---------------------
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_blk.h | 22 +---
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_ctl.c | 6 -
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_dspp.c | 7 --
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_intf.c | 6 -
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_lm.c | 6 -
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_merge3d.c | 6 -
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_pingpong.c | 6 -
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_pingpong.h | 4 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c | 6 -
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_top.c | 6 -
drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c | 4 +-
14 files changed, 10 insertions(+), 220 deletions(-)
delete mode 100644 drivers/gpu/drm/msm/disp/dpu1/dpu_hw_blk.c
next reply other threads:[~2021-05-15 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 19:09 Dmitry Baryshkov [this message]
2021-05-15 19:09 ` [PATCH v3 1/4] drm/msm/dpu: remove unused dpu_hw_blk features Dmitry Baryshkov
2021-06-04 21:08 ` [Freedreno] " abhinavk
2021-05-15 19:09 ` [PATCH v3 2/4] drm/msm/dpu: drop dpu_hw_blk_destroy function Dmitry Baryshkov
2021-06-04 21:08 ` [Freedreno] " abhinavk
2021-05-15 19:09 ` [PATCH v3 3/4] drm/msm/dpu: use struct dpu_hw_merge_3d in dpu_hw_pingpong Dmitry Baryshkov
2021-06-04 21:09 ` [Freedreno] " abhinavk
2021-05-15 19:09 ` [PATCH v3 4/4] drm/msm/dpu: hw_blk: make dpu_hw_blk empty opaque structure Dmitry Baryshkov
2021-06-04 21:15 ` [Freedreno] " abhinavk
2021-06-02 21:43 ` [PATCH v3 0/3] drm/msm/dpu: simplify dpu_hw_blk handling 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=20210515190909.1809050-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=abhinavk@codeaurora.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=jonathan@marek.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sboyd@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).