From: Rajmohan Mani <rajmohan.mani@intel.com>
To: Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
linux-kernel@vger.kernel.org
Cc: heikki.krogerus@linux.intel.com, pmalani@chromium.org,
Rajmohan Mani <rajmohan.mani@intel.com>
Subject: [PATCH 0/2] Add support for Type-C mux events without port partners
Date: Fri, 5 Feb 2021 11:51:11 -0800 [thread overview]
Message-ID: <20210205195113.20277-1-rajmohan.mani@intel.com> (raw)
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
next reply other threads:[~2021-02-05 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 19:51 Rajmohan Mani [this message]
2021-02-05 19:51 ` [PATCH 1/2] platform/chrome: cros_ec_typec: Skip port partner check in configure_mux() Rajmohan Mani
2021-02-05 20:07 ` Prashant Malani
2021-02-05 22:56 ` Mani, Rajmohan
2021-02-05 19:51 ` [PATCH 2/2] platform/chrome: cros_ec_types: Support disconnect events without partners Rajmohan Mani
2021-02-05 20:05 ` Prashant Malani
2021-02-05 20:06 ` Prashant Malani
2021-02-06 0:59 ` [PATCH 0/2] Add support for Type-C mux events without port partners Benson Leung
2021-02-06 1:26 ` Mani, Rajmohan
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=20210205195113.20277-1-rajmohan.mani@intel.com \
--to=rajmohan.mani@intel.com \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.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®