All of lore.kernel.org
 help / color / mirror / Atom feed
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 v2 3/6] drm/vkms: change vkms driver to use drm_writeback_connector.base pointer
Date: Wed,  2 Feb 2022 13:46:59 +0530	[thread overview]
Message-ID: <20220202081702.22119-3-suraj.kandpal@intel.com> (raw)
In-Reply-To: <20220202081702.22119-1-suraj.kandpal@intel.com>

Changing vkms driver to accomadate the change of
drm_writeback_connector.base to a pointer the reason for which is
explained in the Patch(drm: add writeback pointers to drm_connector).

Signed-off-by: Kandpal Suraj <suraj.kandpal@intel.com>
---
 drivers/gpu/drm/vkms/vkms_writeback.c | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/drivers/gpu/drm/vkms/vkms_writeback.c b/drivers/gpu/drm/vkms/vkms_writeback.c
index 8694227f555f..374431471f49 100644
--- a/drivers/gpu/drm/vkms/vkms_writeback.c
+++ b/drivers/gpu/drm/vkms/vkms_writeback.c
@@ -114,7 +114,7 @@ static void vkms_wb_atomic_commit(struct drm_connector *conn,
 	struct vkms_device *vkmsdev = drm_device_to_vkms_device(conn->dev);
 	struct vkms_output *output = &vkmsdev->output;
 	struct drm_writeback_connector *wb_conn = &output->wb_connector;
-	struct drm_connector_state *conn_state = wb_conn->base.state;
+	struct drm_connector_state *conn_state = wb_conn->base->state;
 	struct vkms_crtc_state *crtc_state = output->composer_state;
 
 	if (!conn_state)
@@ -139,9 +139,12 @@ static const struct drm_connector_helper_funcs vkms_wb_conn_helper_funcs = {
 int vkms_enable_writeback_connector(struct vkms_device *vkmsdev)
 {
 	struct drm_writeback_connector *wb = &vkmsdev->output.wb_connector;
+	struct vkms_output *output = &vkmsdev->output;
 
-	vkmsdev->output.wb_connector.encoder.possible_crtcs = 1;
-	drm_connector_helper_add(&wb->base, &vkms_wb_conn_helper_funcs);
+	wb->base = &output->connector;
+	wb->encoder = &output->encoder;
+	output->wb_connector.encoder->possible_crtcs = 1;
+	drm_connector_helper_add(wb->base, &vkms_wb_conn_helper_funcs);
 
 	return drm_writeback_connector_init(&vkmsdev->drm, wb,
 					    &vkms_wb_connector_funcs,
-- 
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 v2 3/6] drm/vkms: change vkms driver to use drm_writeback_connector.base pointer
Date: Wed,  2 Feb 2022 13:46:59 +0530	[thread overview]
Message-ID: <20220202081702.22119-3-suraj.kandpal@intel.com> (raw)
In-Reply-To: <20220202081702.22119-1-suraj.kandpal@intel.com>

Changing vkms driver to accomadate the change of
drm_writeback_connector.base to a pointer the reason for which is
explained in the Patch(drm: add writeback pointers to drm_connector).

Signed-off-by: Kandpal Suraj <suraj.kandpal@intel.com>
---
 drivers/gpu/drm/vkms/vkms_writeback.c | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/drivers/gpu/drm/vkms/vkms_writeback.c b/drivers/gpu/drm/vkms/vkms_writeback.c
index 8694227f555f..374431471f49 100644
--- a/drivers/gpu/drm/vkms/vkms_writeback.c
+++ b/drivers/gpu/drm/vkms/vkms_writeback.c
@@ -114,7 +114,7 @@ static void vkms_wb_atomic_commit(struct drm_connector *conn,
 	struct vkms_device *vkmsdev = drm_device_to_vkms_device(conn->dev);
 	struct vkms_output *output = &vkmsdev->output;
 	struct drm_writeback_connector *wb_conn = &output->wb_connector;
-	struct drm_connector_state *conn_state = wb_conn->base.state;
+	struct drm_connector_state *conn_state = wb_conn->base->state;
 	struct vkms_crtc_state *crtc_state = output->composer_state;
 
 	if (!conn_state)
@@ -139,9 +139,12 @@ static const struct drm_connector_helper_funcs vkms_wb_conn_helper_funcs = {
 int vkms_enable_writeback_connector(struct vkms_device *vkmsdev)
 {
 	struct drm_writeback_connector *wb = &vkmsdev->output.wb_connector;
+	struct vkms_output *output = &vkmsdev->output;
 
-	vkmsdev->output.wb_connector.encoder.possible_crtcs = 1;
-	drm_connector_helper_add(&wb->base, &vkms_wb_conn_helper_funcs);
+	wb->base = &output->connector;
+	wb->encoder = &output->encoder;
+	output->wb_connector.encoder->possible_crtcs = 1;
+	drm_connector_helper_add(wb->base, &vkms_wb_conn_helper_funcs);
 
 	return drm_writeback_connector_init(&vkmsdev->drm, wb,
 					    &vkms_wb_connector_funcs,
-- 
2.17.1


  parent reply	other threads:[~2022-02-02  8:08 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 10:17 [PATCH 1/3] drm: add writeback pointers to drm_connector Kandpal, Suraj
2022-01-11 10:17 ` [Intel-gfx] " Kandpal, Suraj
2022-01-11 10:18 ` [PATCH 2/3] drm/arm/komeda : change driver to use drm_writeback_connector.base pointer Kandpal, Suraj
2022-01-11 10:18   ` [Intel-gfx] " Kandpal, Suraj
2022-01-24 17:27   ` Carsten Haitzler
2022-01-24 17:27     ` [Intel-gfx] " Carsten Haitzler
2022-01-11 10:18 ` [PATCH 3/3] drm/vkms: change vkms " Kandpal, Suraj
2022-01-11 10:18   ` [Intel-gfx] " Kandpal, Suraj
2022-01-31  4:14   ` Kandpal, Suraj
2022-01-31  4:14     ` [Intel-gfx] " Kandpal, Suraj
2022-01-11 15:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/3] drm: add writeback pointers to drm_connector Patchwork
2022-01-11 15:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-11 20:42 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-01-21 18:25 ` [Intel-gfx] [PATCH 1/3] " Abhinav Kumar
2022-01-21 18:25   ` Abhinav Kumar
2022-01-27  9:33   ` Kandpal, Suraj
2022-01-27  9:33     ` [Intel-gfx] " Kandpal, Suraj
2022-01-27 18:17     ` Abhinav Kumar
2022-01-27 18:17       ` [Intel-gfx] " Abhinav Kumar
2022-02-01  1:42       ` Abhinav Kumar
2022-02-01  1:42         ` [Intel-gfx] " Abhinav Kumar
2022-02-01  5:23         ` Kandpal, Suraj
2022-02-01  5:23           ` [Intel-gfx] " Kandpal, Suraj
2022-02-02  8:16 ` [PATCH v2 1/6] " Kandpal Suraj
2022-02-02  8:16   ` [Intel-gfx] " Kandpal Suraj
2022-02-02  8:16   ` [PATCH v2 2/6] drm/arm/komeda : change driver to use drm_writeback_connector.base pointer Kandpal Suraj
2022-02-02  8:16     ` [Intel-gfx] " Kandpal Suraj
2022-02-02  8:16   ` Kandpal Suraj [this message]
2022-02-02  8:16     ` [Intel-gfx] [PATCH v2 3/6] drm/vkms: change vkms " Kandpal Suraj
2022-02-02  8:17   ` [PATCH v2 4/6] drm/vc4: vc4 driver changes to accommodate changes done in drm_writeback_connector structure Kandpal Suraj
2022-02-02  8:17     ` [Intel-gfx] " Kandpal Suraj
2022-02-02  8:17   ` [PATCH v2 5/6] drm/rcar_du: changes to rcar-du driver resulting from drm_writeback_connector structure changes Kandpal Suraj
2022-02-02  8:17     ` [Intel-gfx] " Kandpal Suraj
2022-02-02  8:17   ` [PATCH v2 6/6] drm/arm: changes to malidp " Kandpal Suraj
2022-02-02  8:17     ` [Intel-gfx] " Kandpal Suraj

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=20220202081702.22119-3-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.