From: patchwork-bot+linux-arm-msm@kernel.org
To: Sandeep Maheswaram <quic_c_sanm@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v14 0/7] USB DWC3 host wake up support from system suspend
Date: Tue, 19 Apr 2022 20:40:15 +0000 [thread overview]
Message-ID: <165040081515.22799.4337799175831545587.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1650395470-31333-1-git-send-email-quic_c_sanm@quicinc.com>
Hello:
This series was applied to qcom/linux.git (for-next)
by Bjorn Andersson <bjorn.andersson@linaro.org>:
On Wed, 20 Apr 2022 00:41:03 +0530 you wrote:
> Avoiding phy powerdown in host mode when wakeup capable devices are
> connected, so that it can be wake up by devices.
> Keep usb30_prim gdsc active to retain controller status
> during suspend/resume.
>
> Changes in v14:
> Added patch for device_children_wakeup_capable.
> Used device_children_wakeup_capable instead of usb_wakeup_enabled_descendants.
> Fixed minor nit picks in v13 reported by Matthias.
>
> [...]
Here is the summary with links:
- [v14,1/7] dt-bindings: usb: dwc3: Add wakeup-source property support
(no matching commit)
- [v14,2/7] PM / wakeup: Add device_children_wakeup_capable()
(no matching commit)
- [v14,3/7] usb: dwc3: core: Host wake up support from system suspend
(no matching commit)
- [v14,4/7] usb: dwc3: qcom: Add helper functions to enable,disable wake irqs
(no matching commit)
- [v14,5/7] usb: dwc3: qcom: Configure wakeup interrupts during suspend
(no matching commit)
- [v14,6/7] usb: dwc3: qcom: Keep power domain on to retain controller status
(no matching commit)
- [v14,7/7] arm64: dts: qcom: sc7280: Add wakeup-source property for USB node
https://git.kernel.org/qcom/c/97276cbfb4fb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-04-19 20:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 19:11 [PATCH v14 0/7] USB DWC3 host wake up support from system suspend Sandeep Maheswaram
2022-04-19 19:11 ` [PATCH v14 1/7] dt-bindings: usb: dwc3: Add wakeup-source property support Sandeep Maheswaram
2022-04-19 19:11 ` [PATCH v14 2/7] PM / wakeup: Add device_children_wakeup_capable() Sandeep Maheswaram
2022-04-22 11:57 ` Rafael J. Wysocki
2022-04-22 18:44 ` Matthias Kaehlcke
2022-04-25 13:03 ` Pavan Kondeti
2022-04-29 12:59 ` Pavan Kondeti
2022-04-29 19:19 ` Matthias Kaehlcke
2022-04-30 3:11 ` Pavan Kondeti
2022-05-03 0:57 ` Matthias Kaehlcke
2022-04-19 19:11 ` [PATCH v14 3/7] usb: dwc3: core: Host wake up support from system suspend Sandeep Maheswaram
2022-05-04 17:46 ` Matthias Kaehlcke
2022-05-05 3:26 ` Pavan Kondeti
2022-05-05 16:45 ` Matthias Kaehlcke
2022-05-06 3:01 ` Pavan Kondeti
2022-05-06 16:43 ` Matthias Kaehlcke
2022-04-19 19:11 ` [PATCH v14 4/7] usb: dwc3: qcom: Add helper functions to enable,disable wake irqs Sandeep Maheswaram
2022-04-19 19:11 ` [PATCH v14 5/7] usb: dwc3: qcom: Configure wakeup interrupts during suspend Sandeep Maheswaram
2022-04-19 19:11 ` [PATCH v14 6/7] usb: dwc3: qcom: Keep power domain on to retain controller status Sandeep Maheswaram
2022-04-19 19:11 ` [PATCH v14 7/7] arm64: dts: qcom: sc7280: Add wakeup-source property for USB node Sandeep Maheswaram
2022-04-19 20:40 ` patchwork-bot+linux-arm-msm [this message]
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=165040081515.22799.4337799175831545587.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_c_sanm@quicinc.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