From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Andrei Kuchynski <akuchynski@chromium.org>
Cc: Jameson Thies <jthies@google.com>,
Benson Leung <bleung@chromium.org>,
Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] USB Type-C mode selection
Date: Fri, 6 Nov 2026 02:32:02 +0000 [thread overview]
Message-ID: <au08ImBfMix9nNAV@google.com> (raw)
In-Reply-To: <20261105155906.2670094-1-akuchynski@chromium.org>
On Thu, Nov 05, 2026 at 03:59:04PM +0000, Andrei Kuchynski wrote:
> This patch series introduces priority-based alternate mode selection
> support for cros_ec_typec.
> The base patch series and UCSI support was submitted here:
> https://lore.kernel.org/all/20260119131824.2529334-1-akuchynski@chromium.org/
>
> When AP-driven alternate mode selection is active, the driver enforces the
> mode_selection bit for each registered Alternate Mode. This blocks
> individual altmode drivers from self-activating. Once registration
> completes, the driver evaluates USB4 capability. If USB4 is unsupported,
> it falls back to priority-based negotiation via typec_mode_selection_start.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
[1/2] platform/chrome: cros_ec_typec: Enforce priority-based mode selection
commit: 8dd5100e565ea8a89ef20b2a3512e6b31be9356b
[2/2] platform/chrome: cros_ec_typec: Reorder altmode registration
commit: 2d234d566e1fb434fbff7827872a3da7aa8064c1
Thanks!
prev parent reply other threads:[~2026-11-06 2:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 15:59 Andrei Kuchynski
2026-11-05 15:59 ` [PATCH v4 1/2] platform/chrome: cros_ec_typec: Enforce priority-based " Andrei Kuchynski
2026-11-05 15:59 ` [PATCH v4 2/2] platform/chrome: cros_ec_typec: Reorder altmode registration Andrei Kuchynski
2026-11-06 2:32 ` Tzung-Bi Shih [this message]
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=au08ImBfMix9nNAV@google.com \
--to=tzungbi@kernel.org \
--cc=abhishekpandit@chromium.org \
--cc=akuchynski@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=jthies@google.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®