From: Douglas Anderson <dianders@chromium.org>
To: Minas Harutyunyan <hminas@synopsys.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
heiko@sntech.de
Cc: Alan Stern <stern@rowland.harvard.edu>,
Artur Petrosyan <Arthur.Petrosyan@synopsys.com>,
amstan@chromium.org, linux-rockchip@lists.infradead.org,
William Wu <william.wu@rock-chips.com>,
linux-usb@vger.kernel.org, Stefan Wahren <stefan.wahren@i2se.com>,
Randy Li <ayaka@soulik.info>,
zyw@rock-chips.com, mka@chromium.org, ryandcase@chromium.org,
Amelie Delaunay <amelie.delaunay@st.com>,
jwerner@chromium.org, Elaine Zhang <zhangqing@rock-chips.com>,
Douglas Anderson <dianders@chromium.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] USB: dwc2: Allow wakeup from suspend; enable for rk3288-veyron
Date: Mon, 20 May 2019 10:56:02 -0700 [thread overview]
Message-ID: <20190520175605.2405-1-dianders@chromium.org> (raw)
This is a re-post of the last 3 patches of a series I posted earlier
at:
https://lkml.kernel.org/r/20190418001356.124334-1-dianders@chromium.org
The first two patches were applied but the last three weren't because
they didn't apply at the time. They apply fine now so are ready to
land.
Patch #2 has a slight difference in v3 here to fix build robot
reported error.
Changes in v3:
- Fixed kbuild test robot error.
Changes in v2:
- Rebased to mainline atop rk3288 remote wake quirk series.
- rk3288-veyron dts patch new for v2.
Douglas Anderson (3):
Documentation: dt-bindings: Add snps,need-phy-for-wake for dwc2 USB
USB: dwc2: Don't turn off the usbphy in suspend if wakeup is enabled
ARM: dts: rockchip: Allow wakeup from rk3288-veyron's dwc2 USB ports
.../devicetree/bindings/usb/dwc2.txt | 3 +++
arch/arm/boot/dts/rk3288-veyron.dtsi | 2 ++
drivers/usb/dwc2/core.h | 8 +++++++
drivers/usb/dwc2/hcd.c | 19 +++++++++++++++
drivers/usb/dwc2/platform.c | 23 ++++++++++++++++---
5 files changed, 52 insertions(+), 3 deletions(-)
--
2.21.0.1020.gf2820cf01a-goog
next reply other threads:[~2019-05-20 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 17:56 Douglas Anderson [this message]
2019-05-20 17:56 ` [PATCH v3 1/3] Documentation: dt-bindings: Add snps,need-phy-for-wake for dwc2 USB Douglas Anderson
2019-06-13 23:06 ` Rob Herring
2019-05-20 17:56 ` [PATCH v3 2/3] USB: dwc2: Don't turn off the usbphy in suspend if wakeup is enabled Douglas Anderson
2019-05-20 17:56 ` [PATCH v3 3/3] ARM: dts: rockchip: Allow wakeup from rk3288-veyron's dwc2 USB ports Douglas 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=20190520175605.2405-1-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=Arthur.Petrosyan@synopsys.com \
--cc=amelie.delaunay@st.com \
--cc=amstan@chromium.org \
--cc=ayaka@soulik.info \
--cc=devicetree@vger.kernel.org \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=hminas@synopsys.com \
--cc=jwerner@chromium.org \
--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=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.org \
--cc=ryandcase@chromium.org \
--cc=stefan.wahren@i2se.com \
--cc=stern@rowland.harvard.edu \
--cc=william.wu@rock-chips.com \
--cc=zhangqing@rock-chips.com \
--cc=zyw@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).