From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Patches to fix remote wakeup on rk3288 dwc2 "host" port
Date: Sat, 24 Oct 2015 10:10:23 -0500 [thread overview]
Message-ID: <562B9F5F.1080800@kernel.org> (raw)
In-Reply-To: <1445624891-31680-1-git-send-email-dianders@chromium.org>
On 10/23/2015 01:28 PM, Douglas Anderson wrote:
> 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(+)
A DT reset controller seems like a bit of an overkill here. I think this
would be much more simple if we just add a phy reset hook to the phy
subsystem.
Rob
>
next prev parent reply other threads:[~2015-10-24 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 18:28 [PATCH 0/4] Patches to fix remote wakeup on rk3288 dwc2 "host" port Douglas Anderson
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-23 18:28 ` [PATCH 4/4] ARM: dts: rockchip: Point rk3288 dwc2 usb at phy port reset 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 [this message]
2015-10-24 21:22 ` Doug Anderson
2015-10-26 23:05 ` Rob Herring
2015-10-26 23:49 ` Doug Anderson
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=562B9F5F.1080800@kernel.org \
--to=robh@kernel.org \
--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).