From: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
To: Peter Chen <peter.chen@oss.qualcomm.com>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
cros-qcom-dts-watchers@chromium.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johan Hovold <johan@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Wesley Cheng <wesley.cheng@oss.qualcomm.com>,
Udipto Goswami <udipto.goswami@oss.qualcomm.com>,
Jack Pham <jack.pham@oss.qualcomm.com>,
Pratham Pratap <pratham.pratap@oss.qualcomm.com>,
Prashanth K <prashanth.k@oss.qualcomm.com>,
Elson Serrao <elson.serrao@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] usb: dwc3: qcom: Keep wakeup option default off
Date: Wed, 4 Nov 2026 19:27:32 +0530 [thread overview]
Message-ID: <59c79112-0079-42b0-b6c2-d311f20e0dd2@oss.qualcomm.com> (raw)
In-Reply-To: <20261103061401.2942139-2-peter.chen@oss.qualcomm.com>
On 11/3/2026 11:44 AM, Peter Chen wrote:
> The "wakeup-source" property, as described in
> Documentation/devicetree/bindings/power/wakeup-source.txt, only says
> that a device is capable of waking up the system. Whether wakeup is
> actually enabled is a policy decision, and drivers use
> device_may_wakeup() to decide whether to arm the hardware wakeup logic.
>
> Currently dwc3-qcom calls device_init_wakeup(dev, true) when the
> property is present, so USB wakeup is enabled by default and users who
> do not want USB activity (e.g. connect/disconnect) to wake up the system
> may have to disable it through power/wakeup, otherwise, unexpected wakeup
> may happen.
>
> Having wakeup enabled by default also costs power. In host mode,
> when device_may_wakeup() is true, system suspend keeps the controller
> and PHYs powered (dwc3_core_exit() is skipped and the genpd is not
> powered off) so that the wakeup interrupts can fire, even on systems
> where USB is never used as a wakeup source and could be fully powered
> off.
>
> For USB controllers, keep the wakeup option default off and only mark
> the device as wakeup capable, so that the user decides which USB port
> is used as a system wakeup source. Users who need it can enable it with:
>
> echo enabled > /sys/devices/.../<dwc3 device>/power/wakeup
>
> While at it, drop the local wakeup_source variable and use
> device_property_read_bool() like the other property reads in probe.
>
++cros-qcom-dts-watchers since this is used in chromium userspace and
modifications might be needed there as well.
Regards,
Krishna,
> Signed-off-by: Peter Chen <peter.chen@oss.qualcomm.com>
> ---
> drivers/usb/dwc3/dwc3-qcom.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/usb/dwc3/dwc3-qcom.c b/drivers/usb/dwc3/dwc3-qcom.c
> index 8116dc94c181..1451b5eaccce 100644
> --- a/drivers/usb/dwc3/dwc3-qcom.c
> +++ b/drivers/usb/dwc3/dwc3-qcom.c
> @@ -653,7 +653,6 @@ static int dwc3_qcom_probe(struct platform_device *pdev)
> struct resource *r;
> int ret;
> bool ignore_pipe_clk;
> - bool wakeup_source;
>
> qcom = devm_kzalloc(&pdev->dev, sizeof(*qcom), GFP_KERNEL);
> if (!qcom)
> @@ -757,8 +756,8 @@ static int dwc3_qcom_probe(struct platform_device *pdev)
> if (ret)
> goto remove_core;
>
> - wakeup_source = of_property_read_bool(dev->of_node, "wakeup-source");
> - device_init_wakeup(&pdev->dev, wakeup_source);
> + if (device_property_read_bool(dev, "wakeup-source"))
> + device_set_wakeup_capable(dev, true);
>
> qcom->is_suspended = false;
>
prev parent reply other threads:[~2026-11-04 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 6:14 [RFC PATCH 0/1] " Peter Chen
2026-11-03 6:14 ` [RFC PATCH 1/1] " Peter Chen
2026-11-04 13:57 ` Krishna Kurapati [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=59c79112-0079-42b0-b6c2-d311f20e0dd2@oss.qualcomm.com \
--to=krishna.kurapati@oss.qualcomm.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=andersson@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=elson.serrao@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack.pham@oss.qualcomm.com \
--cc=johan@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@oss.qualcomm.com \
--cc=prashanth.k@oss.qualcomm.com \
--cc=pratham.pratap@oss.qualcomm.com \
--cc=udipto.goswami@oss.qualcomm.com \
--cc=wesley.cheng@oss.qualcomm.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
all inboxes | Powered by JetHome®