From: Jonathan Cameron <jic23@kernel.org>
To: Dinghao Liu <dinghao.liu@zju.edu.cn>
Cc: kjlu@umn.edu, Linus Walleij <linus.walleij@linaro.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: light: gp2ap002: Fix rumtime PM imbalance on error
Date: Sun, 11 Apr 2021 16:07:20 +0100 [thread overview]
Message-ID: <20210411160720.037c405c@jic23-huawei> (raw)
In-Reply-To: <20210407034927.16882-1-dinghao.liu@zju.edu.cn>
On Wed, 7 Apr 2021 11:49:27 +0800
Dinghao Liu <dinghao.liu@zju.edu.cn> wrote:
> When devm_request_threaded_irq() fails, we should decrease the
> runtime PM counter to keep the counter balanced. But when
> iio_device_register() fails, we need not to decrease it because
> we have already decreased it before.
Whilst agree with your assessment that the code is wrong, I'm not
totally sure why we need to do the pm_runtime_get_noresume() in
the first place. Why do we need to hold the reference for
the operations going on here? What can race against this that
might care about that reference count?
Jonathan
>
> Signed-off-by: Dinghao Liu <dinghao.liu@zju.edu.cn>
> ---
> drivers/iio/light/gp2ap002.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/light/gp2ap002.c b/drivers/iio/light/gp2ap002.c
> index 7ba7aa59437c..040d8429a6e0 100644
> --- a/drivers/iio/light/gp2ap002.c
> +++ b/drivers/iio/light/gp2ap002.c
> @@ -583,7 +583,7 @@ static int gp2ap002_probe(struct i2c_client *client,
> "gp2ap002", indio_dev);
> if (ret) {
> dev_err(dev, "unable to request IRQ\n");
> - goto out_disable_vio;
> + goto out_put_pm;
> }
> gp2ap002->irq = client->irq;
>
> @@ -613,8 +613,9 @@ static int gp2ap002_probe(struct i2c_client *client,
>
> return 0;
>
> -out_disable_pm:
> +out_put_pm:
> pm_runtime_put_noidle(dev);
> +out_disable_pm:
> pm_runtime_disable(dev);
> out_disable_vio:
> regulator_disable(gp2ap002->vio);
next prev parent reply other threads:[~2021-04-11 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 3:49 Dinghao Liu
2021-04-07 7:16 ` Linus Walleij
2021-04-11 15:07 ` Jonathan Cameron [this message]
2021-04-11 22:38 ` Linus Walleij
2021-04-12 10:15 ` Jonathan Cameron
2021-04-12 11:47 ` Linus Walleij
2021-04-18 9:43 ` Jonathan Cameron
2021-04-19 10:28 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210411160720.037c405c@jic23-huawei \
--to=jic23@kernel.org \
--cc=dinghao.liu@zju.edu.cn \
--cc=kjlu@umn.edu \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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®