From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/5] arm64: dts: rockchip: add reset property for dwc3 controllers on rk3399.
Date: Sat, 16 Dec 2017 18:01:08 +0100 [thread overview]
Message-ID: <2260405.eszS2niqFZ@phil> (raw)
In-Reply-To: <20171215110005.7564-5-enric.balletbo@collabora.com>
Am Freitag, 15. Dezember 2017, 12:00:05 CET schrieb Enric Balletbo i Serra:
> After commit '06c47e6286d usb: dwc3: of-simple: Add support to get resets
> for the device' you can add the reset property to the dwc3 node, the reset
> is required for the controller to work properly, otherwise bind / unbind
> stress testing of the USB controller on rk3399 we'd often end up with lots
> of failures that looked like this:
>
> phy phy-ff800000.phy.9: phy poweron failed --> -110
> dwc3 fe900000.dwc3: failed to initialize core
> dwc3: probe of fe900000.dwc3 failed with error -110
>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
applied for 4.16
Thanks
Heiko
next prev parent reply other threads:[~2017-12-16 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 11:00 [PATCH v3 1/5] arm64: dts: rockchip: add extcon nodes and enable tcphy Enric Balletbo i Serra
2017-12-15 11:00 ` [PATCH v3 2/5] arm64: dts: rockchip: add the aclk_usb3 clocks for USB3 Enric Balletbo i Serra
2017-12-16 17:00 ` Heiko Stuebner
2017-12-15 11:00 ` [PATCH v3 3/5] arm64: dts: rockchip: add usb3-phy otg-port support for rk3399 Enric Balletbo i Serra
2017-12-16 17:06 ` Heiko Stuebner
2018-03-02 7:43 ` Heiko Stuebner
2017-12-15 11:00 ` [PATCH v3 4/5] arm64: dts: rockchip: add pd_usb3 power-domain node " Enric Balletbo i Serra
2017-12-16 16:55 ` Heiko Stuebner
2017-12-15 11:00 ` [PATCH v3 5/5] arm64: dts: rockchip: add reset property for dwc3 controllers on rk3399 Enric Balletbo i Serra
2017-12-16 17:01 ` Heiko Stuebner [this message]
2017-12-16 17:08 ` [PATCH v3 1/5] arm64: dts: rockchip: add extcon nodes and enable tcphy Heiko Stuebner
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=2260405.eszS2niqFZ@phil \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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).