linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Rosin <peda@axentia.se>
To: linux-kernel@vger.kernel.org
Cc: Peter Rosin <peda@axentia.se>,
	Benjamin Gaignard <benjamin.gaignard@linaro.org>,
	Vincent Abriou <vincent.abriou@st.com>,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, Jyri Sarha <jsarha@ti.com>,
	Daniel Vetter <daniel@ffwll.ch>
Subject: [PATCH v3 23/26] drm/sti: provide an owner .odev device for the bridges
Date: Wed, 16 May 2018 12:15:07 +0200	[thread overview]
Message-ID: <20180516101510.13215-24-peda@axentia.se> (raw)
In-Reply-To: <20180516101510.13215-1-peda@axentia.se>

The .of_node member is going away and providing an .odev will become
mandatory.

Signed-off-by: Peter Rosin <peda@axentia.se>
---
 drivers/gpu/drm/sti/sti_dvo.c  | 2 +-
 drivers/gpu/drm/sti/sti_hda.c  | 1 +
 drivers/gpu/drm/sti/sti_hdmi.c | 1 +
 3 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/sti/sti_dvo.c b/drivers/gpu/drm/sti/sti_dvo.c
index a5979cd25cc7..f2609725f8f1 100644
--- a/drivers/gpu/drm/sti/sti_dvo.c
+++ b/drivers/gpu/drm/sti/sti_dvo.c
@@ -460,9 +460,9 @@ static int sti_dvo_bind(struct device *dev, struct device *master, void *data)
 	if (!bridge)
 		return -ENOMEM;
 
+	bridge->odev = &dvo->dev;
 	bridge->driver_private = dvo;
 	bridge->funcs = &sti_dvo_bridge_funcs;
-	bridge->of_node = dvo->dev.of_node;
 	drm_bridge_add(bridge);
 
 	err = drm_bridge_attach(encoder, bridge, NULL);
diff --git a/drivers/gpu/drm/sti/sti_hda.c b/drivers/gpu/drm/sti/sti_hda.c
index 199db13f565c..7fcd24664cd0 100644
--- a/drivers/gpu/drm/sti/sti_hda.c
+++ b/drivers/gpu/drm/sti/sti_hda.c
@@ -694,6 +694,7 @@ static int sti_hda_bind(struct device *dev, struct device *master, void *data)
 	if (!bridge)
 		return -ENOMEM;
 
+	bridge->odev = dev;
 	bridge->driver_private = hda;
 	bridge->funcs = &sti_hda_bridge_funcs;
 	drm_bridge_attach(encoder, bridge, NULL);
diff --git a/drivers/gpu/drm/sti/sti_hdmi.c b/drivers/gpu/drm/sti/sti_hdmi.c
index 932724784942..d1d2e1a1920c 100644
--- a/drivers/gpu/drm/sti/sti_hdmi.c
+++ b/drivers/gpu/drm/sti/sti_hdmi.c
@@ -1270,6 +1270,7 @@ static int sti_hdmi_bind(struct device *dev, struct device *master, void *data)
 	if (!bridge)
 		return -EINVAL;
 
+	bridge->odev = dev;
 	bridge->driver_private = hdmi;
 	bridge->funcs = &sti_hdmi_bridge_funcs;
 	drm_bridge_attach(encoder, bridge, NULL);
-- 
2.11.0

  parent reply	other threads:[~2018-05-16 10:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16 10:14 [PATCH v3 00/26] device link, bridge supplier <-> drm device Peter Rosin
2018-05-16 10:14 ` [PATCH v3 01/26] drm/bridge: allow optionally specifying an owner .odev device Peter Rosin
2018-05-19 16:07   ` Heiko Stuebner
2018-05-16 10:14 ` [PATCH v3 02/26] drm/bridge: adv7511: provide " Peter Rosin
2018-05-16 10:14 ` [PATCH v3 03/26] drm/bridge/analogix: core: specify the owner .odev of the bridge Peter Rosin
2018-05-16 10:14 ` [PATCH v3 04/26] drm/bridge: analogix-anx78xx: provide an owner .odev device Peter Rosin
2018-05-16 10:14 ` [PATCH v3 05/26] drm/bridge: cdns-dsi: " Peter Rosin
2018-05-16 10:14 ` [PATCH v3 06/26] drm/bridge: vga-dac: " Peter Rosin
2018-05-16 10:14 ` [PATCH v3 07/26] drm/bridge: lvds-encoder: " Peter Rosin
2018-05-16 10:14 ` [PATCH v3 08/26] drm/bridge: megachips-stdpxxxx-ge-b850v3-fw: " Peter Rosin
2018-05-16 10:14 ` [PATCH v3 09/26] drm/bridge: nxp-ptn3460: " Peter Rosin
2018-05-16 10:14 ` [PATCH v3 10/26] drm/bridge: panel: " Peter Rosin
2018-05-16 10:14 ` [PATCH v3 11/26] drm/bridge: ps8622: " Peter Rosin
2018-05-16 10:14 ` [PATCH v3 12/26] drm/bridge: sii902x: " Peter Rosin
2018-05-16 10:14 ` [PATCH v3 13/26] drm/bridge: sii9234: " Peter Rosin
2018-05-16 10:14 ` [PATCH v3 14/26] drm/bridge: sii8620: " Peter Rosin
2018-05-16 10:14 ` [PATCH v3 15/26] drm/bridge: synopsys: provide an owner .odev device for the bridges Peter Rosin
2018-05-16 10:15 ` [PATCH v3 16/26] drm/bridge: tc358767: provide an owner .odev device Peter Rosin
2018-05-16 10:15 ` [PATCH v3 17/26] drm/bridge: thc63lvd1024: " Peter Rosin
2018-05-21  8:00   ` jacopo mondi
2018-05-16 10:15 ` [PATCH v3 18/26] drm/bridge: ti-tfp410: " Peter Rosin
2018-05-16 10:15 ` [PATCH v3 19/26] drm/exynos: mic: provide an owner .odev device for the bridge Peter Rosin
2018-05-16 10:15 ` [PATCH v3 20/26] drm/mediatek: hdmi: " Peter Rosin
2018-05-16 10:22   ` Philipp Zabel
2018-05-16 10:15 ` [PATCH v3 21/26] drm/msm: specify the owner .odev of the bridges Peter Rosin
2018-05-16 10:15 ` [PATCH v3 22/26] drm/rcar-du: lvds: provide an owner .odev device for the bridge Peter Rosin
2018-05-16 10:15 ` Peter Rosin [this message]
2018-05-16 10:15 ` [PATCH v3 24/26] drm/bridge: remove the .of_node member Peter Rosin
2018-05-19 16:08   ` Heiko Stuebner
2018-05-16 10:15 ` [PATCH v3 25/26] drm/bridge: require the owner .odev to be filled in on drm_bridge_add/attach Peter Rosin
2018-05-16 10:15 ` [PATCH v3 26/26] drm/bridge: establish a link between the bridge supplier and consumer Peter Rosin

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=20180516101510.13215-24-peda@axentia.se \
    --to=peda@axentia.se \
    --cc=airlied@linux.ie \
    --cc=benjamin.gaignard@linaro.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jsarha@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vincent.abriou@st.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;
as well as URLs for NNTP newsgroup(s).