[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251201122604.1268071-1-akuchynski@chromium.org>
Date: Mon, 1 Dec 2025 12:25:56 +0000
From: Andrei Kuchynski <akuchynski@...omium.org>
To: Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Abhishek Pandit-Subedi <abhishekpandit@...omium.org>,
Benson Leung <bleung@...omium.org>,
Jameson Thies <jthies@...gle.com>,
Tzung-Bi Shih <tzungbi@...nel.org>,
linux-usb@...r.kernel.org,
chrome-platform@...ts.linux.dev
Cc: Guenter Roeck <groeck@...omium.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
"Christian A. Ehrhardt" <lk@...e.de>,
Abel Vesa <abel.vesa@...aro.org>,
Pooja Katiyar <pooja.katiyar@...el.com>,
Pavan Holla <pholla@...omium.org>,
Madhu M <madhu.m@...el.com>,
Venkat Jayaraman <venkat.jayaraman@...el.com>,
linux-kernel@...r.kernel.org,
Andrei Kuchynski <akuchynski@...omium.org>
Subject: [PATCH RFC 0/8] USB Type-C alternate mode selection
This patch series introduces functionality to the USB Type-C Alternate Mode
negotiation process by implementing a priority-based selection mechanism.
Currently, DisplayPort and Thunderbolt drivers initiate a mode entry
separately within their respective probe functions. The Power Delivery
Controller (PDC) retains the ability to activate either USB4 mode or
Alternate Modes based on its internal policy.
The mode selection mechanism disables Alternate Modes to be entered by
their respective drivers and the PDC. Instead, a priority-ordered approach
is used to activate the most desirable mode.
A new `priority` field is added to the `typec_altmode` structure to store
a numerical priority value, with all priorities being unique.
If the port driver supports the mode selection feature, it must set the
`mode_selection` boolean field within the `typec_altmode` structure. This
indicates to the alternate mode drivers that they are not to activate the
altmode separately.
The mode selection process is managed by three API functions:
- `typec_mode_selection_start`
- `typec_altmode_state_update`
- `typec_mode_selection_delete`
When a partner device is connected, the `typec_mode_selection_start`
function executes the following steps:
- It compiles a priority-ordered list of Alternate Modes that are mutually
supported by both the port and the partner.
- A dedicated mode selection task is subsequently initiated on the Work
Queue.
- This task attempts to activate a mode by starting with the
highest-priority altmode on the list. Alternate modes are identified with
their SVIDs. Activation/Deactivation performed via `activate` typec_altmode
operation. The process stops as soon as a mode is successfully entered.
Otherwise, after a timeout or if an error occurs, the next alternative mode
will be activated.
The `typec_altmode_state_update` function is invoked by the port driver to
communicate the current mode of the Type-C connector.
The `typec_mode_selection_delete` function is responsible for stopping the
currently running mode selection process and releasing all associated
system resources.
USB4 activation can be handled in two distinct ways:
- Treated like an Alternate Mode, using associated sysfs attributes -
`activate` port attribute to enable/disable the mode, `activate` partner
attribute to activate/deactivate the mode, `priority` to keep modes
priority.
- Like a separate USB mode representing in sysfs via `usb_capabily` ports
attribute to enable the mode on the port and `usb_mode` partner attribute
to activate the mode. In this scenario, USB4 is the highest-priority mode,
without the need for a separate priority field. It is put on the top of the
preferred list if it is supported by the partner (partner->usb_capability
has USB_CAPABILITY_USB4 bit set) and is supported and enabled on the port
(port->usb_mode is USB_MODE_USB4).
This patch series implements the second approach. It identifies the USB4
mode via its SVID 0xFF00. Instead of using the typec_altmode_ops activate()
function, activation is handled via the typec_operations enter_usb_mode()
function.
Mode selection is initiated only once during partner registration, and only
if the port driver provides support for this feature. Subsequent
mode-switching activities can be managed via existing sysfs entries. Any
modifications to altmode priorities are relevant only to future
connections.
This series was tested on an Android OS device with kernel 6.17, PDC:
TI TPS6699, Realtek RTS5453.
This series depends on the 'USB Type-C alternate mode priorities' series:
https://lore.kernel.org/all/20251124124639.1101335-1-akuchynski@chromium.org/
Andrei Kuchynski (8):
usb: typec: Implement mode selection
usb: typec: Integrate USB4 into the mode selection process
usb: typec: Introduce mode_selection bit
usb: typec: ucsi: Support mode selection to activate altmodes
usb: typec: ucsi: Enforce mode selection for cros_ec_ucsi
usb: typec: ucsi: Implement enter_usb_mode operation
usb: typec: ucsi: Support for Thunderbolt alt mode
platform/chrome: cros_ec_typec: Enforce priority-based mode selection
drivers/platform/chrome/cros_ec_typec.c | 47 ++-
drivers/platform/chrome/cros_typec_altmode.c | 8 +-
drivers/usb/typec/Makefile | 2 +-
drivers/usb/typec/altmodes/displayport.c | 6 +-
drivers/usb/typec/altmodes/thunderbolt.c | 2 +-
drivers/usb/typec/class.c | 1 +
drivers/usb/typec/class.h | 2 +
drivers/usb/typec/mode_selection.c | 308 +++++++++++++++++++
drivers/usb/typec/ucsi/Makefile | 4 +
drivers/usb/typec/ucsi/cros_ec_ucsi.c | 44 +++
drivers/usb/typec/ucsi/thunderbolt.c | 199 ++++++++++++
drivers/usb/typec/ucsi/ucsi.c | 56 +++-
drivers/usb/typec/ucsi/ucsi.h | 27 ++
include/linux/usb/typec.h | 1 +
include/linux/usb/typec_altmode.h | 43 +++
15 files changed, 728 insertions(+), 22 deletions(-)
create mode 100644 drivers/usb/typec/mode_selection.c
create mode 100644 drivers/usb/typec/ucsi/thunderbolt.c
--
2.52.0.158.g65b55ccf14-goog
Powered by blists - more mailing lists