From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sandeep Maheswaram <sanm@codeaurora.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Felipe Balbi <balbi@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Doug Anderson <dianders@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Manu Gautam <mgautam@codeaurora.org>
Subject: Re: [PATCH v5 1/4] usb: dwc3: core: Host wake up support from system suspend
Date: Tue, 23 Mar 2021 13:10:23 +0100 [thread overview]
Message-ID: <YFnary7nLGoS7zSn@kroah.com> (raw)
In-Reply-To: <1616434280-32635-2-git-send-email-sanm@codeaurora.org>
On Mon, Mar 22, 2021 at 11:01:17PM +0530, Sandeep Maheswaram wrote:
> Avoiding phy powerdown when wakeup capable devices are connected.
That says "what" (in a very abbreviated way), but not _WHY_ you want to
do this. Please fix this up.
thanks,
greg k-h
next prev parent reply other threads:[~2021-03-23 12:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 17:31 [PATCH v5 0/4] USB DWC3 host wake up support from system suspend Sandeep Maheswaram
2021-03-22 17:31 ` [PATCH v5 1/4] usb: dwc3: core: Host " Sandeep Maheswaram
2021-03-23 12:10 ` Greg Kroah-Hartman [this message]
2021-03-24 0:27 ` Matthias Kaehlcke
2021-03-22 17:31 ` [PATCH v5 2/4] usb: dwc3: host: Add suspend_quirk for dwc3 host Sandeep Maheswaram
2021-03-23 12:09 ` Greg Kroah-Hartman
2021-03-23 12:09 ` Greg Kroah-Hartman
2021-03-24 0:38 ` Matthias Kaehlcke
2021-03-22 17:31 ` [PATCH v5 3/4] usb: dwc3: qcom: Configure wakeup interrupts and set genpd active wakeup flag Sandeep Maheswaram
2021-03-23 12:11 ` Greg Kroah-Hartman
2021-03-24 0:49 ` Matthias Kaehlcke
2021-03-24 0:56 ` Matthias Kaehlcke
2021-03-22 17:31 ` [PATCH v5 4/4] arm64: dts: qcom: sc7180: Add wakeup-source property for USB node in IDP and trogdor Sandeep Maheswaram
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=YFnary7nLGoS7zSn@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=agross@kernel.org \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.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=mka@chromium.org \
--cc=robh+dt@kernel.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 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.