From: peda@axentia.se (Peter Rosin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/24] device link, bridge supplier <-> drm device
Date: Fri, 27 Apr 2018 00:31:15 +0200 [thread overview]
Message-ID: <20180426223139.16740-1-peda@axentia.se> (raw)
Hi!
It was noted by Russel King [1] that bridges (not using components)
might disappear unexpectedly if the owner of the bridge was unbound.
Jyri Sarha had previously noted the same thing with panels [2]. Jyri
came up with using device links to resolve the panel issue, which
was also my (independent) reaction to the note from Russel.
This series builds up to the addition of that link in the last
patch, but in my opinion the other 23 patches do have merit on their
own.
The last patch needs testing, while the others look trivial. That
said, I might have missed some subtlety.
Cheers,
Peter
[1] https://lkml.org/lkml/2018/4/23/769
[2] https://www.spinics.net/lists/dri-devel/msg174275.html
Peter Rosin (24):
drm/bridge: allow optionally specifying an .owner device
drm/bridge: adv7511: provide an .owner device
drm/bridge/analogix: core: specify the .owner of the bridge
drm/bridge: analogix-anx78xx: provide an .owner device
drm/bridge: vga-dac: provide an .owner device
drm/bridge: lvds-encoder: provide an .owner device
drm/bridge: megachips-stdpxxxx-ge-b850v3-fw: provide an .owner device
drm/bridge: nxp-ptn3460: provide an .owner device
drm/bridge: panel: provide an .owner device
drm/bridge: ps8622: provide an .owner device
drm/bridge: sii902x: provide an .owner device
drm/bridge: sii9234: provide an .owner device
drm/bridge: sii8620: provide an .owner device
drm/bridge: synopsys: provide an .owner device for the bridges
drm/bridge: tc358767: provide an .owner device
drm/bridge: ti-tfp410: provide an .owner device
drm/exynos: mic: provide an .owner device for the bridge
drm/mediatek: hdmi: provide an .owner device for the bridge
drm/msm: specify the .owner of the bridges
drm/rcar-du: lvds: provide an .owner device for the bridge
drm/sti: provide an .owner device for the bridges
drm/bridge: remove the .of_node member
drm/bridge: require the .owner to be filled in on drm_bridge_attach
drm/bridge: establish a link between the bridge supplier and consumer
drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 2 +-
drivers/gpu/drm/bridge/analogix-anx78xx.c | 5 +----
drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 1 +
drivers/gpu/drm/bridge/dumb-vga-dac.c | 2 +-
drivers/gpu/drm/bridge/lvds-encoder.c | 2 +-
.../drm/bridge/megachips-stdpxxxx-ge-b850v3-fw.c | 2 +-
drivers/gpu/drm/bridge/nxp-ptn3460.c | 2 +-
drivers/gpu/drm/bridge/panel.c | 4 +---
drivers/gpu/drm/bridge/parade-ps8622.c | 2 +-
drivers/gpu/drm/bridge/sii902x.c | 2 +-
drivers/gpu/drm/bridge/sii9234.c | 2 +-
drivers/gpu/drm/bridge/sil-sii8620.c | 2 +-
drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 4 +---
drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c | 4 +---
drivers/gpu/drm/bridge/tc358767.c | 2 +-
drivers/gpu/drm/bridge/ti-tfp410.c | 2 +-
drivers/gpu/drm/drm_bridge.c | 23 +++++++++++++++++++++-
drivers/gpu/drm/exynos/exynos_drm_mic.c | 2 +-
drivers/gpu/drm/mediatek/mtk_hdmi.c | 2 +-
drivers/gpu/drm/msm/dsi/dsi_manager.c | 1 +
drivers/gpu/drm/msm/edp/edp_bridge.c | 1 +
drivers/gpu/drm/msm/hdmi/hdmi_bridge.c | 1 +
drivers/gpu/drm/rcar-du/rcar_lvds.c | 2 +-
drivers/gpu/drm/sti/sti_dvo.c | 2 +-
drivers/gpu/drm/sti/sti_hda.c | 1 +
drivers/gpu/drm/sti/sti_hdmi.c | 1 +
include/drm/drm_bridge.h | 8 ++++----
27 files changed, 51 insertions(+), 33 deletions(-)
--
2.11.0
next reply other threads:[~2018-04-26 22:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180426223215epcas2p38fe3b0b7b1ea1c8190805f9e2a89e11e@epcas2p3.samsung.com>
2018-04-26 22:31 ` Peter Rosin [this message]
2018-04-26 22:31 ` [PATCH 01/24] drm/bridge: allow optionally specifying an .owner device Peter Rosin
2018-04-26 22:31 ` [PATCH 17/24] drm/exynos: mic: provide an .owner device for the bridge Peter Rosin
2018-04-26 22:31 ` [PATCH 18/24] drm/mediatek: hdmi: " Peter Rosin
2018-04-26 22:31 ` [PATCH 22/24] drm/bridge: remove the .of_node member Peter Rosin
2018-04-28 8:09 ` kbuild test robot
2018-04-30 11:14 ` Peter Rosin
2018-04-26 22:31 ` [PATCH 23/24] drm/bridge: require the .owner to be filled in on drm_bridge_attach Peter Rosin
2018-04-30 15:24 ` Daniel Vetter
2018-04-30 20:32 ` Peter Rosin
2018-04-26 22:31 ` [PATCH 24/24] drm/bridge: establish a link between the bridge supplier and consumer Peter Rosin
2018-04-30 15:32 ` Daniel Vetter
2018-04-30 21:12 ` Peter Rosin
2018-04-27 7:11 ` [PATCH 00/24] device link, bridge supplier <-> drm device Andrzej Hajda
2018-04-27 7:37 ` Peter Rosin
2018-04-27 7:51 ` Peter Rosin
[not found] ` <1881012.XPHlTWYXH6@avalon>
2018-04-26 23:09 ` Peter Rosin
[not found] ` <3483427.EaMxDYJt8U@avalon>
2018-04-27 7:27 ` Peter Rosin
2018-04-30 15:18 ` Daniel Vetter
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=20180426223139.16740-1-peda@axentia.se \
--to=peda@axentia.se \
--cc=linux-arm-kernel@lists.infradead.org \
/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