From: "Angus Ainslie (Purism)" <angus@akkea.ca>
To: angus.ainslie@puri.sm
Cc: Guenter Roeck <linux@roeck-us.net>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
"Angus Ainslie (Purism)" <angus@akkea.ca>
Subject: [PATCH v2 1/1] usb: typec: tcpci: Clear the fault status register
Date: Tue, 7 May 2019 18:27:49 -0600 [thread overview]
Message-ID: <20190508002749.14816-2-angus@akkea.ca> (raw)
In-Reply-To: <20190508002749.14816-1-angus@akkea.ca>
If the fault status register doesn't get cleared then
the ptn5110 interrupt gets stuck on. As the fault register gets
set everytime the ptn5110 powers on the interrupt is always stuck.
Fixes: fault status register stuck
Signed-off-by: Angus Ainslie (Purism) <angus@akkea.ca>
---
drivers/usb/typec/tcpm/tcpci.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/drivers/usb/typec/tcpm/tcpci.c b/drivers/usb/typec/tcpm/tcpci.c
index c1f7073a56de..a5746657b190 100644
--- a/drivers/usb/typec/tcpm/tcpci.c
+++ b/drivers/usb/typec/tcpm/tcpci.c
@@ -463,6 +463,17 @@ irqreturn_t tcpci_irq(struct tcpci *tcpci)
else if (status & TCPC_ALERT_TX_FAILED)
tcpm_pd_transmit_complete(tcpci->port, TCPC_TX_FAILED);
+ if (status & TCPC_ALERT_FAULT) {
+ u16 fault_status;
+
+ tcpci_read16(tcpci, TCPC_FAULT_STATUS, &fault_status);
+
+ dev_warn(tcpci->dev, "FAULT ALERT status 0x%x\n", fault_status);
+
+ /* clear the fault status */
+ tcpci_write16(tcpci, TCPC_FAULT_STATUS, fault_status);
+ }
+
return IRQ_HANDLED;
}
EXPORT_SYMBOL_GPL(tcpci_irq);
--
2.17.1
next prev parent reply other threads:[~2019-05-08 0:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 0:27 [PATCH v2 0/1] usb: typec: tcpm: Add some FAULT_STATUS processing Angus Ainslie (Purism)
2019-05-08 0:27 ` Angus Ainslie (Purism) [this message]
2019-05-08 0:49 ` [PATCH v2 1/1] usb: typec: tcpci: Clear the fault status register Guenter Roeck
2019-05-08 6:37 ` Greg Kroah-Hartman
2019-05-08 2:03 ` Guenter Roeck
2019-05-08 2:49 ` Angus Ainslie
2019-05-08 5:18 ` Guenter Roeck
2019-05-08 13:48 ` Angus Ainslie
2019-05-08 16:22 ` Guenter Roeck
2019-05-08 16:33 ` Angus Ainslie
2019-05-08 16:51 ` 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=20190508002749.14816-2-angus@akkea.ca \
--to=angus@akkea.ca \
--cc=angus.ainslie@puri.sm \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.