public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 1/2] platform/chrome: cros_ec_typec: Enforce priority-based mode selection
Date: Fri, 30 Jan 2026 03:26:55 +0000	[thread overview]
Message-ID: <aXwk_wzeF9UPd5DK@google.com> (raw)
In-Reply-To: <20260129131928.794768-1-akuchynski@chromium.org>

On Thu, Jan 29, 2026 at 01:19:27PM +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.

I find the message doesn't help me too much for understanding the patch.
Can you rephrase them and assuming readers might not have too much context?

> ---
>  drivers/platform/chrome/cros_ec_typec.c      | 39 +++++++++++++++++++-
>  drivers/platform/chrome/cros_typec_altmode.c |  8 +++-
>  2 files changed, 44 insertions(+), 3 deletions(-)

The patch uses some exported symbols which aren't yet in upstream
(drivers/usb/typec/mode_selection.c).  Ideally, you should mention that in
either cover letter or note after "---".

> +/* Delay between mode entry/exit attempts, ms */
> +static const unsigned int mode_selection_delay = 1000;
> +/* Timeout for a mode entry attempt, ms */
> +static const unsigned int mode_selection_timeout = 4000;

The commit message probably needs some description about why these values.

      parent reply	other threads:[~2026-01-30  3:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29 13:19 [PATCH 1/2] platform/chrome: cros_ec_typec: Enforce priority-based mode selection Andrei Kuchynski
2026-01-29 13:19 ` [PATCH 2/2] platform/chrome: cros_ec_typec: Reorder altmode registration Andrei Kuchynski
2026-01-30  3:26 ` 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=aXwk_wzeF9UPd5DK@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