drm/bridge: Add debugfs print for bridge chains
authorTomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Wed, 2 Aug 2023 07:04:11 +0000 (10:04 +0300)
committerNeil Armstrong <neil.armstrong@linaro.org>
Wed, 2 Aug 2023 08:05:01 +0000 (10:05 +0200)
commit8e4bb53c902ed2b06a2c4778e6dbb2c1eeec4960
tree13da02f70a939acdd39051504a0935cc18f02f7a
parent76edfcf430cc2fa1abcfb910a2643eed102a1590
drm/bridge: Add debugfs print for bridge chains

DRM bridges are not visible to the userspace and it may not be
immediately clear if the chain is somehow constructed incorrectly. I
have had two separate instances of a bridge driver failing to do a
drm_bridge_attach() call, resulting in the bridge connector not being
part of the chain. In some situations this doesn't seem to cause issues,
but it will if DRM_BRIDGE_ATTACH_NO_CONNECTOR flag is used.

Add a debugfs file to print the bridge chains. For me, on this TI AM62
based platform, I get the following output:

encoder[39]
bridge[0] type: 0, ops: 0x0
bridge[1] type: 0, ops: 0x0, OF: /bus@f0000/i2c@20000000/dsi@e:toshiba,tc358778
bridge[2] type: 0, ops: 0x3, OF: /bus@f0000/i2c@20010000/hdmi@48:lontium,lt8912b
bridge[3] type: 11, ops: 0x7, OF: /hdmi-connector:hdmi-connector

Tested-by: Alexander Stein <alexander.stein@ew.tq-group.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Acked-by: Neil Armstrong <neil.armstrong@linaro.org>
Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
Link: https://patchwork.freedesktop.org/patch/msgid/20230802-drm-bridge-chain-debugfs-v4-1-7e3ae3d137c0@ideasonboard.com
drivers/gpu/drm/drm_bridge.c
drivers/gpu/drm/drm_debugfs.c
include/drm/drm_bridge.h