linux-kernel - [PATCH v3 0/5] drm/bridge: Allow using fwnode API to get the next bridge

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date: Mon, 11 Mar 2024 16:56:54 +0800
From: Sui Jingfeng <sui.jingfeng@...ux.dev>
To: Andrzej Hajda <andrzej.hajda@...el.com>
Cc: Neil Armstrong <neil.armstrong@...aro.org>,
	Robert Foss <rfoss@...nel.org>,
	Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
	Jonas Karlman <jonas@...boo.se>,
	Jernej Skrabec <jernej.skrabec@...il.com>,
	Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
	Maxime Ripard <mripard@...nel.org>,
	Thomas Zimmermann <tzimmermann@...e.de>,
	David Airlie <airlied@...il.com>,
	Daniel Vetter <daniel@...ll.ch>,
	Phong LE <ple@...libre.com>,
	dri-devel@...ts.freedesktop.org,
	linux-kernel@...r.kernel.org,
	Sui Jingfeng <sui.jingfeng@...ux.dev>
Subject: [PATCH v3 0/5] drm/bridge: Allow using fwnode API to get the next bridge

Currently, the various drm bridge drivers relay on OF infrastructures to
works very well. Yet there are platforms and/or devices absence of OF
support. Such as virtual display drivers, USB display apapters and ACPI
based systems etc.

Add fwnode based helpers to fill the niche, this allows part of the drm
display bridge drivers to work across systems. As the fwnode based API
has wider coverage than DT and the fwnode graphs are compatible with
the OF graph, so the provided helpers can be used on all systems in theory.
Assumed that the system has valid fwnode graphs established before the
drm bridge driver is probed, and there is a fwnode assigned to the instance
of specific drm bridge driver.

Tested on TI BeaglePlay board and other platforms.

v1 -> 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

v2 -> v3:
	 * Read kernel-doc and improve function comments
	 * Drop the 'port' argument of it66121_read_bus_width() (Dmitry)
	 * Do more by covertering the sii902x drm bridge drviers

Sui Jingfeng (5):
  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
  drm-bridge: sii902x: 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/sii902x.c           | 43 +++++--------
 drivers/gpu/drm/bridge/simple-bridge.c     | 22 +++----
 drivers/gpu/drm/drm_bridge.c               | 72 ++++++++++++++++++++++
 include/drm/drm_bridge.h                   | 16 +++++
 6 files changed, 159 insertions(+), 81 deletions(-)


base-commit: 3fde6df89bac97416ce1c82b14237a1a67ce3285
-- 
2.34.1