From: Jonathan Cameron <jic23@kernel.org>
To: Kurt Borja <kuurtb@gmail.com>
Cc: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Benson Leung" <bleung@chromium.org>,
"Antoniu Miclaus" <antoniu.miclaus@analog.com>,
"Gwendal Grignou" <gwendal@chromium.org>,
"Shrikant Raskar" <raskar.shree97@gmail.com>,
"Per-Daniel Olsson" <perdaniel.olsson@axis.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Guenter Roeck" <groeck@chromium.org>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
chrome-platform@lists.linux.dev
Subject: Re: [PATCH v5 2/7] iio: core: Refactor iio_device_claim_direct() implementation
Date: Thu, 22 Jan 2026 19:04:01 +0000 [thread overview]
Message-ID: <20260122190401.510234c4@jic23-huawei> (raw)
In-Reply-To: <20260120-lock-impr-v5-2-d4d22347041f@gmail.com>
On Tue, 20 Jan 2026 01:20:42 -0500
Kurt Borja <kuurtb@gmail.com> wrote:
> In order to eventually unify the locking API, implement
> iio_device_claim_direct() fully inline, with the use of
> __iio_dev_mode_lock(), which takes care of sparse annotations.
>
> Reviewed-by: David Lechner <dlechner@baylibre.com>
> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
So sparse does change what it moans about with this one in precisely one instance
There are 9 false positives with Al Viro's updated sparse - I haven't checked the
original one recently.
Anyhow,
drivers/iio/adc/ad7173.c:416:12: warning: context imbalance in 'ad7173_set_filter_type' - different lock contexts for basic block
becomes
drivers/iio/adc/ad7173.c:425:9: warning: context imbalance in 'ad7173_set_filter_type' - unexpected unlock
Lets go with a bit meh for that and move on...
> ---
> drivers/iio/industrialio-core.c | 44 -----------------------------------------
> include/linux/iio/iio.h | 40 ++++++++++++++++++++++++++-----------
> 2 files changed, 28 insertions(+), 56 deletions(-)
>
> diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
> index db803267df6e..0f8e3aa98b72 100644
> --- a/drivers/iio/industrialio-core.c
> +++ b/drivers/iio/industrialio-core.c
> @@ -2201,50 +2201,6 @@ void __iio_dev_mode_unlock(struct iio_dev *indio_dev)
> }
> EXPORT_SYMBOL_GPL(__iio_dev_mode_unlock);
>
> -/**
> - * __iio_device_claim_direct - Keep device in direct mode
> - * @indio_dev: the iio_dev associated with the device
> - *
> - * If the device is in direct mode it is guaranteed to stay
> - * that way until __iio_device_release_direct() is called.
> - *
> - * Use with __iio_device_release_direct().
> - *
> - * Drivers should only call iio_device_claim_direct().
> - *
> - * Returns: true on success, false on failure.
> - */
> -bool __iio_device_claim_direct(struct iio_dev *indio_dev)
> -{
> - struct iio_dev_opaque *iio_dev_opaque = to_iio_dev_opaque(indio_dev);
> -
> - mutex_lock(&iio_dev_opaque->mlock);
> -
> - if (iio_buffer_enabled(indio_dev)) {
> - mutex_unlock(&iio_dev_opaque->mlock);
> - return false;
> - }
> - return true;
> -}
> -EXPORT_SYMBOL_GPL(__iio_device_claim_direct);
> -
> -/**
> - * __iio_device_release_direct - releases claim on direct mode
> - * @indio_dev: the iio_dev associated with the device
> - *
> - * Release the claim. Device is no longer guaranteed to stay
> - * in direct mode.
> - *
> - * Drivers should only call iio_device_release_direct().
> - *
> - * Use with __iio_device_claim_direct()
> - */
> -void __iio_device_release_direct(struct iio_dev *indio_dev)
> -{
> - mutex_unlock(&to_iio_dev_opaque(indio_dev)->mlock);
> -}
> -EXPORT_SYMBOL_GPL(__iio_device_release_direct);
> -
> /**
> * iio_device_claim_buffer_mode - Keep device in buffer mode
> * @indio_dev: the iio_dev associated with the device
> diff --git a/include/linux/iio/iio.h b/include/linux/iio/iio.h
> index aecda887d833..e263ab5eeccf 100644
> --- a/include/linux/iio/iio.h
> +++ b/include/linux/iio/iio.h
> @@ -664,31 +664,47 @@ int iio_push_event(struct iio_dev *indio_dev, u64 ev_code, s64 timestamp);
>
> void __iio_dev_mode_lock(struct iio_dev *indio_dev) __acquires(indio_dev);
> void __iio_dev_mode_unlock(struct iio_dev *indio_dev) __releases(indio_dev);
> -bool __iio_device_claim_direct(struct iio_dev *indio_dev);
> -void __iio_device_release_direct(struct iio_dev *indio_dev);
>
> /*
> * Helper functions that allow claim and release of direct mode
> * in a fashion that doesn't generate many false positives from sparse.
> * Note this must remain static inline in the header so that sparse
> - * can see the __acquire() marking. Revisit when sparse supports
> - * __cond_acquires()
> + * can see the __acquires() and __releases() annotations.
> + */
> +
> +/**
> + * iio_device_claim_direct() - Keep device in direct mode
> + * @indio_dev: the iio_dev associated with the device
> + *
> + * If the device is in direct mode it is guaranteed to stay
> + * that way until iio_device_release_direct() is called.
> + *
> + * Use with iio_device_release_direct().
> + *
> + * Returns: true on success, false on failure.
> */
> static inline bool iio_device_claim_direct(struct iio_dev *indio_dev)
> {
> - if (!__iio_device_claim_direct(indio_dev))
> - return false;
> + __iio_dev_mode_lock(indio_dev);
>
> - __acquire(iio_dev);
> + if (iio_buffer_enabled(indio_dev)) {
> + __iio_dev_mode_unlock(indio_dev);
> + return false;
> + }
>
> return true;
> }
>
> -static inline void iio_device_release_direct(struct iio_dev *indio_dev)
> -{
> - __iio_device_release_direct(indio_dev);
> - __release(indio_dev);
> -}
> +/**
> + * iio_device_release_direct() - Releases claim on direct mode
> + * @indio_dev: the iio_dev associated with the device
> + *
> + * Release the claim. Device is no longer guaranteed to stay
> + * in direct mode.
> + *
> + * Use with iio_device_claim_direct().
> + */
> +#define iio_device_release_direct(indio_dev) __iio_dev_mode_unlock(indio_dev)
>
> int iio_device_claim_buffer_mode(struct iio_dev *indio_dev);
> void iio_device_release_buffer_mode(struct iio_dev *indio_dev);
>
next prev parent reply other threads:[~2026-01-22 19:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 6:20 [PATCH v5 0/7] iio: core: Introduce cleanup.h support for mode locks Kurt Borja
2026-01-20 6:20 ` [PATCH v5 1/7] iio: core: Add and export __iio_dev_mode_lock() Kurt Borja
2026-01-20 6:20 ` [PATCH v5 2/7] iio: core: Refactor iio_device_claim_direct() implementation Kurt Borja
2026-01-22 19:04 ` Jonathan Cameron [this message]
2026-01-22 22:20 ` Kurt Borja
2026-01-23 8:02 ` Andy Shevchenko
2026-01-23 8:01 ` Andy Shevchenko
2026-01-23 9:56 ` Jonathan Cameron
2026-01-20 6:20 ` [PATCH v5 3/7] iio: core: Match iio_device_claim_*() semantics and implementation Kurt Borja
2026-01-20 6:20 ` [PATCH v5 4/7] iio: core: Add cleanup.h support for iio_device_claim_*() Kurt Borja
2026-01-20 6:20 ` [PATCH v5 5/7] iio: light: vcnl4000: Use IIO cleanup helpers Kurt Borja
2026-01-22 19:12 ` Jonathan Cameron
2026-01-22 22:22 ` Kurt Borja
2026-01-20 6:20 ` [PATCH v5 6/7] iio: health: max30102: " Kurt Borja
2026-01-22 19:15 ` Jonathan Cameron
2026-01-20 6:20 ` [PATCH v5 7/7] iio: light: opt4060: " Kurt Borja
2026-01-22 19:16 ` [PATCH v5 0/7] iio: core: Introduce cleanup.h support for mode locks Jonathan Cameron
2026-01-22 22:27 ` Kurt Borja
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=20260122190401.510234c4@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=Michael.Hennerich@analog.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dlechner@baylibre.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=kuurtb@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=perdaniel.olsson@axis.com \
--cc=raskar.shree97@gmail.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®