* [PATCH] Input: omap-keypad - fix runtime pm imbalance on error
@ 2020-05-20 13:34 Dinghao Liu
2020-05-20 17:02 ` Dmitry Torokhov
0 siblings, 1 reply; 4+ messages in thread
From: Dinghao Liu @ 2020-05-20 13:34 UTC (permalink / raw)
To: dinghao.liu, kjlu
Cc: Dmitry Torokhov, Richard Fontana, Allison Randal,
Thomas Gleixner, Greg Kroah-Hartman, linux-input, linux-kernel
pm_runtime_get_sync() increments the runtime PM usage counter even
the call returns an error code. Thus a pairing decrement is needed
on the error handling path to keep the counter balanced.
Signed-off-by: Dinghao Liu <dinghao.liu@zju.edu.cn>
---
drivers/input/keyboard/omap4-keypad.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/keyboard/omap4-keypad.c b/drivers/input/keyboard/omap4-keypad.c
index 94c94d7f5155..d13d81c796d2 100644
--- a/drivers/input/keyboard/omap4-keypad.c
+++ b/drivers/input/keyboard/omap4-keypad.c
@@ -371,8 +371,8 @@ static int omap4_keypad_probe(struct platform_device *pdev)
err_free_input:
input_free_device(input_dev);
err_pm_put_sync:
- pm_runtime_put_sync(&pdev->dev);
err_unmap:
+ pm_runtime_put_sync(&pdev->dev);
iounmap(keypad_data->base);
err_release_mem:
release_mem_region(res->start, resource_size(res));
--
2.17.1
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH] Input: omap-keypad - fix runtime pm imbalance on error
2020-05-20 13:34 [PATCH] Input: omap-keypad - fix runtime pm imbalance on error Dinghao Liu
@ 2020-05-20 17:02 ` Dmitry Torokhov
2020-05-20 17:19 ` Rafael J. Wysocki
2020-05-21 5:19 ` dinghao.liu
0 siblings, 2 replies; 4+ messages in thread
From: Dmitry Torokhov @ 2020-05-20 17:02 UTC (permalink / raw)
To: Dinghao Liu, Rafael J. Wysocki
Cc: Kangjie Lu, Richard Fontana, Allison Randal, Thomas Gleixner,
Greg Kroah-Hartman, linux-input, lkml
Hi Dinghao,
On Wed, May 20, 2020 at 6:35 AM Dinghao Liu <dinghao.liu@zju.edu.cn> wrote:
>
> pm_runtime_get_sync() increments the runtime PM usage counter even
> the call returns an error code. Thus a pairing decrement is needed
> on the error handling path to keep the counter balanced.
This is a very surprising behavior and I wonder if this should be
fixed in the PM core (or the required cleanup steps need to be called
out in the function description). I also see that a few drivers that
handle this situation correctly (?) call pm_runtime_put_noidle()
instead of pm_runtime_put_sync() in the error path.
Rafael, do you have any guidance here?
Thanks.
--
Dmitry
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] Input: omap-keypad - fix runtime pm imbalance on error
2020-05-20 17:02 ` Dmitry Torokhov
@ 2020-05-20 17:19 ` Rafael J. Wysocki
2020-05-21 5:19 ` dinghao.liu
1 sibling, 0 replies; 4+ messages in thread
From: Rafael J. Wysocki @ 2020-05-20 17:19 UTC (permalink / raw)
To: Dmitry Torokhov
Cc: Dinghao Liu, Rafael J. Wysocki, Kangjie Lu, Richard Fontana,
Allison Randal, Thomas Gleixner, Greg Kroah-Hartman, linux-input,
lkml
On Wed, May 20, 2020 at 7:02 PM Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
>
> Hi Dinghao,
>
> On Wed, May 20, 2020 at 6:35 AM Dinghao Liu <dinghao.liu@zju.edu.cn> wrote:
> >
> > pm_runtime_get_sync() increments the runtime PM usage counter even
> > the call returns an error code. Thus a pairing decrement is needed
> > on the error handling path to keep the counter balanced.
>
> This is a very surprising behavior and I wonder if this should be
> fixed in the PM core (or the required cleanup steps need to be called
> out in the function description).
It has been like that forever and it's intentional, because it allows
certain pieces of code to do things like
pm_runtime_get_sync(dev);
/* do something regardless of whether or not PM-runtime is enabled for dev */
pm_runtime_put(dev);
So I wouldn't really call it surprising.
> I also see that a few drivers that
> handle this situation correctly (?) call pm_runtime_put_noidle()
> instead of pm_runtime_put_sync() in the error path.
>
> Rafael, do you have any guidance here?
Feel free to improve the kerneldoc comment of __pm_runtime_resume(),
although it is clear enough to me, and fix the callers that leak the
refcount.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Re: [PATCH] Input: omap-keypad - fix runtime pm imbalance on error
2020-05-20 17:02 ` Dmitry Torokhov
2020-05-20 17:19 ` Rafael J. Wysocki
@ 2020-05-21 5:19 ` dinghao.liu
1 sibling, 0 replies; 4+ messages in thread
From: dinghao.liu @ 2020-05-21 5:19 UTC (permalink / raw)
To: Dmitry Torokhov
Cc: Rafael J. Wysocki, Kangjie Lu, Richard Fontana, Allison Randal,
Thomas Gleixner, Greg Kroah-Hartman, linux-input, lkml
Fixing this in the PM core will influence all callers of pm_runtime_get_sync().
Therefore I think the better solution is to fix its misused callers.
Regards,
Dinghao
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>写道:
> Hi Dinghao,
>
> On Wed, May 20, 2020 at 6:35 AM Dinghao Liu <dinghao.liu@zju.edu.cn> wrote:
> >
> > pm_runtime_get_sync() increments the runtime PM usage counter even
> > the call returns an error code. Thus a pairing decrement is needed
> > on the error handling path to keep the counter balanced.
>
> This is a very surprising behavior and I wonder if this should be
> fixed in the PM core (or the required cleanup steps need to be called
> out in the function description). I also see that a few drivers that
> handle this situation correctly (?) call pm_runtime_put_noidle()
> instead of pm_runtime_put_sync() in the error path.
>
> Rafael, do you have any guidance here?
>
> Thanks.
>
> --
> Dmitry
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-05-21 5:27 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-20 13:34 [PATCH] Input: omap-keypad - fix runtime pm imbalance on error Dinghao Liu
2020-05-20 17:02 ` Dmitry Torokhov
2020-05-20 17:19 ` Rafael J. Wysocki
2020-05-21 5:19 ` dinghao.liu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).