From: Suraj Kandpal <suraj.kandpal@intel.com>
To: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Cc: dmitry.baryshkov@oss.qualcomm.com, John.Harrison@Igalia.com,
kernel-dev@igalia.com, alex.hung@amd.com, liviu.dudau@arm.com,
louis.chauvet@bootlin.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch, laurent.pinchart+renesas@ideasonboard.com,
tomi.valkeinen+renesas@ideasonboard.com,
kieran.bingham+renesas@ideasonboard.com,
dave.stevenson@raspberrypi.com, mcanal@igalia.com,
kernel-list@raspberrypi.com, uma.shankar@intel.com,
arun.r.murthy@intel.com, Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH v7 0/8] Refactor drm_writeback_connector structure
Date: Tue, 10 Nov 2026 11:46:29 +0530 [thread overview]
Message-ID: <20261110061637.2500929-1-suraj.kandpal@intel.com> (raw)
Some drivers cannot work with the current design where the connector
is embedded within the drm_writeback_connector such as intel and
some drivers that can get it working end up adding a lot of checks
all around the code to check if it's a writeback conenctor or not.
This is due to the inheritance limitation in C.
This series intends to solve it by moving the drm_writeback_connector
within the drm_connector and remove the drm_connector base which was in
drm_writeback_connector. This is done in union with hdmi connector
within drm_connector to save memory and since drm_connector cannot be
both hdmi and writeback it serves is well.
A RFC version was floated and discussion had taken place at [1] which
kicked of this more cleaner series.
We do all other required modifications that come with these changes
along with addition of new function which returns the drm_connector when
drm_writeback_connector is present.
This series also contains some writeback API cleanups as a consequence
of writeback connector moving into drm_connector
All drivers will be expected to allocate the drm_connector.
This discussion was tiggered from [2] and sits on top of Dmitry's series
see [3].
[1] https://patchwork.freedesktop.org/series/152758/
[2] https://patchwork.freedesktop.org/series/152106/
[3] https://patchwork.freedesktop.org/series/152420/
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Dmitry Baryshkov (1):
drm: writeback: drop excess connector initialization functions
Suraj Kandpal (7):
drm: writeback: Refactor drm_writeback_connector structure
drm: writeback: Modify writeback init helpers
drm: writeback: Modify drm_writeback_queue_job helper
drm: writeback: Modify drm_writeback_signal_completion helper
drm: writeback: Modify drm_writeback_get_out_fence helper
drm: writeback: Modify prepare_writeback_job helper
drm: writeback: Modify cleanup_writeback_job helper
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 8 +-
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h | 3 +-
.../display/amdgpu_dm/amdgpu_dm_connector.c | 4 +-
.../drm/amd/display/amdgpu_dm/amdgpu_dm_wb.c | 37 ++--
.../drm/amd/display/amdgpu_dm/amdgpu_dm_wb.h | 4 +-
.../tests/amdgpu_dm_connector_test.c | 6 +-
.../display/amdgpu_dm/tests/amdgpu_dm_test.c | 2 +-
.../amdgpu_dm/tests/amdgpu_dm_wb_test.c | 10 +-
.../gpu/drm/arm/display/komeda/komeda_crtc.c | 2 +-
.../gpu/drm/arm/display/komeda/komeda_kms.h | 9 +-
.../arm/display/komeda/komeda_wb_connector.c | 37 ++--
drivers/gpu/drm/arm/malidp_crtc.c | 2 +-
drivers/gpu/drm/arm/malidp_drv.h | 3 +-
drivers/gpu/drm/arm/malidp_mw.c | 32 ++-
drivers/gpu/drm/drm_atomic_uapi.c | 4 +-
drivers/gpu/drm/drm_connector.c | 3 +
drivers/gpu/drm/drm_crtc_internal.h | 3 +
drivers/gpu/drm/drm_writeback.c | 193 ++++++------------
.../drm/msm/disp/dpu1/dpu_encoder_phys_wb.c | 9 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_writeback.c | 10 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_writeback.h | 4 +-
.../gpu/drm/renesas/rcar-du/rcar_du_crtc.h | 8 +-
.../drm/renesas/rcar-du/rcar_du_writeback.c | 44 ++--
drivers/gpu/drm/vc4/vc4_txp.c | 16 +-
drivers/gpu/drm/vkms/vkms_drv.h | 2 +-
drivers/gpu/drm/vkms/vkms_writeback.c | 15 +-
include/drm/drm_connector.h | 69 ++++++-
include/drm/drm_modeset_helper_vtables.h | 4 +-
include/drm/drm_writeback.h | 98 +--------
29 files changed, 307 insertions(+), 334 deletions(-)
--
2.34.1
next reply other threads:[~2026-11-10 6:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 6:16 Suraj Kandpal [this message]
2026-11-10 6:16 ` [PATCH v7 DO NOT REVIEW 1/8] drm: writeback: drop excess connector initialization functions Suraj Kandpal
2026-11-10 6:16 ` [PATCH v7 2/8] drm: writeback: Refactor drm_writeback_connector structure Suraj Kandpal
2026-11-10 6:16 ` [PATCH v7 3/8] drm: writeback: Modify writeback init helpers Suraj Kandpal
2026-11-10 6:16 ` [PATCH v7 4/8] drm: writeback: Modify drm_writeback_queue_job helper Suraj Kandpal
2026-11-10 6:16 ` [PATCH v7 5/8] drm: writeback: Modify drm_writeback_signal_completion helper Suraj Kandpal
2026-11-10 6:16 ` [PATCH v7 6/8] drm: writeback: Modify drm_writeback_get_out_fence helper Suraj Kandpal
2026-11-10 6:16 ` [PATCH v7 7/8] drm: writeback: Modify prepare_writeback_job helper Suraj Kandpal
2026-11-10 6:16 ` [PATCH v7 8/8] drm: writeback: Modify cleanup_writeback_job helper Suraj Kandpal
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=20261110061637.2500929-1-suraj.kandpal@intel.com \
--to=suraj.kandpal@intel.com \
--cc=John.Harrison@Igalia.com \
--cc=airlied@gmail.com \
--cc=alex.hung@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arun.r.murthy@intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=kernel-dev@igalia.com \
--cc=kernel-list@raspberrypi.com \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=louis.chauvet@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcanal@igalia.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tomi.valkeinen+renesas@ideasonboard.com \
--cc=tzimmermann@suse.de \
--cc=uma.shankar@intel.com \
/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®