From: Sui Jingfeng <sui.jingfeng@linux.dev>
To: Andrzej Hajda <andrzej.hajda@intel.com>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Phong LE <ple@baylibre.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Sui Jingfeng <sui.jingfeng@linux.dev>
Subject: [PATCH v2 0/4] drm/bridge: Allow using fwnode API to get the next bridge
Date: Fri, 8 Mar 2024 01:23:30 +0800 [thread overview]
Message-ID: <20240307172334.1753343-1-sui.jingfeng@linux.dev> (raw)
Currently, the various drm bridge drivers relay on OF infrastructures to
works very well. Yet there are platforms and/or don not has OF support.
Such as virtual display drivers, USB display apapters and ACPI based
systems etc. Add fwnode based helpers to fill the niche, this may allows
part of the drm display bridge drivers to work across systems. As the
fwnode based API has wider coverage than DT, it can be used on all systems
in theory. Assumed that the system has valid fwnode graphs established
before drm bridge driver is probed, the fwnode graphs are compatible with
the OF graph.
Tested on TI BeaglePlay board and other platforms.
v1 at https://patchwork.freedesktop.org/series/129040/
v2:
* Modify it66121 to switch togather
* Drop the 'side-by-side' implement
* Add drm_bridge_find_next_bridge_by_fwnode() helper
* Add drm_bridge_set_node() helper
Sui Jingfeng (4):
drm/bridge: Add fwnode based helpers to get the next bridge
drm/bridge: simple-bridge: Use fwnode API to acquire device properties
drm-bridge: display-connector: Use fwnode API to acquire device
properties
drm-bridge: it66121: Use fwnode API to acquire device properties
drivers/gpu/drm/bridge/display-connector.c | 24 ++++----
drivers/gpu/drm/bridge/ite-it66121.c | 63 +++++++++++---------
drivers/gpu/drm/bridge/simple-bridge.c | 22 ++++---
drivers/gpu/drm/drm_bridge.c | 68 ++++++++++++++++++++++
include/drm/drm_bridge.h | 16 +++++
5 files changed, 142 insertions(+), 51 deletions(-)
--
2.34.1
next reply other threads:[~2024-03-07 17:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 17:23 Sui Jingfeng [this message]
2024-03-07 17:23 ` [PATCH v2 1/4] drm/bridge: Add fwnode based helpers to get the next bridge Sui Jingfeng
2024-03-07 18:43 ` Dmitry Baryshkov
2024-03-07 19:20 ` Sui Jingfeng
2024-03-07 19:30 ` Sui Jingfeng
2024-03-07 19:37 ` Dmitry Baryshkov
2024-03-07 20:32 ` Sui Jingfeng
2024-03-07 20:40 ` Dmitry Baryshkov
2024-03-07 21:09 ` Sui Jingfeng
2024-03-07 21:13 ` Sui Jingfeng
2024-03-09 9:33 ` Sui Jingfeng
2024-03-09 10:39 ` Dmitry Baryshkov
2024-03-09 11:25 ` Sui Jingfeng
2024-03-09 12:50 ` Dmitry Baryshkov
2024-03-09 12:03 ` Sui Jingfeng
2024-03-09 13:29 ` Dmitry Baryshkov
2024-03-07 17:23 ` [PATCH v2 2/4] drm/bridge: simple-bridge: Use fwnode API to acquire device properties Sui Jingfeng
2024-03-07 17:23 ` [PATCH v2 3/4] drm-bridge: display-connector: " Sui Jingfeng
2024-03-07 17:23 ` [PATCH v2 4/4] drm-bridge: it66121: " Sui Jingfeng
2024-03-07 19:31 ` Dmitry Baryshkov
2024-03-07 19:39 ` Sui Jingfeng
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=20240307172334.1753343-1-sui.jingfeng@linux.dev \
--to=sui.jingfeng@linux.dev \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=ple@baylibre.com \
--cc=rfoss@kernel.org \
--cc=tzimmermann@suse.de \
/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