From: Douglas Anderson <dianders@chromium.org>
To: heiko@sntech.de, kishon@ti.com, johnyoun@synopsys.com, balbi@ti.com
Cc: gregkh@linuxfoundation.org, lyz@rock-chips.com,
wulf@rock-chips.com, Douglas Anderson <dianders@chromium.org>,
mark.rutland@arm.com, devicetree@vger.kernel.org,
linux@arm.linux.org.uk, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh+dt@kernel.org, galak@codeaurora.org,
gregory.herrero@intel.com, paulz@synopsys.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Patches to fix remote wakeup on rk3288 dwc2 "host" port
Date: Fri, 23 Oct 2015 11:28:07 -0700 [thread overview]
Message-ID: <1445624891-31680-1-git-send-email-dianders@chromium.org> (raw)
The "host1" port (AKA the dwc2 port that isn't the OTG port) on rk3288
has a hardware errata that causes everything to get confused when we get
a remote wakeup. It appears that the "port reset" bit that's in the USB
phy (located in the rk3288 GRF) fixes things up and appears safe to do.
This series of patches exports the "port reset" from the PHY and then
hooks it up to dwc2 through a quirk.
I've tested this series atop a bit of a conglomeration of Heiko's github
"somewhat stable" branch (v4.3-rc3-876-g6509232) but with Greg KH's
usb-next merged in.
These patches currently conflict with patches that I posted previously
to enable USB wakeup from S3, specifically:
* https://patchwork.kernel.org/patch/6727081/
* https://patchwork.kernel.org/patch/6727121/
...those patches no longer apply anyway, so presumably they need to be
reposted and I can do so later atop these patches.
Douglas Anderson (4):
phy: rockchip-usb: Support the PHY's "port reset"
usb: dwc2: optionally assert phy "port reset" when waking up
ARM: dts: rockchip: Enable the USB phys as reset providers on rk3288
ARM: dts: rockchip: Point rk3288 dwc2 usb at phy port reset
.../devicetree/bindings/phy/rockchip-usb-phy.txt | 6 ++
Documentation/devicetree/bindings/usb/dwc2.txt | 7 ++
arch/arm/boot/dts/rk3288.dtsi | 8 +++
drivers/phy/phy-rockchip-usb.c | 74 ++++++++++++++++++++++
drivers/usb/dwc2/core.h | 5 ++
drivers/usb/dwc2/core_intr.c | 7 ++
drivers/usb/dwc2/platform.c | 13 ++++
7 files changed, 120 insertions(+)
--
2.6.0.rc2.230.g3dd15c0
next reply other threads:[~2015-10-23 18:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 18:28 Douglas Anderson [this message]
2015-10-23 18:28 ` [PATCH 2/4] usb: dwc2: optionally assert phy "port reset" when waking up Douglas Anderson
2015-10-23 18:28 ` [PATCH 4/4] ARM: dts: rockchip: Point rk3288 dwc2 usb at phy port reset Douglas Anderson
[not found] ` <1445624891-31680-1-git-send-email-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2015-10-23 18:28 ` [PATCH 1/4] phy: rockchip-usb: Support the PHY's "port reset" Douglas Anderson
2015-10-23 18:28 ` [PATCH 3/4] ARM: dts: rockchip: Enable the USB phys as reset providers on rk3288 Douglas Anderson
2015-10-24 12:26 ` [PATCH 0/4] Patches to fix remote wakeup on rk3288 dwc2 "host" port Heiko Stübner
2015-10-24 15:10 ` Rob Herring
[not found] ` <562B9F5F.1080800-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-10-24 21:22 ` Doug Anderson
[not found] ` <CAD=FV=VgYU8sZfSkbNbbOFpb-nt=Yy9NjybxADBnAiQXfasDpw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-26 23:05 ` Rob Herring
[not found] ` <CAL_JsqLtYrzvreV68V5S0wFJNAR6JusnqZrLjsJwT6yXgrQKHg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-26 23:49 ` Doug Anderson
[not found] ` <CAD=FV=UfdEN4MzAwZLWDTQ4qMakhchpr063U1e3uk6R96wScJw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-27 1:43 ` Doug Anderson
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=1445624891-31680-1-git-send-email-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.herrero@intel.com \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=johnyoun@synopsys.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lyz@rock-chips.com \
--cc=mark.rutland@arm.com \
--cc=paulz@synopsys.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=wulf@rock-chips.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;
as well as URLs for NNTP newsgroup(s).