From: David Lechner <dlechner@baylibre.com>
To: Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: "Michael Hennerich" <michael.hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 2/4] dt-bindings: iio: adc: add AD4695 and similar ADCs
Date: Tue, 18 Jun 2024 14:29:10 -0500 [thread overview]
Message-ID: <187da75c-9af3-42a9-b31e-be731aaf63d2@baylibre.com> (raw)
In-Reply-To: <20240617-iio-adc-ad4695-v2-2-63ef6583f25d@baylibre.com>
On 6/17/24 2:53 PM, David Lechner wrote:
> Add device tree bindings for AD4695 and similar ADCs.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
> ---
>
...
> +
> + interrupts:
> + minItems: 1
> + items:
> + - description:
> + Signal coming from the BSY_ALT_GP0 or GP3 pin that indicates a busy
> + condition.
> + - description:
> + Signal coming from the BSY_ALT_GP0 or GP2 pin that indicates an alert
> + condition.
> +
> + interrupt-names:
> + minItems: 1
> + items:
> + - const: busy
> + - const: alert
> +
Since the interrupt can come from two different pins, it seems like we would
need an extra property to specify this. Is there a standard way to do this?
Otherwise I will add something like:
adi,busy-on-gp3:
$ref: /schemas/types.yaml#/definitions/flag
description:
When present, the busy interrupt is coming from the GP3 pin, otherwise
the interrupt is coming from the BSY_ALT_GP0 pin.
adi,alert-on-gp2:
$ref: /schemas/types.yaml#/definitions/flag
description:
When present, the alert interrupt is coming from the GP2 pin, otherwise
the interrupt is coming from the BSY_ALT_GP0 pin.
> +
> +patternProperties:
> + "^channel@[0-9a-f]$":
> + type: object
> + $ref: adc.yaml
> + unevaluatedProperties: false
> + description:
> + Describes each individual channel. In addition the properties defined
> + below, bipolar from adc.yaml is also supported.
> +
> + properties:
> + reg:
> + maximum: 15
> +
> + diff-channels:
> + description:
> + Describes inputs used for differential channels. The first value must
> + be an even numbered input and the second value must be the next
> + consecutive odd numbered input.
> + items:
> + - minimum: 0
> + maximum: 14
> + multipleOf: 2
> + - minimum: 1
> + maximum: 15
> + not:
> + multipleOf: 2
After some more testing, it turns out that I misunderstood the datasheet and
this isn't actually fully differential, but rather pseudo-differential.
So when pairing with the next pin, it is similar to pairing with the COM pin
where the negative input pin is connected to a constant voltage source.
> +
> + single-channel:
> + minimum: 0
> + maximum: 15
> +
> + common-mode-channel:
> + description:
> + Describes the common mode channel for single channels. 0 is REFGND
> + and 1 is COM. Macros are available for these values in
> + dt-bindings/iio/adi,ad4695.h.
> + minimum: 0
> + maximum: 1
> + default: 0
So I'm thinking the right thing to do here go back to using reg and the INx
number and only have common-mode-channel (no diff-channels or single-channel).
common-mode-channel will need to be changed to allow INx numbers in addition
to COM and REFGND.
This means that [PATCH v2 1/4] "dt-bindings: iio: adc: add common-mode-channel
dependency" would be wrong since we would be using common-mode-channel without
single-channel.
It also means we will need an optional in1-supply: true for all odd numbered
inputs.
next prev parent reply other threads:[~2024-06-18 19:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 19:53 [PATCH v2 0/4] iio: adc: ad4695: new driver for AD4695 and similar ADCs David Lechner
2024-06-17 19:53 ` [PATCH v2 1/4] dt-bindings: iio: adc: add common-mode-channel dependency David Lechner
2024-06-18 19:47 ` David Lechner
2024-06-17 19:53 ` [PATCH v2 2/4] dt-bindings: iio: adc: add AD4695 and similar ADCs David Lechner
2024-06-17 21:30 ` Rob Herring (Arm)
2024-06-17 22:06 ` David Lechner
2024-06-18 18:00 ` Conor Dooley
2024-06-24 14:35 ` Rob Herring
2024-06-18 19:29 ` David Lechner [this message]
2024-06-23 16:39 ` Jonathan Cameron
2024-06-24 14:36 ` David Lechner
2024-06-24 17:52 ` Jonathan Cameron
2024-06-17 19:53 ` [PATCH v2 3/4] iio: adc: ad4695: Add driver for " David Lechner
2024-06-23 16:43 ` Jonathan Cameron
2024-06-17 19:53 ` [PATCH v2 4/4] Documentation: iio: Document ad4695 driver David Lechner
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=187da75c-9af3-42a9-b31e-be731aaf63d2@baylibre.com \
--to=dlechner@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=nuno.sa@analog.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;
as well as URLs for NNTP newsgroup(s).