From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Douglas Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org,
kishon-l0cyMroinI0@public.gmane.org,
johnyoun-HKixBCOQz3hWk0Htik3J/w@public.gmane.org,
balbi-l0cyMroinI0@public.gmane.org,
gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
lyz-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
wulf-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
pawel.moll-5wv7dgnIgG8@public.gmane.org,
ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
gregory.herrero-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
paulz-HKixBCOQz3hWk0Htik3J/w@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [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-F7+t8E8rja9g9hUCZPvPmw@public.gmane.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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
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
>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: heiko@sntech.de, kishon@ti.com, johnyoun@synopsys.com,
balbi@ti.com, gregkh@linuxfoundation.org, lyz@rock-chips.com,
wulf@rock-chips.com, 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: Re: [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: 29+ 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 ` Douglas Anderson
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
2015-10-23 18:28 ` 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 ` Douglas Anderson
2015-10-23 18:28 ` 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 ` Douglas Anderson
2015-10-23 18:28 ` 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 12:26 ` Heiko Stübner
2015-10-24 12:26 ` Heiko Stübner
2015-10-24 15:10 ` Rob Herring [this message]
2015-10-24 15:10 ` Rob Herring
2015-10-24 15:10 ` Rob Herring
[not found] ` <562B9F5F.1080800-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-10-24 21:22 ` Doug Anderson
2015-10-24 21:22 ` Doug Anderson
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
2015-10-26 23:05 ` Rob Herring
2015-10-26 23:05 ` Rob Herring
[not found] ` <CAL_JsqLtYrzvreV68V5S0wFJNAR6JusnqZrLjsJwT6yXgrQKHg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-26 23:49 ` Doug Anderson
2015-10-26 23:49 ` Doug Anderson
2015-10-26 23:49 ` Doug Anderson
[not found] ` <CAD=FV=UfdEN4MzAwZLWDTQ4qMakhchpr063U1e3uk6R96wScJw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-27 1:43 ` Doug Anderson
2015-10-27 1:43 ` 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-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=gregory.herrero-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=johnyoun-HKixBCOQz3hWk0Htik3J/w@public.gmane.org \
--cc=kishon-l0cyMroinI0@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lyz-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=paulz-HKixBCOQz3hWk0Htik3J/w@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=wulf-TNX95d0MmH7DzftRWevZcw@public.gmane.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 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.