From: Robert Hancock <robert.hancock@calian.com>
To: linux-usb@vger.kernel.org
Cc: balbi@kernel.org, gregkh@linuxfoundation.org,
michal.simek@xilinx.com, manish.narani@xilinx.com,
sean.anderson@seco.com, robh+dt@kernel.org,
devicetree@vger.kernel.org, piyush.mehta@xilinx.com,
Robert Hancock <robert.hancock@calian.com>
Subject: [PATCH v7 4/4] usb: dwc3: xilinx: Add ULPI PHY reset handling
Date: Tue, 25 Jan 2022 18:02:53 -0600 [thread overview]
Message-ID: <20220126000253.1586760-5-robert.hancock@calian.com> (raw)
In-Reply-To: <20220126000253.1586760-1-robert.hancock@calian.com>
Hook up an optional GPIO-based reset for the connected USB ULPI PHY
device. This is typically already done by the first-stage boot loader,
however it can be more robust to ensure this reset is done prior to
loading the driver in Linux.
Based on a patch "usb: dwc3: xilinx: Add gpio-reset support" in the
Xilinx kernel tree by Piyush Mehta <piyush.mehta@xilinx.com>.
Signed-off-by: Robert Hancock <robert.hancock@calian.com>
---
drivers/usb/dwc3/dwc3-xilinx.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/drivers/usb/dwc3/dwc3-xilinx.c b/drivers/usb/dwc3/dwc3-xilinx.c
index e14ac15e24c3..0778236509bf 100644
--- a/drivers/usb/dwc3/dwc3-xilinx.c
+++ b/drivers/usb/dwc3/dwc3-xilinx.c
@@ -11,6 +11,7 @@
#include <linux/slab.h>
#include <linux/clk.h>
#include <linux/of.h>
+#include <linux/gpio/consumer.h>
#include <linux/platform_device.h>
#include <linux/dma-mapping.h>
#include <linux/of_platform.h>
@@ -101,6 +102,7 @@ static int dwc3_xlnx_init_zynqmp(struct dwc3_xlnx *priv_data)
struct phy *usb3_phy;
int ret;
u32 reg;
+ struct gpio_desc *reset_gpio;
usb3_phy = devm_phy_optional_get(dev, "usb3-phy");
if (IS_ERR(usb3_phy)) {
@@ -201,6 +203,22 @@ static int dwc3_xlnx_init_zynqmp(struct dwc3_xlnx *priv_data)
}
skip_usb3_phy:
+ /* ulpi reset via gpio-modepin or gpio-framework driver */
+ reset_gpio = devm_gpiod_get_optional(dev, "reset", GPIOD_OUT_HIGH);
+ if (IS_ERR(reset_gpio)) {
+ dev_err_probe(dev, PTR_ERR(reset_gpio),
+ "Failed to bind reset gpio\n");
+ goto err;
+ }
+
+ if (reset_gpio) {
+ /* Toggle ulpi to reset the phy. */
+ gpiod_set_value(reset_gpio, 0);
+ usleep_range(5000, 10000); /* delay */
+ gpiod_set_value(reset_gpio, 1);
+ usleep_range(5000, 10000); /* delay */
+ }
+
/*
* This routes the USB DMA traffic to go through FPD path instead
* of reaching DDR directly. This traffic routing is needed to
--
2.31.1
next prev parent reply other threads:[~2022-01-26 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 0:02 [PATCH v7 0/4] Xilinx ZynqMP USB fixes Robert Hancock
2022-01-26 0:02 ` [PATCH v7 1/4] usb: dwc3: xilinx: Skip resets and USB3 register settings for USB2.0 mode Robert Hancock
2022-01-26 0:02 ` [PATCH v7 2/4] usb: dwc3: xilinx: Fix error handling when getting USB3 PHY Robert Hancock
2022-01-26 0:02 ` [PATCH v7 3/4] dt-bindings: usb: dwc3-xilinx: Added reset-gpios Robert Hancock
2022-01-26 0:02 ` Robert Hancock [this message]
2022-01-26 23:01 ` [PATCH v7 4/4] usb: dwc3: xilinx: Add ULPI PHY reset handling Robert Hancock
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=20220126000253.1586760-5-robert.hancock@calian.com \
--to=robert.hancock@calian.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=manish.narani@xilinx.com \
--cc=michal.simek@xilinx.com \
--cc=piyush.mehta@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=sean.anderson@seco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox