From: RD Babiera <rdbabiera@google.com>
To: linux@roeck-us.net, heikki.krogerus@linux.intel.com,
gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
badhri@google.com, RD Babiera <rdbabiera@google.com>
Subject: [PATCH v1 0/2] usb: typec: handle tcpc vconn oc fault by triggering tcpm error recovery
Date: Tue, 21 Nov 2023 20:38:46 +0000 [thread overview]
Message-ID: <20231121203845.170234-4-rdbabiera@google.com> (raw)
When a Vconn swap results in a Vconn over current fault, typec port
interoperability is affected and cannot be recovered unless the connection
is reset and restablished.
The tcpm currently does not have an export symbol to set the port to the
error recovery state in the event of tcpc faults. This patch set adds
tcpm_port_error_recovery for tcpci drivers to use when a fault should
result in a connection reset. Vconn over current fault handling is added
to the maxim tcpci driver.
RD Babiera (2):
usb: typec: tcpm: add tcpm_port_error_recovery symbol
usb: typec: tcpci: add vconn over current fault handling to maxim_core
drivers/usb/typec/tcpm/tcpci_maxim_core.c | 20 +++++++++++++++++++-
drivers/usb/typec/tcpm/tcpm.c | 14 ++++++++++++++
include/linux/usb/tcpci.h | 5 ++++-
include/linux/usb/tcpm.h | 1 +
4 files changed, 38 insertions(+), 2 deletions(-)
--
2.43.0.rc1.413.gea7ed67945-goog
next reply other threads:[~2023-11-21 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 20:38 RD Babiera [this message]
2023-11-21 20:38 ` [PATCH v1 1/2] usb: typec: tcpm: add tcpm_port_error_recovery symbol RD Babiera
2023-11-28 7:57 ` Heikki Krogerus
2023-11-28 15:10 ` Guenter Roeck
2023-11-21 20:38 ` [PATCH v1 2/2] usb: typec: tcpci: add vconn over current fault handling to maxim_core RD Babiera
2023-11-28 7:59 ` Heikki Krogerus
2023-11-28 15:11 ` Guenter Roeck
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=20231121203845.170234-4-rdbabiera@google.com \
--to=rdbabiera@google.com \
--cc=badhri@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
/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®