Linux USB
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Peter Chen" <peter.chen@oss.qualcomm.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH 1/1] usb: dwc3: qcom: Keep wakeup option default off
Date: Tue, 10 Nov 2026 09:35:09 +0000	[thread overview]
Message-ID: <sashiko-outbox-206768@kernel.org> (raw)
In-Reply-To: <20261110092157.2989350-2-peter.chen@oss.qualcomm.com>

> 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. Users who do
> not want USB activity (e.g. connect/disconnect) to wake up the system
> have to disable it through power/wakeup, otherwise unexpected wakeups
> may happen.
> 
> Having wakeup enabled by default also costs power. In host mode, system
> suspend skips dwc3_core_exit() and keeps the PHYs and the wakeup
> detection logic powered so that the wakeup interrupts can fire, even on
> systems where USB is never used as a wakeup source and the controller
> could be fully powered off.
> 
> Keep the wakeup option default off and only mark the device as wakeup
> capable, so that the user decides which USB controller 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.
> 
> Signed-off-by: Peter Chen <peter.chen@oss.qualcomm.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261110092157.2989350-1-peter.chen@oss.qualcomm.com?part=1


  reply	other threads:[~2026-11-10  9:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10  9:21 [PATCH 0/1] usb: dwc3: qcom: Keep wakeup option default off Peter Chen
2026-11-10  9:21 ` [PATCH 1/1] " Peter Chen
2026-11-10  9:35   ` sashiko-bot [this message]
2026-11-12  1:14 ` [PATCH 0/1] " Thinh Nguyen
2026-11-12  8:10   ` Peter Chen

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=sashiko-outbox-206768@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter.chen@oss.qualcomm.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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