From: Rob Herring <robh@kernel.org>
To: Olivier Moysan <olivier.moysan@foss.st.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/8] dt-bindings: iio: add backend support to sd modulator
Date: Wed, 3 Jul 2024 16:08:51 -0600 [thread overview]
Message-ID: <20240703220851.GA2075233-robh@kernel.org> (raw)
In-Reply-To: <20240703160535.2277871-6-olivier.moysan@foss.st.com>
On Wed, Jul 03, 2024 at 06:05:30PM +0200, Olivier Moysan wrote:
> The legacy sd modulator driver registers the sigma delta modulator as
> an IIO channel provider. This implementation is not convenient when the
> SD modulator has to be cascaded with another IIO device. The scaling
> information is distributed across devices, which makes it difficult to
> report consistent scaling data on IIO devices.
>
> The solution is to expose these cascaded IIO devices as an aggregate
> device, which report global scaling information.
> Add IIO backend support to SD modulator to allow scaling information
> management.
>
> Signed-off-by: Olivier Moysan <olivier.moysan@foss.st.com>
> ---
> .../iio/adc/sigma-delta-modulator.yaml | 24 +++++++++++++++++--
> 1 file changed, 22 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/iio/adc/sigma-delta-modulator.yaml b/Documentation/devicetree/bindings/iio/adc/sigma-delta-modulator.yaml
> index cab0d425eaa4..e34aa560da63 100644
> --- a/Documentation/devicetree/bindings/iio/adc/sigma-delta-modulator.yaml
> +++ b/Documentation/devicetree/bindings/iio/adc/sigma-delta-modulator.yaml
> @@ -18,18 +18,38 @@ properties:
> - sd-modulator
> - ads1201
>
> + '#io-backend-cells':
> + const: 0
> +
> '#io-channel-cells':
> const: 0
>
> + reg:
> + maxItems: 1
> +
> + vref-supply:
> + description: Phandle to the vref input analog reference voltage.
> +
> required:
> - compatible
> - - '#io-channel-cells'
> +
> +allOf:
Don't need allOf
> + - anyOf:
> + - required: ['#io-backend-cells']
> + - required: ['#io-channel-cells']
>
> additionalProperties: false
>
> examples:
> - |
> - ads1202: adc {
> + // Exemple1: SD modulator is an IIO backend device
> + ads1201_0 {
> + compatible = "ti,ads1201";
> + #io-backend-cells = <0>;
> + };
> +
> + //Example2: SD modulator is an IIO channel provider
> + ads1201_1 {
> compatible = "sd-modulator";
> #io-channel-cells = <0>;
Don't you need some link between the nodes?
> };
> --
> 2.25.1
>
prev parent reply other threads:[~2024-07-03 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 16:05 [PATCH v3 0/8] iio: adc: dfsdm: add scaling support Olivier Moysan
2024-07-03 16:05 ` [PATCH v3 4/8] dt-bindings: iio: dfsdm: move to backend framework Olivier Moysan
2024-07-03 16:05 ` [PATCH v3 5/8] dt-bindings: iio: add backend support to sd modulator Olivier Moysan
2024-07-03 17:33 ` Rob Herring (Arm)
2024-07-03 22:08 ` Rob Herring [this message]
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=20240703220851.GA2075233-robh@kernel.org \
--to=robh@kernel.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olivier.moysan@foss.st.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;
as well as URLs for NNTP newsgroup(s).