linux-kernel - Re: [PATCH v0] PM: wakeup: call device resume after superior device complete resume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJZ5v0ihxgyqcG_dU0XS48g6TwHhw5rA58niTfc1SDtHBEPxJg@mail.gmail.com>
Date: Tue, 13 Jan 2026 13:23:49 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Li XingYang <yanhuoguifan@...il.com>
Cc: "Rafael J . Wysocki" <rafael@...nel.org>, Len Brown <lenb@...nel.org>, Pavel Machek <pavel@...nel.org>, 
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Danilo Krummrich <dakr@...nel.org>, linux-pm@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v0] PM: wakeup: call device resume after superior device
 complete resume

On Mon, Jan 12, 2026 at 4:15 PM Li XingYang <yanhuoguifan@...il.com> wrote:
>
> Background:
> Extist device A,B and C.A is parent of B,C has no dependency on
> either A or B.A is an asynchronously resume device,
> while B and C are synchronously resume devices.dpm_list: A->B->C.
> When A has not completed asynchronous resume,
> the main loop will be blocked at B,and C cannot start resume
> even if it is not associated with either A or B.

Yes, that's how "synchronous" works by design.

If you need/want C to suspend/resume independently of A and B, make it
async instead of hacking the core code.

Thanks!