From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: An Wu <an.wu@canonical.com>
Cc: andreas.noever@gmail.com, michael.jamet@intel.com,
YehezkelShB@gmail.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thunderbolt: Defer DP tunnel teardown until display driver is ready
Date: Mon, 1 Jun 2026 09:04:39 +0200 [thread overview]
Message-ID: <20260601070439.GO3102@black.igk.intel.com> (raw)
In-Reply-To: <CAO4Mv0ZbazqxzM9Sjd9=7YzMzZs6w54SLkhq+NtragOau5-eAA@mail.gmail.com>
Hi,
On Mon, Jun 01, 2026 at 02:50:21PM +0800, An Wu wrote:
> Hi Mika
>
> Another approach I considered is using register_module_notifier() to
> detect when a display driver module is loaded, then retrigger the DP
> tunnel setup. However, since struct module does not carry any device
> class or subsystem metadata, there is no generic way to identify
> whether a loaded module is a display driver. We would need to maintain
> a hardcoded list of known GPU module names (i915, xe, amdgpu, etc.),
> which is fragile and not scalable.
Indeed. Perhaps not to try to solve this in the kernel and instead do this
in userspace?
Have you actually measured how much initramfs size "increases" if you do
include the relevant graphics drivers and their dependencies?
next prev parent reply other threads:[~2026-06-01 7:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 6:41 [PATCH 0/1] " ChunAn Wu
2026-05-27 6:41 ` [PATCH] " ChunAn Wu
2026-05-27 7:14 ` Mika Westerberg
2026-05-28 1:03 ` An Wu
2026-05-28 10:29 ` Mika Westerberg
2026-06-01 2:45 ` An Wu
2026-06-01 6:50 ` An Wu
2026-06-01 7:04 ` Mika Westerberg [this message]
2026-06-01 8:18 ` An Wu
2026-06-05 10:16 ` An Wu
2026-07-16 18:31 ` Mario Limonciello
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=20260601070439.GO3102@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=an.wu@canonical.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
/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
Powered by JetHome