From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: John Youn <John.Youn@synopsys.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
John Schoenick <johns@valvesoftware.com>,
Andrey Smirnov <andrew.smirnov@gmail.com>,
Vivek Dasmohapatra <vivek@collabora.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc3: Properly set system wakeup
Date: Fri, 8 Mar 2024 11:34:13 -0300 [thread overview]
Message-ID: <cac3f811-189f-be7f-e5fa-12ee6ca8a62a@igalia.com> (raw)
In-Reply-To: <667cfda7009b502e08462c8fb3f65841d103cc0a.1709865476.git.Thinh.Nguyen@synopsys.com>
On 07/03/2024 23:40, Thinh Nguyen wrote:
> If the device is configured for system wakeup, then make sure that the
> xHCI driver knows about it and make sure to permit wakeup only at the
> appropriate time.
>
> For host mode, if the controller goes through the dwc3 code path, then a
> child xHCI platform device is created. Make sure the platform device
> also inherits the wakeup setting for xHCI to enable remote wakeup.
>
> For device mode, make sure to disable system wakeup if no gadget driver
> is bound. We may experience unwanted system wakeup due to the wakeup
> signal from the controller PMU detecting connection/disconnection when
> in low power (D3). E.g. In the case of Steam Deck, the PCI PME prevents
> the system staying in suspend.
>
> Cc: stable@vger.kernel.org
> Reported-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
> Closes: https://lore.kernel.org/linux-usb/70a7692d-647c-9be7-00a6-06fc60f77294@igalia.com/T/#mf00d6669c2eff7b308d1162acd1d66c09f0853c7
> Fixes: d07e8819a03d ("usb: dwc3: add xHCI Host support")
> Signed-off-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
[CCing some interested parties here from Deck development teams]
Hi Thinh, thanks a bunch for the fix, and all the support and attention
on this issue - much appreciated!
I've tested this fix on top of v6.8-rc7, in the Steam Deck, and it
manages to resolve the sleep problems we have on device mode.
So, feel free to add:
Tested-by: Guilherme G. Piccoli <gpiccoli@igalia.com> # Steam Deck
Should we try to get it included last minute on v6.8, or better to make
use of the merge window opening next week?
Cheers,
Guilherme
next prev parent reply other threads:[~2024-03-08 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 2:40 [PATCH] usb: dwc3: Properly set system wakeup Thinh Nguyen
2024-03-08 7:01 ` Sanath S
2024-03-08 14:34 ` Guilherme G. Piccoli [this message]
2024-03-15 1:03 ` Thinh Nguyen
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=cac3f811-189f-be7f-e5fa-12ee6ca8a62a@igalia.com \
--to=gpiccoli@igalia.com \
--cc=John.Youn@synopsys.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=andrew.smirnov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=johns@valvesoftware.com \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vivek@collabora.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