From: Jonathan Cameron <jic23@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: "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>,
"Olivier Moysan" <olivier.moysan@foss.st.com>,
"Mark Brown" <broonie@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH v2 2/4] iio: backend: add devm_iio_backend_get_by_index()
Date: Sat, 7 Feb 2026 14:57:31 +0000 [thread overview]
Message-ID: <20260207145731.69c8d842@jic23-huawei> (raw)
In-Reply-To: <550323d752213f177b7673bdd42e667f1d2228cb.1770393792.git.antoniu.miclaus@analog.com>
On Fri, 6 Feb 2026 18:07:14 +0200
Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
> Add a new function to get an IIO backend by its index in the
> io-backends device tree property. This is useful for multi-channel
> devices that have multiple backends, where looking up by index is
> more straightforward than using named backends.
>
> The new function directly uses the index to find the backend reference
> in the io-backends property, avoiding the need for io-backend-names.
>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
One thing inline.
> ---
> drivers/iio/industrialio-backend.c | 51 ++++++++++++++++++++++++++++++
> include/linux/iio/backend.h | 2 ++
> 2 files changed, 53 insertions(+)
>
> diff --git a/drivers/iio/industrialio-backend.c b/drivers/iio/industrialio-backend.c
> index 447b694d6d5f..3b692d48481e 100644
> --- a/drivers/iio/industrialio-backend.c
> +++ b/drivers/iio/industrialio-backend.c
> @@ -1008,6 +1008,57 @@ struct iio_backend *devm_iio_backend_get(struct device *dev, const char *name)
> }
> EXPORT_SYMBOL_NS_GPL(devm_iio_backend_get, "IIO_BACKEND");
>
> +static struct iio_backend *
> +__devm_iio_backend_fwnode_get_by_index(struct device *dev,
> + struct fwnode_handle *fwnode,
> + unsigned int index)
> +{
> + struct fwnode_handle *fwnode_back;
> + struct iio_backend *back;
> + int ret;
> +
> + fwnode_back = fwnode_find_reference(fwnode, "io-backends", index);
Applies more generally in this file, but does holding the fwnode over the
__dev_iio_backed_get() below matter? If not
struct fwnode_handle *fwnode_back __free(fwnode_handle) =
fwnode_find_reference(fwnode, "io-backends", index);
and you can drop the various fwnode_handle_put() calls.
> + if (IS_ERR(fwnode_back))
> + return dev_err_cast_probe(dev, fwnode_back,
> + "Cannot get Firmware reference\n");
> +
> + guard(mutex)(&iio_back_lock);
> + list_for_each_entry(back, &iio_back_list, entry) {
> + if (!device_match_fwnode(back->dev, fwnode_back))
> + continue;
> +
> + fwnode_handle_put(fwnode_back);
> + ret = __devm_iio_backend_get(dev, back);
> + if (ret)
> + return ERR_PTR(ret);
> +
> + back->idx = index;
> +
> + return back;
> + }
> +
> + fwnode_handle_put(fwnode_back);
> + return ERR_PTR(-EPROBE_DEFER);
> +}
> +
> +/**
> + * devm_iio_backend_get_by_index - Device managed backend device get by index
> + * @dev: Consumer device for the backend
> + * @index: Index of the backend in the io-backends property
> + *
> + * Get's the backend at @index associated with @dev.
> + *
> + * RETURNS:
> + * A backend pointer, negative error pointer otherwise.
> + */
> +struct iio_backend *devm_iio_backend_get_by_index(struct device *dev,
> + unsigned int index)
> +{
> + return __devm_iio_backend_fwnode_get_by_index(dev, dev_fwnode(dev),
> + index);
> +}
> +EXPORT_SYMBOL_NS_GPL(devm_iio_backend_get_by_index, "IIO_BACKEND");
> +
> /**
> * devm_iio_backend_fwnode_get - Device managed backend firmware node get
> * @dev: Consumer device for the backend
> diff --git a/include/linux/iio/backend.h b/include/linux/iio/backend.h
> index 7f815f3fed6a..8f18df0ca896 100644
> --- a/include/linux/iio/backend.h
> +++ b/include/linux/iio/backend.h
> @@ -237,6 +237,8 @@ int iio_backend_extend_chan_spec(struct iio_backend *back,
> struct iio_chan_spec *chan);
> void *iio_backend_get_priv(const struct iio_backend *conv);
> struct iio_backend *devm_iio_backend_get(struct device *dev, const char *name);
> +struct iio_backend *devm_iio_backend_get_by_index(struct device *dev,
> + unsigned int index);
> struct iio_backend *devm_iio_backend_fwnode_get(struct device *dev,
> const char *name,
> struct fwnode_handle *fwnode);
next prev parent reply other threads:[~2026-02-07 14:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 16:07 [PATCH v2 0/4] iio: adc: ad4080: add support for AD4880 dual-channel ADC Antoniu Miclaus
2026-02-06 16:07 ` [PATCH v2 1/4] spi: allow ancillary devices to share parent's chip selects Antoniu Miclaus
2026-02-07 18:09 ` David Lechner
2026-02-06 16:07 ` [PATCH v2 2/4] iio: backend: add devm_iio_backend_get_by_index() Antoniu Miclaus
2026-02-07 14:57 ` Jonathan Cameron [this message]
2026-02-07 18:13 ` David Lechner
2026-02-08 9:24 ` Nuno Sá
2026-02-09 15:28 ` David Lechner
2026-02-09 16:47 ` Nuno Sá
2026-02-09 17:48 ` Nuno Sá
2026-02-09 18:20 ` David Lechner
2026-02-06 16:07 ` [PATCH v2 3/4] dt-bindings: iio: adc: ad4080: add AD4880 support Antoniu Miclaus
2026-02-07 10:41 ` Krzysztof Kozlowski
2026-02-08 9:16 ` Nuno Sá
2026-02-08 9:20 ` Krzysztof Kozlowski
2026-02-09 16:43 ` Nuno Sá
2026-02-09 17:13 ` Krzysztof Kozlowski
2026-02-09 17:45 ` Nuno Sá
2026-02-06 16:07 ` [PATCH v2 4/4] iio: adc: ad4080: add support for AD4880 dual-channel ADC Antoniu Miclaus
2026-02-07 15:04 ` Jonathan Cameron
2026-02-07 18:29 ` David Lechner
2026-02-08 9:26 ` Nuno Sá
2026-02-08 12:50 ` [PATCH v2 0/4] " Andy Shevchenko
2026-02-14 16:08 ` Jonathan Cameron
2026-02-14 18:11 ` Andy Shevchenko
2026-02-14 18:31 ` David Lechner
2026-02-15 8:03 ` Andy Shevchenko
2026-02-15 23:16 ` David Lechner
2026-02-16 7:14 ` Andy Shevchenko
2026-02-16 18:53 ` David Lechner
2026-02-17 8:28 ` Andy Shevchenko
2026-02-17 22:55 ` David Lechner
2026-02-18 19:08 ` Jonathan Cameron
2026-02-20 10:45 ` Andy Shevchenko
2026-02-25 19:07 ` (subset) " Mark Brown
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=20260207145731.69c8d842@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.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