From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Andrei Kuchynski <akuchynski@chromium.org>,
Benson Leung <bleung@chromium.org>,
Jameson Thies <jthies@google.com>,
Tzung-Bi Shih <tzungbi@kernel.org>,
linux-usb@vger.kernel.org, chrome-platform@lists.linux.dev,
Guenter Roeck <groeck@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/5] USB Type-C alternate mode selection
Date: Thu, 18 Sep 2025 09:50:00 +0200 [thread overview]
Message-ID: <2025091821-bony-defame-02f6@gregkh> (raw)
In-Reply-To: <CANFp7mVwZksBYBOgPLDDYiynjFDh3jJqY1PFvvBWxtFd8MMYjw@mail.gmail.com>
On Wed, Sep 17, 2025 at 05:09:44PM -0700, Abhishek Pandit-Subedi wrote:
> After actually trying to do this today, I think a better approach
> might be to just add a MODULE_SOFTDEP for all the typec altmodes. That
> way, all the modules get loaded together and there's less of a chance
> of waiting for the altmode driver to load when enumerating partners on
> boot.
MODULE_SOFTDEP is going to be nothing but problems going forward, I
wouldn't recommend it at all. Try it out yourself on your hardware and
see :)
thanks,
greg k-h
next prev parent reply other threads:[~2025-09-18 7:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 12:30 [PATCH RFC 0/5] USB Type-C alternate mode selection Andrei Kuchynski
2025-09-09 12:30 ` [PATCH RFC 1/5] usb: typec: Implement " Andrei Kuchynski
2025-09-09 12:30 ` [PATCH RFC 2/5] usb: typec: Expose mode_selection attribute via sysfs Andrei Kuchynski
2025-09-09 12:30 ` [PATCH RFC 3/5] usb: typec: Report altmode entry status via callback Andrei Kuchynski
2025-09-09 12:30 ` [PATCH RFC 4/5] usb: typec: ucsi: displayport: Propagate DP altmode entry result Andrei Kuchynski
2025-09-09 12:30 ` [PATCH RFC 5/5] platform/chrome: cros_ec_typec: Propagate " Andrei Kuchynski
2025-09-16 13:12 ` [PATCH RFC 0/5] USB Type-C alternate mode selection Heikki Krogerus
2025-09-16 16:47 ` Abhishek Pandit-Subedi
2025-09-17 12:28 ` Heikki Krogerus
2025-09-17 17:51 ` Abhishek Pandit-Subedi
2025-09-18 0:09 ` Abhishek Pandit-Subedi
2025-09-18 7:50 ` Greg Kroah-Hartman [this message]
2025-09-19 11:50 ` Heikki Krogerus
2025-09-19 16:58 ` Abhishek Pandit-Subedi
2025-09-22 13:50 ` Heikki Krogerus
2025-09-23 19:23 ` Abhishek Pandit-Subedi
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=2025091821-bony-defame-02f6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=abhishekpandit@chromium.org \
--cc=akuchynski@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jthies@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tzungbi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox