From: sashiko-bot@kernel.org
To: "Chaoyi Chen" <kernel@airkyi.com>
Cc: linux-phy@lists.infradead.org, dri-devel@lists.freedesktop.org,
vkoul@kernel.org, neil.armstrong@linaro.org, olteanv@gmail.com
Subject: Re: [PATCH v7 3/7] drm/display: Add soft depend for aux-hpd-typec-dp-bridge module
Date: Fri, 28 Aug 2026 08:56:34 +0000 [thread overview]
Message-ID: <20260828085634.922FD1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260828084737.565-4-kernel@airkyi.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Dependency inversion unconditionally loads USB Type-C subsystem on all DP-capable systems
--
commit 18e75df5599eb3c3479dc1002547dcf5f6a1593b
Author: Chaoyi Chen <chaoyi.chen@rock-chips.com>
drm/display: Add soft depend for aux-hpd-typec-dp-bridge module
This commit adds a soft dependency in the drm_display_helper module for the
aux-hpd-typec-dp-bridge module. This ensures the bridge module is loaded
early, as it serves as a generic Type-C DisplayPort HPD bridge that isn't
directly required by any other module.
> diff --git a/drivers/gpu/drm/display/drm_display_helper_mod.c b/drivers/gpu/drm/display/drm_display_helper_mod.c
> index d8a6e62287736..f0152d6b0b2d7 100644
> --- a/drivers/gpu/drm/display/drm_display_helper_mod.c
> +++ b/drivers/gpu/drm/display/drm_display_helper_mod.c
> @@ -18,5 +18,6 @@ static void __exit drm_display_helper_module_exit(void)
> drm_dp_aux_dev_exit();
> }
>
> +MODULE_SOFTDEP("pre: aux-hpd-typec-dp-bridge");
[Severity: Medium]
Does adding a soft dependency on aux-hpd-typec-dp-bridge to the core
drm_display_helper module create an architectural dependency inversion?
The leaf bridge driver (aux-hpd-typec-dp-bridge) has a hard dependency on the
typec core subsystem because it registers a bus notifier on typec_bus. As a
result, when a system loads a DRM driver that utilizes generic display helpers
(such as amdgpu, i915, or nouveau), won't this unconditionally pull the entire
USB Type-C subsystem into memory?
This seems like it might waste memory resources on systems without Type-C
hardware by automatically loading aux-hpd-typec-dp-bridge.ko (and consequently
typec.ko) upon loading any standard DRM driver. Is there a better way to
handle this without burdening all generic display helper users?
> module_init(drm_display_helper_module_init);
> module_exit(drm_display_helper_module_exit);
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260828084737.565-1-kernel@airkyi.com?part=3
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Chaoyi Chen" <kernel@airkyi.com>
Cc: linux-phy@lists.infradead.org, dri-devel@lists.freedesktop.org,
vkoul@kernel.org, neil.armstrong@linaro.org, olteanv@gmail.com
Subject: Re: [PATCH v7 3/7] drm/display: Add soft depend for aux-hpd-typec-dp-bridge module
Date: Fri, 28 Aug 2026 08:56:34 +0000 [thread overview]
Message-ID: <20260828085634.922FD1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260828084737.565-4-kernel@airkyi.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Dependency inversion unconditionally loads USB Type-C subsystem on all DP-capable systems
--
commit 18e75df5599eb3c3479dc1002547dcf5f6a1593b
Author: Chaoyi Chen <chaoyi.chen@rock-chips.com>
drm/display: Add soft depend for aux-hpd-typec-dp-bridge module
This commit adds a soft dependency in the drm_display_helper module for the
aux-hpd-typec-dp-bridge module. This ensures the bridge module is loaded
early, as it serves as a generic Type-C DisplayPort HPD bridge that isn't
directly required by any other module.
> diff --git a/drivers/gpu/drm/display/drm_display_helper_mod.c b/drivers/gpu/drm/display/drm_display_helper_mod.c
> index d8a6e62287736..f0152d6b0b2d7 100644
> --- a/drivers/gpu/drm/display/drm_display_helper_mod.c
> +++ b/drivers/gpu/drm/display/drm_display_helper_mod.c
> @@ -18,5 +18,6 @@ static void __exit drm_display_helper_module_exit(void)
> drm_dp_aux_dev_exit();
> }
>
> +MODULE_SOFTDEP("pre: aux-hpd-typec-dp-bridge");
[Severity: Medium]
Does adding a soft dependency on aux-hpd-typec-dp-bridge to the core
drm_display_helper module create an architectural dependency inversion?
The leaf bridge driver (aux-hpd-typec-dp-bridge) has a hard dependency on the
typec core subsystem because it registers a bus notifier on typec_bus. As a
result, when a system loads a DRM driver that utilizes generic display helpers
(such as amdgpu, i915, or nouveau), won't this unconditionally pull the entire
USB Type-C subsystem into memory?
This seems like it might waste memory resources on systems without Type-C
hardware by automatically loading aux-hpd-typec-dp-bridge.ko (and consequently
typec.ko) upon loading any standard DRM driver. Is there a better way to
handle this without burdening all generic display helper users?
> module_init(drm_display_helper_module_init);
> module_exit(drm_display_helper_module_exit);
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260828084737.565-1-kernel@airkyi.com?part=3
next prev parent reply other threads:[~2026-08-28 8:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 8:47 [PATCH v7 0/7] drm/bridge: Implement generic USB Type-C DP HPD bridge Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 8:47 ` [PATCH v7 1/7] drm/bridge: aux-hpd-bridge: Add drm_dev_has_dp_hpd_bridge() Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 8:47 ` [PATCH v7 2/7] drm/bridge: Implement generic USB Type-C DP HPD bridge Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 9:04 ` sashiko-bot
2026-08-28 9:04 ` sashiko-bot
2026-08-28 8:47 ` [PATCH v7 3/7] drm/display: Add soft depend for aux-hpd-typec-dp-bridge module Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 8:56 ` sashiko-bot [this message]
2026-08-28 8:56 ` sashiko-bot
2026-08-28 8:47 ` [PATCH v7 4/7] drm/bridge: aux: Add drm_aux_bridge_register_from_node() Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 8:57 ` sashiko-bot
2026-08-28 8:57 ` sashiko-bot
2026-08-28 8:47 ` [PATCH v7 5/7] phy: rockchip: phy-rockchip-typec: Add DRM AUX bridge Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 9:01 ` sashiko-bot
2026-08-28 9:01 ` sashiko-bot
2026-08-28 8:47 ` [PATCH v7 6/7] drm/rockchip: cdn-dp: Support handle lane info without extcon Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 9:07 ` sashiko-bot
2026-08-28 9:07 ` sashiko-bot
2026-08-28 8:47 ` [PATCH v7 7/7] drm/rockchip: cdn-dp: Add multiple bridges to support PHY port selection Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 8:47 ` Chaoyi Chen
2026-08-28 9:14 ` sashiko-bot
2026-08-28 9:14 ` sashiko-bot
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=20260828085634.922FD1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@airkyi.com \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.