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: David Airlie <airlied@linux.ie>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
Stephen Boyd <swboyd@chromium.org>,
freedreno@lists.freedesktop.org
Subject: [PATCH v4 0/5] drm/msm/dpu: simplify RM code
Date: Thu, 6 Jan 2022 02:10:26 +0300 [thread overview]
Message-ID: <20220105231031.436020-1-dmitry.baryshkov@linaro.org> (raw)
INTF blocks are not really handled by resource manager, they are
assigned at dpu_encoder_setup_display using dpu_encoder_get_intf().
Then this allocation is passed to RM and then returned to then
dpu_encoder. So allocate them outside of RM and use them directly.
While we are at it, drop the lm_max_width from the RM and simplify VBIF
handling (move creation/destruction to the RM too). Once this and SSPP
handling patches are merged, the RM would handle lifetime of all
dpu_hw_* objects.
Changes since v3:
- Add missing DSPP blocks teardown
- Remove dpu_hw_blk from dpu_hw_intf
- move dpu_hw_vbif creation/destruction to the RM
Changes since v2:
- Dropped DSPP, PP and MERGE_3D patches for now.
Changes since v1:
- Split into separate patch series to ease review.
The following changes since commit 6ed95285382d6f90a3c3a11d5806a5eb7db715c3:
drm/msm/a5xx: Fix missing CP_PROTECT for SMMU on A540 (2021-12-17 15:09:46 -0800)
are available in the Git repository at:
https://git.linaro.org/people/dmitry.baryshkov/kernel.git dpu-rm-clean-4
for you to fetch changes up to 95f32a88ae0dd366700e2ebf98d793b41c53aeeb:
drm/msm/dpu: move VBIF blocks handling to dpu_rm (2021-12-27 03:41:20 +0300)
----------------------------------------------------------------
Dmitry Baryshkov (5):
drm/msm/dpu: drop unused lm_max_width from RM
drm/msm/dpu: add DSPP blocks teardown
drm/msm/dpu: get INTF blocks directly rather than through RM
drm/msm/dpu: stop embedding dpu_hw_blk into dpu_hw_intf
drm/msm/dpu: move VBIF blocks handling to dpu_rm
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 36 +------
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.h | 16 ---
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys.h | 5 -
.../gpu/drm/msm/disp/dpu1/dpu_encoder_phys_cmd.c | 8 --
.../gpu/drm/msm/disp/dpu1/dpu_encoder_phys_vid.c | 8 --
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_intf.h | 11 --
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_vbif.h | 1 +
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 28 +----
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 2 -
drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c | 116 ++++++---------------
drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h | 31 ++++--
drivers/gpu/drm/msm/disp/dpu1/dpu_vbif.c | 26 ++---
12 files changed, 70 insertions(+), 218 deletions(-)
next reply other threads:[~2022-01-05 23:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 23:10 Dmitry Baryshkov [this message]
2022-01-05 23:10 ` [PATCH v4 1/5] drm/msm/dpu: drop unused lm_max_width from RM Dmitry Baryshkov
2022-01-07 0:53 ` Stephen Boyd
2022-01-05 23:10 ` [PATCH v4 2/5] drm/msm/dpu: add DSPP blocks teardown Dmitry Baryshkov
2022-01-07 0:54 ` Stephen Boyd
2022-01-05 23:10 ` [PATCH v4 3/5] drm/msm/dpu: get INTF blocks directly rather than through RM Dmitry Baryshkov
2022-01-07 1:01 ` Stephen Boyd
2022-01-05 23:10 ` [PATCH v4 4/5] drm/msm/dpu: stop embedding dpu_hw_blk into dpu_hw_intf Dmitry Baryshkov
2022-01-07 1:20 ` Stephen Boyd
2022-01-07 1:21 ` Stephen Boyd
2022-01-05 23:10 ` [PATCH v4 5/5] drm/msm/dpu: move VBIF blocks handling to dpu_rm Dmitry Baryshkov
2022-01-07 1:27 ` Stephen Boyd
2022-01-21 21:01 ` 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=20220105231031.436020-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=abhinavk@codeaurora.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--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).