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 v3 1/2] platform/chrome: cros_ec_typec: Enforce priority-based mode selection
Date: Thu, 29 Oct 2026 04:19:08 +0000 [thread overview]
Message-ID: <auLJPLArIkwFHtRj@google.com> (raw)
In-Reply-To: <20261028090932.27053-2-akuchynski@chromium.org>
On Wed, Oct 28, 2026 at 09:09:31AM +0000, Andrei Kuchynski wrote:
> The driver sets mode_selection bit for each Alternate mode, thereby
> preventing individual altmode drivers from activating their respective
> modes.
> Once the registration of all Alternate Modes is complete, the driver
> verifies if USB4 mode is supported by both the port and the partner and
> activates USB4 mode. In cases where USB4 is not supported, the driver
> invokes typec_mode_selection_start to initiate the mode selection process
> based on mode priorities.
> The driver communicates the current Type-C mode to the mode selection
> process via typec_altmode_state_update.
Hi Andrei,
I'm less familiar with the details of cros_ec_typec and its friend drivers.
Could you double-check the Sashiko review [1] to see if any of the findings
need to be addressed as they look real?
[1] https://sashiko.dev/#/patchset/20261028090932.27053-1-akuchynski%40chromium.org
next prev parent reply other threads:[~2026-10-29 4:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 9:09 [PATCH v3 0/2] USB Type-C " Andrei Kuchynski
2026-10-28 9:09 ` [PATCH v3 1/2] platform/chrome: cros_ec_typec: Enforce priority-based " Andrei Kuchynski
2026-10-29 4:19 ` Tzung-Bi Shih [this message]
2026-10-29 12:29 ` Andrei Kuchynski
2026-10-28 9:09 ` [PATCH v3 2/2] platform/chrome: cros_ec_typec: Reorder altmode registration Andrei Kuchynski
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=auLJPLArIkwFHtRj@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®