There are cases, where support for Type-C mux events is needed, that
does not have port partners.
Enabling communication to a retimer connected to an USB4 port, when
no devices are attached, is a case that requires support for handling
Type-C mux events without port partners.

The following patches[1] are needed on top of the mainline kernel to be
able to verify these patches.

commit 8553a979fcd0 ("platform/chrome: cros_ec_typec: Send mux
                      configuration acknowledgment to EC")
commit ba8ce515454e ("platform/chrome: cros_ec_typec: Parameterize
                      cros_typec_cmds_supported()")
commit 156309096542 ("platform/chrome: cros_ec_typec: Register plug
                      altmodes")
commit f4edab68e101 ("platform/chrome: cros_ec_typec: Register SOP'
                      cable plug")
commit 599229763911 ("platform/chrome: cros_ec_typec: Set partner
                      num_altmodes")
commit 72d6e32bd85b ("platform/chrome: cros_ec_typec: Store cable plug
                      type")
commit 8b46a212ad11 ("platform/chrome: cros_ec_typec: Register cable")
commit c097f229b71e ("platform/chrome: cros_ec_typec: Rename discovery
                      struct")
commit 8fab2755191f ("platform/chrome: cros_ec_typec: Factor out PD
                      identity parsing")
commit a906f45d1480 ("platform/chrome: cros_ec_typec: Make disc_done
                      flag partner-only")

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/
linux.git/log/?h=cros-ec-typec-for-5.12

Rajmohan Mani (2):
  platform/chrome: cros_ec_typec: Skip port partner check in
    configure_mux()
  platform/chrome: cros_ec_types: Support disconnect events without
    partners

 drivers/platform/chrome/cros_ec_typec.c | 27 ++++++++++++++++---------
 1 file changed, 18 insertions(+), 9 deletions(-)

-- 
2.30.0

Reply via email to