From: Al Cooper <alcooperx@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Danesh Petigara <danesh.petigara@broadcom.com>,
Al Cooper <alcooperx@gmail.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
devicetree@vger.kernel.org, Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Sasi Kumar <sasi.kumar@broadcom.com>
Subject: [PATCH 6/7] usb: bdc: Halt controller on suspend
Date: Fri, 17 Jul 2020 11:23:06 -0400 [thread overview]
Message-ID: <20200717152307.36705-7-alcooperx@gmail.com> (raw)
In-Reply-To: <20200717152307.36705-1-alcooperx@gmail.com>
From: Danesh Petigara <danesh.petigara@broadcom.com>
GISB bus error kernel panics have been observed during S2 transition
tests on the 7271t platform. The errors are a result of the BDC
interrupt handler trying to access BDC register space after the
system's suspend callbacks have completed.
Adding a suspend hook to the BDC driver that halts the controller before
S2 entry thus preventing unwanted access to the BDC register space during
this transition.
Signed-off-by: Danesh Petigara <danesh.petigara@broadcom.com>
Signed-off-by: Al Cooper <alcooperx@gmail.com>
Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com>
---
drivers/usb/gadget/udc/bdc/bdc_core.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/gadget/udc/bdc/bdc_core.c b/drivers/usb/gadget/udc/bdc/bdc_core.c
index 47bcc9f6afbd..ac989adefe9d 100644
--- a/drivers/usb/gadget/udc/bdc/bdc_core.c
+++ b/drivers/usb/gadget/udc/bdc/bdc_core.c
@@ -607,9 +607,14 @@ static int bdc_remove(struct platform_device *pdev)
static int bdc_suspend(struct device *dev)
{
struct bdc *bdc = dev_get_drvdata(dev);
+ int ret;
- clk_disable_unprepare(bdc->clk);
- return 0;
+ /* Halt the controller */
+ ret = bdc_stop(bdc);
+ if (!ret)
+ clk_disable_unprepare(bdc->clk);
+
+ return ret;
}
static int bdc_resume(struct device *dev)
--
2.17.1
next prev parent reply other threads:[~2020-07-17 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 15:23 [PATCH 0/7] usb: bdc: Updates and fixes to the USB BDC driver Al Cooper
2020-07-17 15:23 ` [PATCH 1/7] dt-bindings: usb: bdc: Update compatible strings Al Cooper
2020-07-17 15:23 ` [PATCH 2/7] usb: bdc: Add compatible string for new style USB DT nodes Al Cooper
2020-07-17 16:55 ` Florian Fainelli
2020-07-17 15:23 ` [PATCH 3/7] bdc: Fix bug causing crash after multiple disconnects Al Cooper
2020-07-17 16:56 ` Florian Fainelli
2020-07-17 15:23 ` [PATCH 4/7] usb: bdc: Adb shows offline after resuming from S2 Al Cooper
2020-07-17 15:23 ` [PATCH 5/7] usb: bdc: driver runs out of buffer descriptors on large ADB transfers Al Cooper
2020-07-17 16:58 ` Florian Fainelli
2020-07-17 15:23 ` Al Cooper [this message]
2020-07-17 15:23 ` [PATCH 7/7] usb: bdc: Use devm_clk_get_optional() Al Cooper
2020-07-17 16:57 ` Florian Fainelli
2020-07-21 9:33 ` [PATCH 0/7] usb: bdc: Updates and fixes to the USB BDC driver Felipe Balbi
2020-07-21 13:45 ` Alan Cooper
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=20200717152307.36705-7-alcooperx@gmail.com \
--to=alcooperx@gmail.com \
--cc=balbi@kernel.org \
--cc=danesh.petigara@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sasi.kumar@broadcom.com \
/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.