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 v5 0/6] drm/msm/dpu: simplify RM code
Date: Sat, 22 Jan 2022 00:06:12 +0300 [thread overview]
Message-ID: <20220121210618.3482550-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 v4:
- Changes IS_ERR_OR_NULL() to IS_ERR() in dpu_rm_init()
- Removed if(!null) conditions when calling dpu_hw_intf_destroy() and
dpu_hw_vbif_destroy()
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.
Dmitry Baryshkov (6):
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: fix error handling in dpu_rm_init
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 ---
.../gpu/drm/msm/disp/dpu1/dpu_encoder_phys.h | 5 -
.../drm/msm/disp/dpu1/dpu_encoder_phys_cmd.c | 8 --
.../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 | 126 +++++-------------
drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h | 31 ++++-
drivers/gpu/drm/msm/disp/dpu1/dpu_vbif.c | 26 +---
12 files changed, 73 insertions(+), 225 deletions(-)
--
2.34.1
next reply other threads:[~2022-01-21 21:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 21:06 Dmitry Baryshkov [this message]
2022-01-21 21:06 ` [PATCH v5 1/6] drm/msm/dpu: drop unused lm_max_width from RM Dmitry Baryshkov
2022-02-10 0:08 ` [Freedreno] " Abhinav Kumar
2022-01-21 21:06 ` [PATCH v5 2/6] drm/msm/dpu: add DSPP blocks teardown Dmitry Baryshkov
2022-02-10 0:09 ` Abhinav Kumar
2022-01-21 21:06 ` [PATCH v5 3/6] drm/msm/dpu: get INTF blocks directly rather than through RM Dmitry Baryshkov
2022-02-10 0:25 ` Abhinav Kumar
2022-02-10 9:32 ` Dmitry Baryshkov
2022-02-10 23:31 ` [Freedreno] " Abhinav Kumar
2022-02-11 13:47 ` Dmitry Baryshkov
2022-02-12 1:08 ` Abhinav Kumar
2022-01-21 21:06 ` [PATCH v5 4/6] drm/msm/dpu: stop embedding dpu_hw_blk into dpu_hw_intf Dmitry Baryshkov
2022-02-14 19:08 ` Abhinav Kumar
2022-01-21 21:06 ` [PATCH v5 5/6] drm/msm/dpu: fix error handling in dpu_rm_init Dmitry Baryshkov
2022-02-14 19:15 ` Abhinav Kumar
2022-02-14 20:43 ` Dmitry Baryshkov
2022-02-14 21:25 ` Abhinav Kumar
2022-01-21 21:06 ` [PATCH v5 6/6] drm/msm/dpu: move VBIF blocks handling to dpu_rm Dmitry Baryshkov
2022-02-14 19:53 ` Abhinav Kumar
2022-02-14 20:56 ` Dmitry Baryshkov
2022-02-14 22:04 ` [Freedreno] " Abhinav Kumar
2022-02-14 22:39 ` Dmitry Baryshkov
2022-02-14 23:22 ` Abhinav Kumar
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=20220121210618.3482550-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).