From: cy_huang <u0084500@gmail.com>
To: gregkh@linuxfoundation.org, robh+dt@kernel.org,
matthias.bgg@gmail.com, linux@roeck-us.net,
heikki.krogerus@linux.intel.com
Cc: cy_huang@richtek.com, gene_chen@richtek.com,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 3/3] usb typec: mt6360: Prevent the race condition during module remove
Date: Thu, 27 Aug 2020 11:25:32 +0800 [thread overview]
Message-ID: <1598498732-25194-3-git-send-email-u0084500@gmail.com> (raw)
In-Reply-To: <1598498732-25194-1-git-send-email-u0084500@gmail.com>
From: ChiYuan Huang <cy_huang@richtek.com>
Prevent the race condition from interrupt and tcpci port unregister
during module remove.
Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
---
drivers/usb/typec/tcpm/tcpci_mt6360.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/typec/tcpm/tcpci_mt6360.c b/drivers/usb/typec/tcpm/tcpci_mt6360.c
index 6a28193..a381b5d 100644
--- a/drivers/usb/typec/tcpm/tcpci_mt6360.c
+++ b/drivers/usb/typec/tcpm/tcpci_mt6360.c
@@ -164,6 +164,7 @@ static int mt6360_tcpc_remove(struct platform_device *pdev)
{
struct mt6360_tcpc_info *mti = platform_get_drvdata(pdev);
+ disable_irq(mti->irq);
tcpci_unregister_port(mti->tcpci);
return 0;
}
--
2.7.4
next prev parent reply other threads:[~2020-08-27 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 3:25 [PATCH v2 1/3] usb typec: mt6360: Add support for mt6360 Type-C driver cy_huang
2020-08-27 3:25 ` [PATCH v2 2/3] usb typec: mt6360: Add MT6360 Type-C DT binding documentation cy_huang
2020-08-27 3:25 ` cy_huang [this message]
2020-08-27 3:34 ` [PATCH v2 3/3] usb typec: mt6360: Prevent the race condition during module remove Guenter Roeck
2020-08-27 4:53 ` 啟原黃
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=1598498732-25194-3-git-send-email-u0084500@gmail.com \
--to=u0084500@gmail.com \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=gene_chen@richtek.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).