From: Matthias Kaehlcke <mka@chromium.org>
To: Sandeep Maheswaram <sanm@codeaurora.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <balbi@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Doug Anderson <dianders@chromium.org>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
Manu Gautam <mgautam@codeaurora.org>
Subject: Re: [PATCH v6 2/5] usb: dwc3: core: Host wake up support from system suspend
Date: Mon, 19 Apr 2021 16:16:35 -0700 [thread overview]
Message-ID: <YH4PU6O+dlnF1y35@google.com> (raw)
In-Reply-To: <1618567313-25373-3-git-send-email-sanm@codeaurora.org>
On Fri, Apr 16, 2021 at 03:31:50PM +0530, Sandeep Maheswaram wrote:
> Avoiding phy powerdown when wakeup capable devices are connected
> by checking phy_power_off flag.
> Phy should be on to wake up the device from suspend using wakeup capable
> devices such as keyboard and mouse.
>
> Signed-off-by: Sandeep Maheswaram <sanm@codeaurora.org>
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
next prev parent reply other threads:[~2021-04-19 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 10:01 [PATCH v6 0/5] USB DWC3 host wake up support from system suspend Sandeep Maheswaram
2021-04-16 10:01 ` [PATCH v6 1/5] usb: dwc3: host: Add suspend_quirk for dwc3 host Sandeep Maheswaram
2021-04-19 20:53 ` Matthias Kaehlcke
2021-04-16 10:01 ` [PATCH v6 2/5] usb: dwc3: core: Host wake up support from system suspend Sandeep Maheswaram
2021-04-19 23:16 ` Matthias Kaehlcke [this message]
2021-04-16 10:01 ` [PATCH v6 3/5] usb: dwc3: qcom: Add helper functions to enable,disable wake irqs Sandeep Maheswaram
2021-04-19 19:37 ` Matthias Kaehlcke
2021-04-16 10:01 ` [PATCH v6 4/5] usb: dwc3: qcom: Configure wakeup interrupts during suspend Sandeep Maheswaram
2021-04-19 23:22 ` Matthias Kaehlcke
2021-04-16 10:01 ` [PATCH v6 5/5] usb: dwc3: qcom: Set genpd active wakeup flag for usb gdsc Sandeep Maheswaram
2021-04-20 0:12 ` Matthias Kaehlcke
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=YH4PU6O+dlnF1y35@google.com \
--to=mka@chromium.org \
--cc=agross@kernel.org \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgautam@codeaurora.org \
--cc=sanm@codeaurora.org \
--cc=swboyd@chromium.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).