From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Rupesh Majhi" <zoone.rupert@gmail.com>,
"Andy Shevchenko" <andy@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Jishnu Prakash" <jishnu.prakash@oss.qualcomm.com>,
"Nuno Sá" <nuno.sa@analog.com>,
linux-arm-msm@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, "Marco Elver" <elver@google.com>,
"Bart Van Assche" <bvanassche@acm.org>
Subject: Re: [PATCH] iio: adc: qcom-spmi-adc5-gen3: fix lock annotations on mutex helpers
Date: Mon, 19 Oct 2026 00:45:09 +0100 [thread overview]
Message-ID: <20261019004509.68409863@jic23-hlaptop> (raw)
In-Reply-To: <asIRkK-uUz4FKQBN@ashevche-desk.local>
On Sun, 4 Oct 2026 11:42:56 +0300
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> On Sun, Oct 04, 2026 at 12:45:16AM +0300, Rupesh Majhi wrote:
> > The __acquires() and __releases() on adc5_gen3_mutex_lock() and
> > adc5_gen3_mutex_unlock() name adc, a local declared in the body. With
> > context analysis enabled for this file, the build fails:
> >
> > error: use of undeclared identifier 'adc'
> >
> > The lock and unlock are split across these two helpers for the ADC_TM
> > driver, so mark them __context_unsafe() instead.
>
> Doesn't sound right to me. The __acquires() and __releases() IIRC are sparse
> annotations. If clang has something special, it needs to be addressed in
> the compiler-clang.h, no?
>
It's in compiler-context-analysis.h and for now I believe is clang
only. Reuses the older sparse definitions. I think the intent is to avoid
churn.
I currently have no idea if this is the right fix. The only users
today are places where a lock is intentionally skipped.
+CC Marco and Bart and putting back the patch content for context.
> diff --git a/drivers/iio/adc/qcom-spmi-adc5-gen3.c b/drivers/iio/adc/qcom-spmi-adc5-gen3.c
> index c68c6c5f6aca..6a3cabedf4e8 100644
> --- a/drivers/iio/adc/qcom-spmi-adc5-gen3.c
> +++ b/drivers/iio/adc/qcom-spmi-adc5-gen3.c
> @@ -663,7 +663,7 @@ static int adc5_gen3_add_aux_tm_device(struct adc5_chip *adc)
> }
>
> void adc5_gen3_mutex_lock(struct device *dev)
> - __acquires(&adc->lock)
> + __context_unsafe(/* returns with adc->lock held */)
> {
> struct iio_dev *indio_dev = dev_get_drvdata(dev->parent);
> struct adc5_chip *adc = iio_priv(indio_dev);
> @@ -673,7 +673,7 @@ void adc5_gen3_mutex_lock(struct device *dev)
> EXPORT_SYMBOL_NS_GPL(adc5_gen3_mutex_lock, "QCOM_SPMI_ADC5_GEN3");
>
> void adc5_gen3_mutex_unlock(struct device *dev)
> - __releases(&adc->lock)
> + __context_unsafe(/* releases adc->lock */)
> {
> struct iio_dev *indio_dev = dev_get_drvdata(dev->parent);
> struct adc5_chip *adc = iio_priv(indio_dev);
>
> base-commit: 04434a1d0f311d76b1f15fa987918b471a0b8c6a
> --
> 2.43.0
next prev parent reply other threads:[~2026-10-18 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 21:45 Rupesh Majhi
2026-10-04 8:42 ` Andy Shevchenko
2026-10-18 21:38 ` Rupesh Majhi
2026-10-19 10:01 ` Andy Shevchenko
2026-10-18 23:45 ` Jonathan Cameron [this message]
2026-10-19 22:15 ` Marco Elver
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=20261019004509.68409863@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=bvanassche@acm.org \
--cc=dlechner@baylibre.com \
--cc=elver@google.com \
--cc=jishnu.prakash@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=zoone.rupert@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®