From: Jonathan Cameron <jic23@kernel.org>
To: Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org>
Cc: <nuno.sa@analog.com>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v2 6/8] iio: add the IIO backend framework
Date: Sun, 10 Dec 2023 14:28:54 +0000 [thread overview]
Message-ID: <20231210142854.27e3f5af@jic23-huawei> (raw)
In-Reply-To: <20231208-dev-iio-backend-v2-6-5450951895e1@analog.com>
On Fri, 08 Dec 2023 16:14:13 +0100
Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org> wrote:
> From: Nuno Sa <nuno.sa@analog.com>
>
> This is a Framework to handle complex IIO aggregate devices.
>
> The typical architecture is to have one device as the frontend device which
> can be "linked" against one or multiple backend devices. All the IIO and
> userspace interface is expected to be registers/managed by the frontend
> device which will callback into the backends when needed (to get/set
> some configuration that it does not directly control).
>
> The basic framework interface is pretty simple:
> - Backends should register themselves with @devm_iio_backend_register()
> - Frontend devices should get backends with @devm_iio_backend_get()
>
> Signed-off-by: Nuno Sa <nuno.sa@analog.com>
Name space all the Symbol Exports. Otherwise, no particular comments from me.
I will take a deeper look at all the details at somepoint, but so far
it looks basically fine to me.
Jonathan
next prev parent reply other threads:[~2023-12-10 14:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 15:14 [PATCH v2 0/8] iio: add new backend framework Nuno Sa via B4 Relay
2023-12-08 15:14 ` [PATCH v2 1/8] dt-bindings: adc: ad9467: document io-backend property Nuno Sa via B4 Relay
2023-12-08 17:40 ` Krzysztof Kozlowski
2023-12-09 14:35 ` Nuno Sá
2023-12-08 15:14 ` [PATCH v2 2/8] dt-bindings: adc: axi-adc: deprecate 'adi,adc-dev' Nuno Sa via B4 Relay
2023-12-08 17:39 ` Krzysztof Kozlowski
2023-12-09 14:40 ` Nuno Sá
2023-12-08 15:14 ` [PATCH v2 3/8] driver: core: allow modifying device_links flags Nuno Sa via B4 Relay
2023-12-10 14:22 ` Jonathan Cameron
2023-12-08 15:14 ` [PATCH v2 4/8] of: property: add device link support for io-backends Nuno Sa via B4 Relay
2023-12-08 15:14 ` [PATCH v2 5/8] iio: buffer-dmaengine: export buffer alloc and free functions Nuno Sa via B4 Relay
2023-12-10 14:24 ` Jonathan Cameron
2023-12-11 9:36 ` Nuno Sá
2023-12-08 15:14 ` [PATCH v2 6/8] iio: add the IIO backend framework Nuno Sa via B4 Relay
2023-12-10 14:28 ` Jonathan Cameron [this message]
2023-12-08 15:14 ` [PATCH v2 7/8] iio: adc: ad9467: convert to " Nuno Sa via B4 Relay
2023-12-08 15:14 ` [PATCH v2 8/8] iio: adc: adi-axi-adc: move " Nuno Sa via B4 Relay
2023-12-08 15:30 ` [PATCH v2 0/8] iio: add new " Conor Dooley
2023-12-09 14:32 ` Nuno Sá
2023-12-10 14:04 ` Conor Dooley
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=20231210142854.27e3f5af@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+nuno.sa.analog.com@kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=rafael@kernel.org \
--cc=robh+dt@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