[PATCH v2 0/4] drm/bridge: Allow using fwnode API to get the next bridge
Sui Jingfeng
sui.jingfeng at linux.dev
Thu Mar 7 17:23:30 UTC 2024
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
More information about the dri-devel
mailing list