From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Tomas Melin <tomas.melin@vaisala.com>
Cc: Michael Hennerich <Michael.Hennerich@analog.com>,
Nuno Sa <nuno.sa@analog.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Jonathan Cameron <jic23@kernel.org>,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>,
Olivier Moysan <olivier.moysan@foss.st.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 4/4] iio: adc: ad9467: check for backend capabilities
Date: Wed, 21 Jan 2026 14:58:13 +0200 [thread overview]
Message-ID: <aXDNZWSWpuDPzdwv@smile.fi.intel.com> (raw)
In-Reply-To: <20260121-b4-ad9467-optional-backend-v4-4-18d2c0d450cc@vaisala.com>
On Wed, Jan 21, 2026 at 12:08:33PM +0000, Tomas Melin wrote:
> Add capability checks for operation with backends that do not necessarily
> support full set of features, but are otherwise compatible with the device.
> This ensures a fully functional device, but with limited capabilities.
...
> static int __ad9467_update_clock(struct ad9467_state *st, long r_clk)
> if (ret)
> return ret;
>
> - guard(mutex)(&st->lock);
I would leave this as is. Yes, practically we don't need to cover
iio_backend_has_caps() with mutex to access the data, but it just makes code
slightly more maintainable in my opinion. If anything appears here, it would
probably mean some kind of if (...) do_blablabla(...); pattern that will need
a mutex.
> - return ad9467_calibrate(st);
> + if (iio_backend_has_caps(st->back, IIO_BACKEND_CAP_CALIBRATION)) {
> + guard(mutex)(&st->lock);
> + return ad9467_calibrate(st);
> + }
> + return 0;
> }
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-01-21 12:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 12:08 [PATCH v4 0/4] iio: adc: ad9467: Support alternative backends Tomas Melin
2026-01-21 12:08 ` [PATCH v4 1/4] iio: industrialio-backend: support backend capabilities Tomas Melin
2026-01-22 20:43 ` Jonathan Cameron
2026-01-23 5:38 ` Tomas Melin
2026-01-21 12:08 ` [PATCH v4 2/4] iio: adc: adi-axi-adc: define supported iio-backend capabilities Tomas Melin
2026-01-21 12:08 ` [PATCH v4 3/4] iio: adc: adi-axi-dac: " Tomas Melin
2026-01-22 20:44 ` Jonathan Cameron
2026-01-21 12:08 ` [PATCH v4 4/4] iio: adc: ad9467: check for backend capabilities Tomas Melin
2026-01-21 12:58 ` Andy Shevchenko [this message]
2026-01-23 7:10 ` Tomas Melin
2026-01-23 8:18 ` Andy Shevchenko
2026-01-22 20:38 ` [PATCH v4 0/4] iio: adc: ad9467: Support alternative backends 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=aXDNZWSWpuDPzdwv@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.com \
--cc=tomas.melin@vaisala.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