From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Alisa-Dariana Roman <alisadariana@gmail.com>,
michael.hennerich@analog.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
alexandru.tachici@analog.com, lars@metafoo.de,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
lgirdwood@gmail.com, broonie@kernel.org, andy@kernel.org,
nuno.sa@analog.com, marcelo.schmitt@analog.com,
bigunclemax@gmail.com, dlechner@baylibre.com,
okan.sahin@analog.com, fr0st61te@gmail.com,
alisa.roman@analog.com, marcus.folkesson@gmail.com,
schnelle@linux.ibm.com, liambeguin@gmail.com
Subject: Re: [PATCH v6 4/5] dt-bindings: iio: adc: ad7192: Add AD7194 support
Date: Sat, 20 Apr 2024 11:52:03 +0100 [thread overview]
Message-ID: <20240420115203.1a5783b3@jic23-huawei> (raw)
In-Reply-To: <20240418144019.GA1581398-robh@kernel.org>
On Thu, 18 Apr 2024 09:40:19 -0500
Rob Herring <robh@kernel.org> wrote:
> On Wed, Apr 17, 2024 at 08:00:53PM +0300, Alisa-Dariana Roman wrote:
> > Unlike the other AD719Xs, AD7194 has configurable differential
> > channels. The user can dynamically configure them in the devicetree.
> >
> > Also add an example for AD7194 devicetree.
> >
> > Signed-off-by: Alisa-Dariana Roman <alisa.roman@analog.com>
More general follow up comment inline.
> > ---
> > .../bindings/iio/adc/adi,ad7192.yaml | 77 +++++++++++++++++++
> > 1 file changed, 77 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad7192.yaml b/Documentation/devicetree/bindings/iio/adc/adi,ad7192.yaml
> > index cf5c568f140a..7e4e15e4e648 100644
> > --- a/Documentation/devicetree/bindings/iio/adc/adi,ad7192.yaml
> > +++ b/Documentation/devicetree/bindings/iio/adc/adi,ad7192.yaml
> > @@ -21,8 +21,15 @@ properties:
> > - adi,ad7190
> > - adi,ad7192
> > - adi,ad7193
> > + - adi,ad7194
> > - adi,ad7195
> >
> > + "#address-cells":
> > + const: 1
> > +
> > + "#size-cells":
> > + const: 0
> > +
> > reg:
> > maxItems: 1
> >
> > @@ -89,6 +96,30 @@ properties:
> > description: see Documentation/devicetree/bindings/iio/adc/adc.yaml
> > type: boolean
> >
> > +patternProperties:
> > + "^channel@[0-9a-z]+$":
>
> Unit-addresses are hex (typically). So something like:
>
> '^channel@(100|[0-9a-f]{1,2})$'
>
> > + type: object
> > + $ref: adc.yaml
> > + unevaluatedProperties: false
> > +
> > + properties:
> > + reg:
> > + description: The channel index.
> > + minimum: 1
> > + maximum: 256
>
> Why not 0 based?
>
>
> > +
> > + diff-channels:
> > + description: |
>
> Don't need '|' if no formatting.
>
> > + Both inputs can be connected to pins AIN1 to AIN16 by choosing the
> > + appropriate value from 1 to 16.
> > + items:
> > + minimum: 1
> > + maximum: 16
> > +
> > + required:
> > + - reg
> > + - diff-channels
>
> Single ended modes aren't supported?
To follow up on this.
For single ended only devices we just let reg reference the the channel.
For differential channels that never worked (because there was a pair).
So for mixed devices it's a bit of a mess.
I'd be happy if we cleaned that up by adding a binding alongside
diff-channels that was simply channel.
For single ended only devices it would be optional but it would make
this device and similar easier to describe.
We can wrap it up in a helper function that queries channel first
and falls back to reg if it isn't there.
Maybe could call it single-channel to make it obvious it's an either
or with diff-channels.
With hindsight we could have just made that take 1 or 2 elements and
given it a generic name from the start. Ah the wonder if retro designing
interfaces... :(
New element in adc.yaml would looks something like.
single-channel:
$ref: /schemas/types.yaml#/definitions/uint32
description:
When devices combine single and differential channels, allow
the channel for a single element to be specified, independent
of reg (as for differentila channels). If this and
diff-channels are not present reg shall be used instead.
Jonathan
>
> > +
> > required:
> > - compatible
> > - reg
> > @@ -103,6 +134,17 @@ required:
> >
> > allOf:
> > - $ref: /schemas/spi/spi-peripheral-props.yaml#
> > + - if:
> > + properties:
> > + compatible:
> > + enum:
> > + - adi,ad7190
> > + - adi,ad7192
> > + - adi,ad7193
> > + - adi,ad7195
> > + then:
> > + patternProperties:
> > + "^channel@[0-9a-z]+$": false
> >
> > unevaluatedProperties: false
> >
> > @@ -133,3 +175,38 @@ examples:
> > adi,burnout-currents-enable;
> > };
> > };
> > + - |
> > + spi {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + adc@0 {
> > + compatible = "adi,ad7194";
> > + reg = <0>;
> > +
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + spi-max-frequency = <1000000>;
> > + spi-cpol;
> > + spi-cpha;
> > + clocks = <&ad7192_mclk>;
> > + clock-names = "mclk";
> > + interrupts = <25 0x2>;
> > + interrupt-parent = <&gpio>;
> > + aincom-supply = <&aincom>;
> > + dvdd-supply = <&dvdd>;
> > + avdd-supply = <&avdd>;
> > + vref-supply = <&vref>;
> > +
> > + channel@1 {
> > + reg = <1>;
> > + diff-channels = <1 6>;
> > + };
> > +
> > + channel@2 {
> > + reg = <2>;
> > + diff-channels = <16 5>;
> > + };
> > + };
> > + };
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2024-04-20 10:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 17:00 [PATCH v6 0/5] iio: adc: ad7192: Add AD7194 support Alisa-Dariana Roman
2024-04-17 17:00 ` [PATCH v6 1/5] iio: adc: ad7192: Use standard attribute Alisa-Dariana Roman
2024-04-20 10:37 ` Jonathan Cameron
2024-04-17 17:00 ` [PATCH v6 2/5] dt-bindings: iio: adc: ad7192: Add aincom supply Alisa-Dariana Roman
2024-04-19 21:35 ` Rob Herring
2024-04-17 17:00 ` [PATCH v6 3/5] " Alisa-Dariana Roman
2024-04-17 17:08 ` Andy Shevchenko
2024-04-20 10:42 ` Jonathan Cameron
2024-04-17 17:00 ` [PATCH v6 4/5] dt-bindings: iio: adc: ad7192: Add AD7194 support Alisa-Dariana Roman
2024-04-18 14:40 ` Rob Herring
2024-04-20 10:52 ` Jonathan Cameron [this message]
2024-04-17 17:00 ` [PATCH v6 5/5] " Alisa-Dariana Roman
2024-04-17 17:06 ` Andy Shevchenko
2024-04-20 10:55 ` Jonathan Cameron
2024-04-20 11:02 ` 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=20240420115203.1a5783b3@jic23-huawei \
--to=jic23@kernel.org \
--cc=alexandru.tachici@analog.com \
--cc=alisa.roman@analog.com \
--cc=alisadariana@gmail.com \
--cc=andy@kernel.org \
--cc=bigunclemax@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=fr0st61te@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=liambeguin@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=marcus.folkesson@gmail.com \
--cc=michael.hennerich@analog.com \
--cc=nuno.sa@analog.com \
--cc=okan.sahin@analog.com \
--cc=robh@kernel.org \
--cc=schnelle@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.