* [PATCH RFC] PM: runtime: Drop device usage only after remove is done
@ 2023-04-02 10:39 Uwe Kleine-König
2023-04-03 19:17 ` Wysocki, Rafael J
0 siblings, 1 reply; 2+ messages in thread
From: Uwe Kleine-König @ 2023-04-02 10:39 UTC (permalink / raw)
To: Rafael J . Wysocki, Greg Kroah-Hartman; +Cc: linux-kernel, kernel
Many device drivers call one of the variants of pm_runtime_resume() in
their remove callback. So calling pm_runtime_put_sync() just before that
is ineffective as the suspend callback might just be called just to
resume the device directly afterwards again.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
---
Hello,
this is a theoretical issue that I noticed while doing some research how
pm-runtime works. Not sure it makes sense, so I marked it as RFC.
Best regards
Uwe
drivers/base/dd.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/base/dd.c b/drivers/base/dd.c
index 8def2ba08a82..6beac141d3d2 100644
--- a/drivers/base/dd.c
+++ b/drivers/base/dd.c
@@ -1235,10 +1235,10 @@ static void __device_release_driver(struct device *dev, struct device *parent)
bus_notify(dev, BUS_NOTIFY_UNBIND_DRIVER);
- pm_runtime_put_sync(dev);
-
device_remove(dev);
+ pm_runtime_put_sync(dev);
+
if (dev->bus && dev->bus->dma_cleanup)
dev->bus->dma_cleanup(dev);
base-commit: fe15c26ee26efa11741a7b632e9f23b01aca4cc6
--
2.39.2
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH RFC] PM: runtime: Drop device usage only after remove is done
2023-04-02 10:39 [PATCH RFC] PM: runtime: Drop device usage only after remove is done Uwe Kleine-König
@ 2023-04-03 19:17 ` Wysocki, Rafael J
0 siblings, 0 replies; 2+ messages in thread
From: Wysocki, Rafael J @ 2023-04-03 19:17 UTC (permalink / raw)
To: Uwe Kleine-König, Greg Kroah-Hartman; +Cc: linux-kernel, kernel, linux-pm
CC-ing linux-pm would have been nice (done now).
On 4/2/2023 12:39 PM, Uwe Kleine-König wrote:
> Many device drivers call one of the variants of pm_runtime_resume() in
> their remove callback. So calling pm_runtime_put_sync() just before that
> is ineffective as the suspend callback might just be called just to
> resume the device directly afterwards again.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Hello,
>
> this is a theoretical issue that I noticed while doing some research how
> pm-runtime works. Not sure it makes sense, so I marked it as RFC.
>
> Best regards
> Uwe
>
> drivers/base/dd.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/base/dd.c b/drivers/base/dd.c
> index 8def2ba08a82..6beac141d3d2 100644
> --- a/drivers/base/dd.c
> +++ b/drivers/base/dd.c
> @@ -1235,10 +1235,10 @@ static void __device_release_driver(struct device *dev, struct device *parent)
>
> bus_notify(dev, BUS_NOTIFY_UNBIND_DRIVER);
>
> - pm_runtime_put_sync(dev);
> -
> device_remove(dev);
>
> + pm_runtime_put_sync(dev);
> +
> if (dev->bus && dev->bus->dma_cleanup)
> dev->bus->dma_cleanup(dev);
>
>
> base-commit: fe15c26ee26efa11741a7b632e9f23b01aca4cc6
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-04-03 19:18 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-04-02 10:39 [PATCH RFC] PM: runtime: Drop device usage only after remove is done Uwe Kleine-König
2023-04-03 19:17 ` Wysocki, Rafael J
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®