From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: Rob Clark <robin.clark@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Jessica Zhang <jesszhan0024@gmail.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: [PATCH 0/7] drm/msm/dpu: simplify VBIF handling
Date: Fri, 27 Feb 2026 20:36:39 +0200 [thread overview]
Message-ID: <20260227-drop-vbif-nrt-v1-0-2b97d0438182@oss.qualcomm.com> (raw)
Once Konrad asked, what is the use for VBIF_NRT. Answering to his
question revealed that it's not actually used by the DPU driver.
There are two VBIF interfaces two memory, VBIF_RT and VBIF_NRT with
VBIF_NRT being used only for the offscreen rotator, a separate block
performing writeback operation with the optional 90 degree rotation.
This block will require a separate isntance of the DPU driver, and it is
not supported at this point.
The only exception to that rule is MSM8996, where VBIF_NRT has also been
used for outputting all writeback data. The DPU driver don't support WB
on that platform and most likely will not in the close feature.
The missing features don't match the extra complexity required to
support two VBIF interfaces, so drop the second one and all the options
to support it.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
---
Dmitry Baryshkov (7):
drm/msm/dpu: drop VBIF_NRT handling
drm/msm/dpu: stop declaring VBIFs as an array in catalog
drm/msm/dpu: replace VBIF-related array with bare pointers
drm/msm/dpu: drop VBIF id, base and name from the catalog
drm/msm/dpu: drop vbif_idx from WB configuration
drm/msm/dpu: drop VBIF index from the VBIF params
drm/msm/dpu: drop VBIF index from the struct dpu_hw_vbif
.../drm/msm/disp/dpu1/catalog/dpu_10_0_sm8650.h | 4 +-
.../drm/msm/disp/dpu1/catalog/dpu_12_0_sm8750.h | 4 +-
.../drm/msm/disp/dpu1/catalog/dpu_12_2_glymur.h | 4 +-
.../drm/msm/disp/dpu1/catalog/dpu_13_0_kaanapali.h | 4 +-
.../drm/msm/disp/dpu1/catalog/dpu_1_14_msm8937.h | 3 +-
.../drm/msm/disp/dpu1/catalog/dpu_1_15_msm8917.h | 3 +-
.../drm/msm/disp/dpu1/catalog/dpu_1_16_msm8953.h | 3 +-
.../drm/msm/disp/dpu1/catalog/dpu_1_7_msm8996.h | 3 +-
.../drm/msm/disp/dpu1/catalog/dpu_3_0_msm8998.h | 3 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_3_2_sdm660.h | 3 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_3_3_sdm630.h | 3 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_4_0_sdm845.h | 3 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_4_1_sdm670.h | 3 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_5_0_sm8150.h | 4 +-
.../drm/msm/disp/dpu1/catalog/dpu_5_1_sc8180x.h | 4 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_5_2_sm7150.h | 4 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_5_3_sm6150.h | 4 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_5_4_sm6125.h | 4 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_6_0_sm8250.h | 4 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_6_2_sc7180.h | 4 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_6_3_sm6115.h | 3 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_6_4_sm6350.h | 4 +-
.../drm/msm/disp/dpu1/catalog/dpu_6_5_qcm2290.h | 3 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_6_9_sm6375.h | 3 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_7_0_sm8350.h | 4 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_7_2_sc7280.h | 4 +-
.../drm/msm/disp/dpu1/catalog/dpu_8_0_sc8280xp.h | 3 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_8_1_sm8450.h | 4 +-
.../drm/msm/disp/dpu1/catalog/dpu_8_4_sa8775p.h | 4 +-
.../gpu/drm/msm/disp/dpu1/catalog/dpu_9_0_sm8550.h | 4 +-
.../drm/msm/disp/dpu1/catalog/dpu_9_1_sar2130p.h | 4 +-
.../drm/msm/disp/dpu1/catalog/dpu_9_2_x1e80100.h | 4 +-
.../gpu/drm/msm/disp/dpu1/dpu_encoder_phys_wb.c | 7 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c | 35 ++---
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h | 8 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_mdss.h | 6 -
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_vbif.c | 3 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_vbif.h | 1 -
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 70 +++------
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 4 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c | 5 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_trace.h | 19 +--
drivers/gpu/drm/msm/disp/dpu1/dpu_vbif.c | 163 ++++++++-------------
drivers/gpu/drm/msm/disp/dpu1/dpu_vbif.h | 4 -
44 files changed, 144 insertions(+), 296 deletions(-)
---
base-commit: 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f
change-id: 20260219-drop-vbif-nrt-cb7da190f6f4
Best regards,
--
With best wishes
Dmitry
next reply other threads:[~2026-02-27 18:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 18:36 Dmitry Baryshkov [this message]
2026-02-27 18:36 ` [PATCH 1/7] drm/msm/dpu: drop VBIF_NRT handling Dmitry Baryshkov
2026-03-02 12:37 ` Konrad Dybcio
2026-02-27 18:36 ` [PATCH 2/7] drm/msm/dpu: stop declaring VBIFs as an array in catalog Dmitry Baryshkov
2026-03-02 12:38 ` Konrad Dybcio
2026-02-27 18:36 ` [PATCH 3/7] drm/msm/dpu: replace VBIF-related array with bare pointers Dmitry Baryshkov
2026-03-02 12:40 ` Konrad Dybcio
2026-02-27 18:36 ` [PATCH 4/7] drm/msm/dpu: drop VBIF id, base and name from the catalog Dmitry Baryshkov
2026-03-02 12:41 ` Konrad Dybcio
2026-02-27 18:36 ` [PATCH 5/7] drm/msm/dpu: drop vbif_idx from WB configuration Dmitry Baryshkov
2026-03-02 12:42 ` Konrad Dybcio
2026-02-27 18:36 ` [PATCH 6/7] drm/msm/dpu: drop VBIF index from the VBIF params Dmitry Baryshkov
2026-03-02 12:43 ` Konrad Dybcio
2026-02-27 18:36 ` [PATCH 7/7] drm/msm/dpu: drop VBIF index from the struct dpu_hw_vbif Dmitry Baryshkov
2026-03-02 12:44 ` Konrad Dybcio
2026-03-02 11:58 ` [PATCH 0/7] drm/msm/dpu: simplify VBIF handling Konrad Dybcio
2026-03-02 12:33 ` Dmitry Baryshkov
2026-03-02 12:37 ` Konrad Dybcio
2026-03-02 12:45 ` Konrad Dybcio
2026-03-02 12:52 ` Dmitry Baryshkov
2026-03-27 19:47 ` 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=20260227-drop-vbif-nrt-v1-0-2b97d0438182@oss.qualcomm.com \
--to=dmitry.baryshkov@oss.qualcomm.com \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
/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
all inboxes | Powered by JetHome®