[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a461add5-95a0-4750-8d66-850cce2fe9fb@acm.org>
Date: Mon, 1 Dec 2025 15:06:30 -1000
From: Bart Van Assche <bvanassche@....org>
To: "Rafael J. Wysocki" <rafael@...nel.org>, YangYang <yang.yang@...o.com>
Cc: Jens Axboe <axboe@...nel.dk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Danilo Krummrich <dakr@...nel.org>, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [PATCH v1] PM: sleep: Do not flag runtime PM workqueue as
freezable
On 12/1/25 11:58 AM, Rafael J. Wysocki wrote:
> So I've been testing the patch below for a few days and it will eliminate
> the latter, but even after this patch runtime PM will be disabled in
> device_suspend_late() and if the problem you are facing is still there
> after this patch, it will need to dealt with at the driver level.
>
> Generally speaking, driver involvement is needed to make runtime PM and
> system suspend/resume work together in the majority of cases.
Thank you for having developed and shared this patch. Is the following
quote from the Linux kernel documentation still correct with this patch
applied or should an update for Documentation/power/runtime_pm.rst
perhaps be included in this patch?
"The power management workqueue pm_wq in which bus types and device
drivers can
put their PM-related work items. It is strongly recommended that
pm_wq be
used for queuing all work items related to runtime PM, because this
allows
them to be synchronized with system-wide power transitions (suspend
to RAM,
hibernation and resume from system sleep states). pm_wq is declared in
include/linux/pm_runtime.h and defined in kernel/power/main.c."
Bart.
Powered by blists - more mailing lists