From: Alan Stern <stern@rowland.harvard.edu>
To: Mingcong Bai <jeffbai@aosc.io>
Cc: Huacai Chen <chenhuacai@kernel.org>,
Huacai Chen <chenhuacai@loongson.cn>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Kexy Biscuit <kexybiscuit@aosc.io>
Subject: Re: [PATCH] USB: core: Enable root_hub's remote wakeup for wakeup sources
Date: Tue, 25 Feb 2025 17:37:49 -0500 [thread overview]
Message-ID: <4db69da5-199d-4db4-b82b-165d8eb1679b@rowland.harvard.edu> (raw)
In-Reply-To: <c2b8f8af-db2b-4b64-9e45-83e2b0a3d919@aosc.io>
On Wed, Feb 26, 2025 at 01:41:14AM +0800, Mingcong Bai wrote:
> Hi Alan,
>
> 在 2025/2/9 18:22, Mingcong Bai 写道:
> > Hi again,
> >
> > Oops. I missed the dmesg.
> >
>
> <snip>
>
> Gentle ping as it has been almost a month since our last correspondence. Can
> you please advise if you would need any further information and, since the
> fix is probably incorrect, if you have any suggestions as to how we could
> move forward with a better fix or platform-specific quirk?
I was waiting to see if your last email (Feb 9) to Huacai Chen got a
reply, since you suggested the problem was Loongson-specific.
As for a platform-specific solution... I wonder if it might not be
better to fix this in userspace, by making Powertop (or whatever tool is
responsible for managing wakeup settings) automatically enable root-hub
wakeups on Loongson platforms.
Another possibility is to ask somebody at Intel if Loongson has some
special way to handle UHCI wakeups that we don't currently support. The
driver does contain support for the USBRES_INTEL register (see
uhci-hcd.h and uhci-pci.c). Is this different for Loongson?
Alan Stern
prev parent reply other threads:[~2025-02-25 22:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 10:06 Huacai Chen
2025-01-31 10:49 ` Greg Kroah-Hartman
2025-01-31 14:46 ` Huacai Chen
2025-01-31 15:17 ` Alan Stern
2025-02-01 6:42 ` Huacai Chen
2025-02-01 16:55 ` Alan Stern
2025-02-03 14:44 ` Huacai Chen
2025-02-03 15:12 ` Alan Stern
2025-02-03 16:01 ` Mingcong Bai
2025-02-03 16:15 ` Alan Stern
2025-02-05 5:59 ` Mingcong Bai
2025-02-05 18:25 ` Alan Stern
2025-02-06 3:49 ` Mingcong Bai
2025-02-06 21:20 ` Alan Stern
2025-02-07 3:23 ` Mingcong Bai
2025-02-09 10:19 ` Mingcong Bai
2025-02-09 10:22 ` Mingcong Bai
2025-02-25 17:41 ` Mingcong Bai
2025-02-25 22:37 ` Alan Stern [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=4db69da5-199d-4db4-b82b-165d8eb1679b@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=gregkh@linuxfoundation.org \
--cc=jeffbai@aosc.io \
--cc=kexybiscuit@aosc.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.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 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®