From: Kandpal Suraj <suraj.kandpal@intel.com>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: Kandpal Suraj <suraj.kandpal@intel.com>,
carsten.haitzler@arm.com, jani.nikula@intel.com,
quic_abhinavk@quicinc.com, laurent.pinchart@ideasonboard.com,
dmitry.baryshkov@linaro.org, arun.r.murthy@intel.com
Subject: [PATCH 0/6] drm writeback connector changes
Date: Wed, 2 Feb 2022 14:24:23 +0530 [thread overview]
Message-ID: <20220202085429.22261-1-suraj.kandpal@intel.com> (raw)
This patch series contains drm_writeback_connector structure change i.e
change of drm_connector and drm_encoder fields to a pointer the reason
for which is explained in patch(1/6) drm: add writeback pointers to
drm_connector and the accompanying changes to the different drivers that
were effected by it.
I had perviously floated a patch series but missed some of the drivers
that were effected by the change hence refloating the patch series
Kandpal Suraj (6):
drm: add writeback pointers to drm_connector
drm/arm/komeda : change driver to use drm_writeback_connector.base
pointer
drm/vkms: change vkms driver to use drm_writeback_connector.base
pointer
drm/vc4: vc4 driver changes to accommodate changes done in
drm_writeback_connector structure
drm/rcar_du: changes to rcar-du driver resulting from
drm_writeback_connector structure changes
drm/arm: changes to malidp driver resulting from
drm_writeback_connector structure changes
.../gpu/drm/arm/display/komeda/komeda_crtc.c | 2 +-
.../gpu/drm/arm/display/komeda/komeda_kms.h | 3 ++-
.../arm/display/komeda/komeda_wb_connector.c | 11 +++++-----
drivers/gpu/drm/arm/malidp_crtc.c | 2 +-
drivers/gpu/drm/arm/malidp_drv.h | 2 ++
drivers/gpu/drm/arm/malidp_mw.c | 12 +++++++----
drivers/gpu/drm/drm_writeback.c | 19 +++++++++---------
drivers/gpu/drm/rcar-du/rcar_du_crtc.h | 2 ++
drivers/gpu/drm/rcar-du/rcar_du_writeback.c | 8 +++++---
drivers/gpu/drm/vc4/vc4_txp.c | 20 +++++++++++++------
drivers/gpu/drm/vkms/vkms_writeback.c | 9 ++++++---
include/drm/drm_connector.h | 3 +++
include/drm/drm_writeback.h | 6 +++---
13 files changed, 63 insertions(+), 36 deletions(-)
--
2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Kandpal Suraj <suraj.kandpal@intel.com>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: carsten.haitzler@arm.com, jani.nikula@intel.com,
quic_abhinavk@quicinc.com, laurent.pinchart@ideasonboard.com,
dmitry.baryshkov@linaro.org
Subject: [Intel-gfx] [PATCH 0/6] drm writeback connector changes
Date: Wed, 2 Feb 2022 14:24:23 +0530 [thread overview]
Message-ID: <20220202085429.22261-1-suraj.kandpal@intel.com> (raw)
This patch series contains drm_writeback_connector structure change i.e
change of drm_connector and drm_encoder fields to a pointer the reason
for which is explained in patch(1/6) drm: add writeback pointers to
drm_connector and the accompanying changes to the different drivers that
were effected by it.
I had perviously floated a patch series but missed some of the drivers
that were effected by the change hence refloating the patch series
Kandpal Suraj (6):
drm: add writeback pointers to drm_connector
drm/arm/komeda : change driver to use drm_writeback_connector.base
pointer
drm/vkms: change vkms driver to use drm_writeback_connector.base
pointer
drm/vc4: vc4 driver changes to accommodate changes done in
drm_writeback_connector structure
drm/rcar_du: changes to rcar-du driver resulting from
drm_writeback_connector structure changes
drm/arm: changes to malidp driver resulting from
drm_writeback_connector structure changes
.../gpu/drm/arm/display/komeda/komeda_crtc.c | 2 +-
.../gpu/drm/arm/display/komeda/komeda_kms.h | 3 ++-
.../arm/display/komeda/komeda_wb_connector.c | 11 +++++-----
drivers/gpu/drm/arm/malidp_crtc.c | 2 +-
drivers/gpu/drm/arm/malidp_drv.h | 2 ++
drivers/gpu/drm/arm/malidp_mw.c | 12 +++++++----
drivers/gpu/drm/drm_writeback.c | 19 +++++++++---------
drivers/gpu/drm/rcar-du/rcar_du_crtc.h | 2 ++
drivers/gpu/drm/rcar-du/rcar_du_writeback.c | 8 +++++---
drivers/gpu/drm/vc4/vc4_txp.c | 20 +++++++++++++------
drivers/gpu/drm/vkms/vkms_writeback.c | 9 ++++++---
include/drm/drm_connector.h | 3 +++
include/drm/drm_writeback.h | 6 +++---
13 files changed, 63 insertions(+), 36 deletions(-)
--
2.17.1
next reply other threads:[~2022-02-02 8:46 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 8:54 Kandpal Suraj [this message]
2022-02-02 8:54 ` [Intel-gfx] [PATCH 0/6] drm writeback connector changes Kandpal Suraj
2022-02-02 8:54 ` [PATCH 1/6] drm: add writeback pointers to drm_connector Kandpal Suraj
2022-02-02 8:54 ` [Intel-gfx] " Kandpal Suraj
2022-02-02 10:28 ` Dmitry Baryshkov
2022-02-02 10:28 ` [Intel-gfx] " Dmitry Baryshkov
2022-02-03 8:46 ` Kandpal, Suraj
2022-02-03 8:46 ` [Intel-gfx] " Kandpal, Suraj
2022-02-02 11:17 ` kernel test robot
2022-02-02 11:17 ` kernel test robot
2022-02-02 20:07 ` kernel test robot
2022-02-02 20:07 ` kernel test robot
2022-02-02 20:07 ` kernel test robot
2022-02-02 8:54 ` [PATCH 2/6] drm/arm/komeda : change driver to use drm_writeback_connector.base pointer Kandpal Suraj
2022-02-02 8:54 ` [Intel-gfx] " Kandpal Suraj
2022-02-02 8:54 ` [PATCH 3/6] drm/vkms: change vkms " Kandpal Suraj
2022-02-02 8:54 ` [Intel-gfx] " Kandpal Suraj
2022-02-02 8:54 ` [PATCH 4/6] drm/vc4: vc4 driver changes to accommodate changes done in drm_writeback_connector structure Kandpal Suraj
2022-02-02 8:54 ` [Intel-gfx] " Kandpal Suraj
2022-02-02 8:54 ` [PATCH 5/6] drm/rcar_du: changes to rcar-du driver resulting from drm_writeback_connector structure changes Kandpal Suraj
2022-02-02 8:54 ` [Intel-gfx] " Kandpal Suraj
2022-02-02 12:42 ` Laurent Pinchart
2022-02-02 12:42 ` [Intel-gfx] " Laurent Pinchart
2022-02-02 13:15 ` Jani Nikula
2022-02-02 13:15 ` [Intel-gfx] " Jani Nikula
2022-02-02 13:26 ` Laurent Pinchart
2022-02-02 13:26 ` [Intel-gfx] " Laurent Pinchart
2022-02-02 15:38 ` Jani Nikula
2022-02-02 15:38 ` [Intel-gfx] " Jani Nikula
2022-02-26 18:27 ` Rob Clark
2022-02-26 18:27 ` [Intel-gfx] " Rob Clark
2022-02-28 8:03 ` Laurent Pinchart
2022-02-28 8:03 ` [Intel-gfx] " Laurent Pinchart
2022-02-28 12:09 ` Jani Nikula
2022-02-28 12:09 ` [Intel-gfx] " Jani Nikula
2022-02-28 12:28 ` Laurent Pinchart
2022-02-28 12:28 ` [Intel-gfx] " Laurent Pinchart
2022-02-28 13:42 ` Laurent Pinchart
2022-02-28 13:42 ` [Intel-gfx] " Laurent Pinchart
2022-03-02 18:28 ` Abhinav Kumar
2022-03-02 18:28 ` [Intel-gfx] " Abhinav Kumar
2022-03-02 18:31 ` Laurent Pinchart
2022-03-02 18:31 ` [Intel-gfx] " Laurent Pinchart
2022-03-03 17:32 ` Abhinav Kumar
2022-03-03 17:32 ` [Intel-gfx] " Abhinav Kumar
2022-03-04 9:56 ` Kandpal, Suraj
2022-03-04 9:56 ` [Intel-gfx] " Kandpal, Suraj
2022-03-04 10:39 ` Dmitry Baryshkov
2022-03-04 10:39 ` [Intel-gfx] " Dmitry Baryshkov
2022-03-04 10:47 ` Kandpal, Suraj
2022-03-04 10:47 ` [Intel-gfx] " Kandpal, Suraj
2022-03-04 11:25 ` Dmitry Baryshkov
2022-03-04 11:25 ` [Intel-gfx] " Dmitry Baryshkov
2022-03-04 14:16 ` Kandpal, Suraj
2022-03-04 14:16 ` [Intel-gfx] " Kandpal, Suraj
2022-03-04 20:47 ` Abhinav Kumar
2022-03-04 20:47 ` [Intel-gfx] " Abhinav Kumar
2022-03-08 14:30 ` Kandpal, Suraj
2022-03-08 14:30 ` [Intel-gfx] " Kandpal, Suraj
2022-03-08 19:44 ` Abhinav Kumar
2022-03-08 19:44 ` [Intel-gfx] " Abhinav Kumar
2022-02-06 23:32 ` Dmitry Baryshkov
2022-02-06 23:32 ` [Intel-gfx] " Dmitry Baryshkov
2022-02-07 7:20 ` Abhinav Kumar
2022-02-07 7:20 ` [Intel-gfx] " Abhinav Kumar
2022-02-10 1:40 ` Abhinav Kumar
2022-02-10 1:40 ` [Intel-gfx] " Abhinav Kumar
2022-02-10 4:58 ` Laurent Pinchart
2022-02-10 4:58 ` [Intel-gfx] " Laurent Pinchart
2022-02-22 3:32 ` Dmitry Baryshkov
2022-02-22 3:32 ` [Intel-gfx] " Dmitry Baryshkov
2022-02-22 7:34 ` Laurent Pinchart
2022-02-22 7:34 ` [Intel-gfx] " Laurent Pinchart
2022-02-24 0:27 ` Abhinav Kumar
2022-02-24 0:27 ` [Intel-gfx] " Abhinav Kumar
2022-02-02 13:34 ` Ville Syrjälä
2022-02-02 13:34 ` [Intel-gfx] " Ville Syrjälä
2022-02-02 13:40 ` Dmitry Baryshkov
2022-02-02 13:40 ` [Intel-gfx] " Dmitry Baryshkov
2022-02-02 15:57 ` Jani Nikula
2022-02-02 15:57 ` [Intel-gfx] " Jani Nikula
2022-02-23 6:17 ` Kandpal, Suraj
2022-02-23 6:17 ` [Intel-gfx] " Kandpal, Suraj
2022-02-25 23:26 ` Abhinav Kumar
2022-02-25 23:26 ` [Intel-gfx] " Abhinav Kumar
2022-02-26 5:10 ` Kandpal, Suraj
2022-02-26 5:10 ` [Intel-gfx] " Kandpal, Suraj
2022-02-28 8:00 ` Laurent Pinchart
2022-02-28 8:00 ` [Intel-gfx] " Laurent Pinchart
2022-02-28 8:07 ` Dmitry Baryshkov
2022-02-28 8:07 ` [Intel-gfx] " Dmitry Baryshkov
2022-02-28 8:28 ` Laurent Pinchart
2022-02-28 8:28 ` [Intel-gfx] " Laurent Pinchart
2022-02-02 8:54 ` [PATCH 6/6] drm/arm: changes to malidp " Kandpal Suraj
2022-02-02 8:54 ` [Intel-gfx] " Kandpal Suraj
2022-02-02 10:01 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm writeback connector changes Patchwork
2022-02-02 10:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-02 12:22 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=20220202085429.22261-1-suraj.kandpal@intel.com \
--to=suraj.kandpal@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=carsten.haitzler@arm.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=quic_abhinavk@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.