From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Andrzej Hajda <andrzej.hajda@intel.com>,
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>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Daniel Stone <daniel@fooishbar.org>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
kernel@collabora.com, Daniel Stone <daniels@collabora.com>
Subject: Re: [PATCH v5 3/4] drm/display: bridge_connector: init scdc debugfs for HDMI
Date: Sat, 06 Jun 2026 20:39:39 +0200 [thread overview]
Message-ID: <kFXCAerTTJqUXQYeypgmPw@collabora.com> (raw)
In-Reply-To: <20260606-bright-smooth-chihuahua-3eac7f@houat>
On Saturday, 6 June 2026 10:54:23 Central European Summer Time Maxime Ripard wrote:
> Hi,
>
> On Thu, Jun 04, 2026 at 05:52:08PM +0200, Nicolas Frattaroli wrote:
> > On drm_bridge_connectors that contain an HDMI bridge, initialise the
> > SCDC debugfs entry under the connector's debugfs root.
> >
> > Reviewed-by: Daniel Stone <daniels@collabora.com>
> > Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
> > ---
> > drivers/gpu/drm/display/drm_bridge_connector.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/display/drm_bridge_connector.c b/drivers/gpu/drm/display/drm_bridge_connector.c
> > index cafa498c3848..629d9b8aff22 100644
> > --- a/drivers/gpu/drm/display/drm_bridge_connector.c
> > +++ b/drivers/gpu/drm/display/drm_bridge_connector.c
> > @@ -25,6 +25,7 @@
> > #include <drm/display/drm_hdmi_cec_helper.h>
> > #include <drm/display/drm_hdmi_helper.h>
> > #include <drm/display/drm_hdmi_state_helper.h>
> > +#include <drm/display/drm_scdc_helper.h>
> >
> > /**
> > * DOC: overview
> > @@ -263,6 +264,9 @@ static void drm_bridge_connector_debugfs_init(struct drm_connector *connector,
> > if (bridge->funcs->debugfs_init)
> > bridge->funcs->debugfs_init(bridge, root);
> > }
> > +
> > + if (bridge_connector->bridge_hdmi)
> > + drm_scdc_debugfs_init(connector, root);
> > }
>
> We register the other debugfs entries in drm_debugfs_connector_add /
> hdmi_debugfs_add. I don't think there's anything specific to bridge
> connector here and it would benefit to drivers that don't use it as
> well, so I think putting it in the generic part of the framework would
> be better.
Yeah, I tried that, but unfortunately this creates a dependency cycle
during linking:
depmod: ERROR: Cycle detected: drm_display_helper -> drm_kms_helper -> drm -> drm_display_helper
depmod: ERROR: Cycle detected: drm_display_helper -> drm -> drm_display_helper
depmod: ERROR: Found 3 modules in dependency cycles!
My way of working around this was to move it into the target of the
indirect function call for the connector, in this case the bridge
connector.
If you have alternate suggestions I'm open to them; I don't know
enough about the kernel's linking process and how people usually
resolve these issues.
Kind regards,
Nicolas Frattaroli
>
> Maxime
>
next prev parent reply other threads:[~2026-06-06 18:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 15:52 [PATCH v5 0/4] Add SCDC information to connector debugfs Nicolas Frattaroli
2026-06-04 15:52 ` [PATCH v5 1/4] drm/scdc-helper: Don't use ssize_t return type for scdc_read/write Nicolas Frattaroli
2026-06-04 15:52 ` [PATCH v5 2/4] drm/scdc-helper: Add scdc_status debugfs entry Nicolas Frattaroli
2026-06-06 11:43 ` Hans Verkuil
2026-06-04 15:52 ` [PATCH v5 3/4] drm/display: bridge_connector: init scdc debugfs for HDMI Nicolas Frattaroli
2026-06-06 8:54 ` Maxime Ripard
2026-06-06 18:39 ` Nicolas Frattaroli [this message]
2026-06-04 15:52 ` [PATCH v5 4/4] drm/scdc-helper: Implement parsing and printing HDMI 2.1 fields Nicolas Frattaroli
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=kFXCAerTTJqUXQYeypgmPw@collabora.com \
--to=nicolas.frattaroli@collabora.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@fooishbar.org \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil+cisco@kernel.org \
--cc=jani.nikula@linux.intel.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--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
all inboxes | Powered by JetHome®