From: Jonathan Cameron <jic23@kernel.org>
To: Nikhil Gautam <nikhilgtr@gmail.com>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] iio: light: gp2ap002: Fix unbalanced runtime PM on repeated event writes
Date: Mon, 3 Aug 2026 01:19:31 +0100 [thread overview]
Message-ID: <20260803011931.1451deca@jic23-huawei> (raw)
In-Reply-To: <20260725015245.5f911412@jic23-huawei>
On Sat, 25 Jul 2026 01:52:45 +0100
Jonathan Cameron <jic23@kernel.org> wrote:
> On Wed, 22 Jul 2026 21:52:45 +0530
> Nikhil Gautam <nikhilgtr@gmail.com> wrote:
>
> > The IIO core does not filter duplicate writes to the event enable
> > attribute, so writing the same value twice invokes
> > write_event_config() twice. Enabling twice leaks a runtime PM
> > reference, preventing the device from ever suspending again;
> > disabling twice underflows the usage count and triggers a
> > "Runtime PM usage count underflow" warning.
> >
> > Bail out early when the requested state matches the current state.
> > While at it, switch to pm_runtime_resume_and_get() so a failed
> > resume is propagated to userspace instead of silently marking the
> > event enabled.
> >
> > Fixes: 97d642e23037c ("iio: light: Add a driver for Sharp GP2AP002x00F")
> > Signed-off-by: Nikhil Gautam <nikhilgtr@gmail.com>
>
> https://sashiko.dev/#/patchset/20260722162247.8229-1-nikhilgtr%40gmail.com
>
> Sashiko raises a point about concurrent accessors. My previous understanding
> was that we were fine if there was only a single file involved. Having
> dug around a bit I'm fairly sure that is correct.
> The comment here implying to me that we are fine.
> https://elixir.bootlin.com/linux/v7.1.4/source/fs/kernfs/file.c#L340
>
> Now if we had more than one file then we couldn't rely on this.
> Hence to me it's a bit fragile and we should probably add a local lock
> anyway.
>
> One other comment inline.
Huh. no idea what that comment was. Never mind.
>
> > ---
> > drivers/iio/light/gp2ap002.c | 13 +++++++++----
> > 1 file changed, 9 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/iio/light/gp2ap002.c b/drivers/iio/light/gp2ap002.c
> > index 42859e5b1089..966459994995 100644
> > --- a/drivers/iio/light/gp2ap002.c
> > +++ b/drivers/iio/light/gp2ap002.c
> > @@ -343,6 +343,10 @@ static int gp2ap002_write_event_config(struct iio_dev *indio_dev,
> > bool state)
> > {
> > struct gp2ap002 *gp2ap002 = iio_priv(indio_dev);
> > + int ret;
> > +
> > + if (state == gp2ap002->enabled)
> > + return 0;
> >
> > if (state) {
> > /*
> > @@ -350,14 +354,15 @@ static int gp2ap002_write_event_config(struct iio_dev *indio_dev,
> > * already) and reintialize the sensor by using runtime_pm
> > * callbacks.
> > */
> > - pm_runtime_get_sync(gp2ap002->dev);
> > - gp2ap002->enabled = true;
>
> > +
> > + ret = pm_runtime_resume_and_get(gp2ap002->dev);
> > + if (ret)
> > + return ret;
> > } else {
> > - pm_runtime_mark_last_busy(gp2ap002->dev);
> > pm_runtime_put_autosuspend(gp2ap002->dev);
> > - gp2ap002->enabled = false;
> > }
> >
> > + gp2ap002->enabled = state;
> > return 0;
> > }
> >
>
>
next prev parent reply other threads:[~2026-08-03 0:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 16:22 [PATCH v2 0/3] iio: light: gp2ap002: runtime PM and error path fixes Nikhil Gautam
2026-07-22 16:22 ` [PATCH v2 1/3] iio: light: gp2ap002: Fix unbalanced runtime PM on repeated event writes Nikhil Gautam
2026-07-25 0:52 ` Jonathan Cameron
2026-08-03 0:19 ` Jonathan Cameron [this message]
2026-07-22 16:22 ` [PATCH v2 2/3] iio: light: gp2ap002: re-enable irq if runtime suspend fails Nikhil Gautam
2026-07-22 16:22 ` [PATCH v2 3/3] iio: light: gp2ap002: Fix regulator leaks in runtime resume error path Nikhil Gautam
2026-08-03 0:27 ` Jonathan Cameron
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=20260803011931.1451deca@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhilgtr@gmail.com \
--cc=nuno.sa@analog.com \
/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®