From: Jonathan Cameron <jic23@kernel.org>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
Conor Dooley <conor@kernel.org>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: iio: adc: ti-ads1298: Add driver
Date: Wed, 20 Dec 2023 13:59:13 +0000 [thread overview]
Message-ID: <20231220135913.50edaa7f@jic23-huawei> (raw)
In-Reply-To: <ca96c5d2-33aa-496b-b85f-531e628cb6d6@topic.nl>
> >>> + avdd-supply:
> >>> + description:
> >>> + Analog power supply, voltage between AVDD and AVSS. When providing a
> >>> + symmetric +/- 2.5V, the regulator should report 5V.
> >
> > Any precedence in tree for doing this? I thought we had bindings that required negative
> > supplies to be specified separately if present - so this would need to be 2
> > supplies. e.g.
> > https://elixir.bootlin.com/linux/v6.7-rc5/source/Documentation/devicetree/bindings/iio/adc/ti,adc12138.yaml#L37
> >
>
> Given that some serious thought...
>
> Splitting into positive and negative supplies would make sense if the chip
> would have terminals for positive, negative and ground. Which it does not
> have, there's only positive and negative (which the datasheet misleadingly
> calls "analog ground").
>
> The analog voltage supplied to the chip has no effect on its outputs, the
> analog supply must be connected between the AVDD and AVSS pins. Its relation
> to analog ground is not relevant, so whether the voltages are +5/0 or
> +2.5/-2.5 or +4/-1 or whatever does not affect the output of the ADC, which
> only reports the difference between its "p" and "n" input signals. It only
> affects the range of the inputs, as it cannot measure (p or n) outside the
> analog supply.
>
Ah. Not having seen any isolators, I assumed this device was running
against a common ground with the digital side of things.
AVSS to DGND is between -3 and 0.2 so I think there is a ground even if it's
not directly connected.
Given this only operates in differential mode the fact both signals are
referenced to +-vref which is from VASS doesn't matter in the end and any
offset goes away.
So yes I think I agree. This should be a single supply.
Jonathan
next prev parent reply other threads:[~2023-12-20 13:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.618139b3-8cb2-4e4c-9283-9e3787c70105@emailsignatures365.codetwo.com>
2023-12-13 9:47 ` [PATCH 1/2] dt-bindings: iio: adc: ti-ads1298: Add driver Mike Looijmans
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.27993507-256d-4b05-88df-c8643e7f1a68@emailsignatures365.codetwo.com>
2023-12-13 9:47 ` [PATCH 2/2] " Mike Looijmans
2023-12-13 14:55 ` Andy Shevchenko
2024-01-31 16:10 ` Mike Looijmans
2024-02-01 11:38 ` Andy Shevchenko
2024-02-04 13:06 ` Jonathan Cameron
2023-12-14 11:06 ` Jonathan Cameron
2024-01-31 16:24 ` Mike Looijmans
2024-02-04 13:32 ` Jonathan Cameron
2023-12-13 16:23 ` [PATCH 1/2] dt-bindings: " Conor Dooley
2023-12-14 10:22 ` Jonathan Cameron
2023-12-20 10:42 ` Mike Looijmans
2023-12-20 13:59 ` Jonathan Cameron [this message]
2023-12-14 11:11 ` Jonathan Cameron
2023-12-20 10:58 ` Mike Looijmans
2023-12-20 14:00 ` 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=20231220135913.50edaa7f@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.looijmans@topic.nl \
--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;
as well as URLs for NNTP newsgroup(s).