From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Andrei Kuchynski <akuchynski@chromium.org>
Cc: Abhishek Pandit-Subedi <abhishekpandit@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>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
"Christian A. Ehrhardt" <lk@c--e.de>,
Venkat Jayaraman <venkat.jayaraman@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/5] usb: typec: ucsi: Set no_mode_control flag
Date: Tue, 9 Sep 2025 12:07:51 +0300 [thread overview]
Message-ID: <aL_uZxBkBfC9Etrk@kuha.fi.intel.com> (raw)
In-Reply-To: <20250905142206.4105351-4-akuchynski@chromium.org>
On Fri, Sep 05, 2025 at 02:22:04PM +0000, Andrei Kuchynski wrote:
> This flag indicates that the PPM allows the OPM to change the currently
> negotiated alternate mode using the SET_NEW_CAM command.
>
> Signed-off-by: Andrei Kuchynski <akuchynski@chromium.org>
> ---
> drivers/usb/typec/ucsi/ucsi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/usb/typec/ucsi/ucsi.c b/drivers/usb/typec/ucsi/ucsi.c
> index 0d6b0cf5a7cd..9f754344a841 100644
> --- a/drivers/usb/typec/ucsi/ucsi.c
> +++ b/drivers/usb/typec/ucsi/ucsi.c
> @@ -1632,6 +1632,7 @@ static int ucsi_register_port(struct ucsi *ucsi, struct ucsi_connector *con)
>
> cap->driver_data = con;
> cap->ops = &ucsi_ops;
> + cap->no_mode_control = !(con->ucsi->cap.features & UCSI_CAP_ALT_MODE_OVERRIDE);
The flag is now used to expose the priority file, but you can't affect
the order in which the UCSI attempts to enter the modes, or can you?
thanks,
--
heikki
next prev parent reply other threads:[~2025-09-09 9:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 14:22 [PATCH v3 0/5] USB Type-C alternate mode priorities Andrei Kuchynski
2025-09-05 14:22 ` [PATCH v3 1/5] usb: typec: Add mode_control field to port property Andrei Kuchynski
2025-09-09 8:47 ` Heikki Krogerus
2025-09-10 13:30 ` Greg Kroah-Hartman
2025-09-10 19:34 ` Andrei Kuchynski
2025-09-05 14:22 ` [PATCH v3 2/5] platform/chrome: cros_ec_typec: Set no_mode_control flag Andrei Kuchynski
2025-09-08 3:57 ` Tzung-Bi Shih
2025-09-05 14:22 ` [PATCH v3 3/5] usb: typec: ucsi: " Andrei Kuchynski
2025-09-09 9:07 ` Heikki Krogerus [this message]
2025-09-09 9:22 ` Andrei Kuchynski
2025-09-10 19:36 ` Andrei Kuchynski
2025-09-05 14:22 ` [PATCH v3 4/5] usb: typec: Implement alternate mode priority handling Andrei Kuchynski
2025-09-09 8:50 ` Heikki Krogerus
2025-09-10 13:31 ` Greg Kroah-Hartman
2025-09-10 19:35 ` Andrei Kuchynski
2025-09-11 5:07 ` Greg Kroah-Hartman
2025-09-11 8:46 ` Andrei Kuchynski
2025-09-11 10:41 ` Greg Kroah-Hartman
2025-09-11 13:11 ` Andrei Kuchynski
2025-09-05 14:22 ` [PATCH v3 5/5] usb: typec: Expose alternate mode priority via sysfs Andrei Kuchynski
2025-09-10 13:27 ` Greg Kroah-Hartman
2025-09-10 19:34 ` 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=aL_uZxBkBfC9Etrk@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=abhishekpandit@chromium.org \
--cc=akuchynski@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=jthies@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lk@c--e.de \
--cc=tzungbi@kernel.org \
--cc=venkat.jayaraman@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