From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Jorge Marques" <gastmaier@gmail.com>,
"Jorge Marques" <jorge.marques@analog.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 3/7] iio: adc: Add support for ad4062
Date: Sat, 6 Dec 2025 16:31:03 +0000 [thread overview]
Message-ID: <20251206163103.514c1aad@jic23-huawei> (raw)
In-Reply-To: <aSQhCKBC36T9t-H1@smile.fi.intel.com>
On Mon, 24 Nov 2025 11:10:32 +0200
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> On Mon, Nov 24, 2025 at 09:57:26AM +0100, Jorge Marques wrote:
> > On Mon, Nov 24, 2025 at 09:43:09AM +0200, Andy Shevchenko wrote:
> > > On Sun, Nov 23, 2025 at 08:48:09PM +0100, Jorge Marques wrote:
> > > > On Sat, Oct 18, 2025 at 05:10:32PM +0100, Jonathan Cameron wrote:
> > > > > On Mon, 13 Oct 2025 09:28:01 +0200
> > > > > Jorge Marques <jorge.marques@analog.com> wrote:
>
> > > > Mostly acknowledgements and explanations, except a comment on ACQUIRE usage.
>
> ...
>
> > > > > > +static int ad4062_read_chan_raw(struct iio_dev *indio_dev, int *val)
> > > > > > +{
> > > > > > + struct ad4062_state *st = iio_priv(indio_dev);
> > > > > > + int ret;
> > > > > > +
> > > > > > + ret = pm_runtime_resume_and_get(&st->i3cdev->dev);
> > > > > There is a nice new
> > > > > ACQUIRE()/ACQUIRE_ERR() related set of conditional guards defined that
> > > > > let you do this using cleanup.h style.
> > > > >
> > > > > https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9a0abc39450a3123fd52533a662fbd37e0d1508c
> > > > >
> > > > > This looks like a perfect example of where those help.
> > > > >
> > > > > When I catch up with review backlog I plan to look for other
> > > > > places to use that infrastructure in IIO.
> > > > >
> > > > I tried implementing, here becomes
> > > >
> > > > ACQUIRE(pm_runtime_active_try_enabled, pm)(&st->i3cdev->dev);
> > > > ret = ACQUIRE_ERR(pm_runtime_active_try_enabled, &pm);
> > > >
> > > > At buffer and monitor, since we put the device as active during the
> > > > lifetime of the buffer and monitor mode, either I leave as is, or I bump
> > > > the counter with pm_runtime_get_noresume, so when the method leaves, the
> > > > counter drops to 1 and not 0, then on disable I drop the counter back to
> > > > 0 and queue the autosuspend with pm_runtime_put_autosuspend.
> > > > >
> > > > > > + if (ret)
> > > > > > + return ret;
> > > > > > +
> > > > > > + ret = ad4062_set_operation_mode(st, st->mode);
> > > > > > + if (ret)
> > > > > > + goto out_error;
> > > > > > +
> > > > > > + ret = __ad4062_read_chan_raw(st, val);
> > > > > > +
> > > > > > +out_error:
> > > > > > + pm_runtime_put_autosuspend(&st->i3cdev->dev);
> > > > > > + return ret;
> > > > > > +}
> > >
> > > I read the above code, I read it again, I don't understand the reasoning.
> > > The ACQUIRE() doesn't change the behaviour of the above code.
> > >
> > > If you need to bump the reference counter, it should be done somewhere else
> > > where it affects the flow, or this code has a bug.
> > >
> > > If I miss something, please elaborate.
> >
> > The part highlighted does not require bumping the reference counter, but
> > at the buffer acquisition and monitor mode, to not put the device back
> > in low power mode during the lifetime of those operations.
> >
> > Buffer more:
> >
> > static int ad4062_triggered_buffer_postenable(struct iio_dev *indio_dev)
> > {
> > struct ad4062_state *st = iio_priv(indio_dev);
> > int ret;
> >
> > // [ Some code ]
> >
> > ACQUIRE(pm_runtime_active_try_enabled, pm)(&st->i3cdev->dev);
> > ret = ACQUIRE_ERR(pm_runtime_active_try_enabled, &pm);
> > if (ret)
> > return ret;
> >
> > // [ More code ]
>
> > pm_runtime_get_noresume(&st->i3cdev->dev);
>
>
> Yes, this looks good if it makes the error paths cleaner.
> Also consider adding
>
> struct device *dev = &st->i3cdev->dev;
>
> at the top of the functions that use it, it might make code better to read.
>
Sorry I'm late to respond to this. If we do end up doing this
Raphael has been posting some new macros to help and I'm rather dubious
about using an acquire to grab a first reference then upgrading with with
a second on the use paths. I think ACQUIRE in this particular place may
just not be appropriate.
Jonathan
> > return 0;
> > }
> >
> > static int ad4062_triggered_buffer_predisable(struct iio_dev *indio_dev)
> > {
> > struct ad4062_state *st = iio_priv(indio_dev);
> >
> > pm_runtime_put_autosuspend(&st->i3cdev->dev);
> > return 0;
> > }
> >
> > Monitor mode:
> >
> > static int ad4062_monitor_mode_enable(struct ad4062_state *st, bool enable)
> > {
> > int ret = 0;
> >
> > if (!enable) {
> > pm_runtime_put_autosuspend(&st->i3cdev->dev);
> > return 0;
> > }
> >
> > ACQUIRE(pm_runtime_active_try_enabled, pm)(&st->i3cdev->dev);
> > ret = ACQUIRE_ERR(pm_runtime_active_try_enabled, &pm);
> > if (ret)
> > return ret;
> >
> > // [ Some code ]
> >
> > pm_runtime_get_noresume(&st->i3cdev->dev);
> > return 0;
> > }
>
next prev parent reply other threads:[~2025-12-06 16:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 7:27 [PATCH 0/7] Add support for AD4062 device family Jorge Marques
2025-10-13 7:27 ` [PATCH 1/7] dt-bindings: iio: adc: Add adi,ad4062 Jorge Marques
2025-10-13 19:50 ` Conor Dooley
2025-10-26 16:35 ` Jorge Marques
2025-10-18 15:11 ` Jonathan Cameron
2025-10-26 16:37 ` Jorge Marques
2025-10-13 7:28 ` [PATCH 2/7] docs: iio: New docs for ad4062 driver Jorge Marques
2025-10-18 15:21 ` Jonathan Cameron
2025-10-28 15:31 ` Jorge Marques
2025-11-02 12:37 ` Jonathan Cameron
2025-11-03 10:19 ` Jorge Marques
2025-11-03 12:22 ` Jorge Marques
2025-11-09 12:16 ` Jonathan Cameron
2025-11-09 12:31 ` Jonathan Cameron
2025-10-13 7:28 ` [PATCH 3/7] iio: adc: Add support for ad4062 Jorge Marques
2025-10-18 16:10 ` Jonathan Cameron
2025-11-23 19:48 ` Jorge Marques
2025-11-24 7:43 ` Andy Shevchenko
2025-11-24 8:57 ` Jorge Marques
2025-11-24 9:10 ` Andy Shevchenko
2025-12-06 16:31 ` Jonathan Cameron [this message]
2025-11-24 9:11 ` Andy Shevchenko
2025-11-24 9:24 ` Jorge Marques
2025-10-13 7:28 ` [PATCH 4/7] docs: iio: ad4062: Add IIO Trigger support Jorge Marques
2025-10-13 7:28 ` [PATCH 5/7] iio: adc: " Jorge Marques
2025-10-18 16:14 ` Jonathan Cameron
2025-11-23 19:48 ` Jorge Marques
2025-10-13 7:28 ` [PATCH 6/7] docs: iio: ad4062: Add IIO Events support Jorge Marques
2025-10-13 7:28 ` [PATCH 7/7] iio: adc: " Jorge Marques
2025-10-18 16:26 ` Jonathan Cameron
2025-11-23 19:48 ` Jorge Marques
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=20251206163103.514c1aad@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=gastmaier@gmail.com \
--cc=jorge.marques@analog.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).