From: duanchenghao <duanchenghao@kylinos.cn>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Hongyu Xie <xy521521@gmail.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-usb@vger.kernel.org,
niko.mauno@vaisala.com, pavel@ucw.cz, stanley_chang@realtek.com,
tj@kernel.org, Hongyu Xie <xiehongyu1@kylinos.cn>
Subject: Re: [PATCH] USB: Fix the issue of task recovery failure caused by USB status when S4 wakes up
Date: Sat, 12 Oct 2024 17:51:41 +0800 [thread overview]
Message-ID: <f27bcdb6c5ddd4e91a1dc9f86b4f0c55c50671a8.camel@kylinos.cn> (raw)
In-Reply-To: <b8eb28f3-504d-4d26-8b02-ca1ae7309a70@rowland.harvard.edu>
Hi Alan,
The V3 patch has been sent. Please review it to check if it aligns with
the solution you described.
Thanks
Duan Chenghao
在 2024-10-11星期五的 09:53 -0400,Alan Stern写道:
> On Fri, Oct 11, 2024 at 09:42:11AM +0800, duanchenghao wrote:
> > Hi Alan,
> >
> > I roughly understand now.
> >
> > In your previous email, you mentioned assigning a value to
> > do_wakeup
> > based on the judgment of PMSG in suspend_common, but there is no
> > parameter passing of PMSG in suspend_common.
>
> In my kernel tree, the first line of code in suspend_common()
> (following
> all the variable definitions) is this:
>
> do_wakeup = PMSG_IS_AUTO(msg) ? true :
> device_may_wakeup(dev);
>
> That's what I was talking about.
>
> > Do you mean using the global parameter pm_transition.event for the
> > judgment?
>
> No, I meant what I wrote.
>
> Alan Stern
next prev parent reply other threads:[~2024-10-12 9:52 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 3:05 Duan Chenghao
2024-09-06 14:05 ` Alan Stern
[not found] ` <1725931490447646.3.seg@mailgw.kylinos.cn>
2024-09-10 9:34 ` duanchenghao
2024-09-10 9:36 ` duanchenghao
2024-09-11 14:40 ` Alan Stern
2024-09-12 3:21 ` duanchenghao
2024-09-12 6:26 ` [PATCH v2] " Duan Chenghao
2024-09-12 15:00 ` [PATCH] " Alan Stern
2024-09-13 1:51 ` duanchenghao
2024-09-13 9:38 ` duanchenghao
2024-09-14 2:43 ` Hongyu Xie
2024-09-23 8:00 ` duanchenghao
2024-09-24 13:38 ` Alan Stern
2024-09-29 3:14 ` duanchenghao
2024-10-09 1:19 ` duanchenghao
2024-10-09 1:54 ` Alan Stern
2024-10-09 2:35 ` duanchenghao
2024-10-09 6:29 ` Gopal, Saranya
2024-10-09 15:50 ` Alan Stern
2024-10-10 5:53 ` duanchenghao
2024-10-10 5:59 ` duanchenghao
2024-10-10 14:21 ` Alan Stern
2024-10-11 1:42 ` duanchenghao
2024-10-11 13:53 ` Alan Stern
2024-10-12 9:46 ` [PATCH v3] " Duan Chenghao
2024-10-12 12:39 ` Greg KH
2024-10-12 12:40 ` Greg KH
2024-10-12 15:06 ` Alan Stern
2024-10-12 9:51 ` duanchenghao [this message]
2024-10-12 15:01 ` [PATCH] " Alan Stern
2024-10-14 1:32 ` duanchenghao
2024-10-14 1:41 ` duanchenghao
2024-10-14 4:10 ` Gopal, Saranya
2024-10-16 8:57 ` Gopal, Saranya
2024-10-16 9:06 ` duanchenghao
2024-10-24 2:40 ` [PATCH v4] " Duan Chenghao
2024-10-24 2:53 ` duanchenghao
2024-10-24 7:05 ` Greg KH
2024-10-24 8:46 ` duanchenghao
2024-10-29 3:27 ` Greg KH
2024-10-29 8:01 ` duanchenghao
2024-11-06 1:29 ` duanchenghao
2024-11-21 19:09 ` Greg KH
2024-11-20 2:14 ` 回复:[PATCH " Duan Chenghao
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=f27bcdb6c5ddd4e91a1dc9f86b4f0c55c50671a8.camel@kylinos.cn \
--to=duanchenghao@kylinos.cn \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=niko.mauno@vaisala.com \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=stanley_chang@realtek.com \
--cc=stern@rowland.harvard.edu \
--cc=tj@kernel.org \
--cc=xiehongyu1@kylinos.cn \
--cc=xy521521@gmail.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®