[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b8eb28f3-504d-4d26-8b02-ca1ae7309a70@rowland.harvard.edu>
Date: Fri, 11 Oct 2024 09:53:07 -0400
From: Alan Stern <stern@...land.harvard.edu>
To: duanchenghao <duanchenghao@...inos.cn>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Hongyu Xie <xy521521@...il.com>, gregkh@...uxfoundation.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
linux-usb@...r.kernel.org, niko.mauno@...sala.com, pavel@....cz,
stanley_chang@...ltek.com, tj@...nel.org,
Hongyu Xie <xiehongyu1@...inos.cn>
Subject: Re: [PATCH] USB: Fix the issue of task recovery failure caused by
USB status when S4 wakes up
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
Powered by blists - more mailing lists