From: Rob Herring <robh@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
devicetree@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Michael Hennerich <michael.hennerich@analog.com>
Subject: Re: [PATCH v2 2/2] dt-bindings:iio:adc:adi,ad7474: Add missing binding document
Date: Fri, 9 Apr 2021 11:08:41 -0500 [thread overview]
Message-ID: <20210409160841.GA3735818@robh.at.kernel.org> (raw)
In-Reply-To: <20210405162325.627977-3-jic23@kernel.org>
On Mon, Apr 05, 2021 at 05:23:25PM +0100, Jonathan Cameron wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> This binding covers class of simple SPI ADCs which only provide
> data output - they don't have MOSI pin.
>
> The only real variation between them is over how many supplies they
> use and which one is used for the reference.
>
> Michael listed as maintainer for this one as it is his driver and
> falls under the catch all MAINTAINERS entry for ADI devices.
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Cc: Michael Hennerich <michael.hennerich@analog.com>
> ---
> .../bindings/iio/adc/adi,ad7476.yaml | 173 ++++++++++++++++++
> 1 file changed, 173 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad7476.yaml b/Documentation/devicetree/bindings/iio/adc/adi,ad7476.yaml
> new file mode 100644
> index 000000000000..bebf5b435947
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/adi,ad7476.yaml
> @@ -0,0 +1,173 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +# Copyright 2019 Analog Devices Inc.
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/adc/adi,ad7476.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: AD7476 and similar simple SPI ADCs from multiple manufacturers.
> +
> +maintainers:
> + - Michael Hennerich <michael.hennerich@analog.com>
> +
> +description: |
> + A lot of simple SPI ADCs have very straight forward interfaces.
> + They typically don't provide a MOSI pin, simply reading out data
> + on MISO when the clock toggles.
> +
> +properties:
> + compatible:
> + enum:
> + - adi,ad7091
> + - adi,ad7091r
> + - adi,ad7273
> + - adi,ad7274
> + - adi,ad7276
> + - adi,ad7277
> + - adi,ad7278
> + - adi,ad7466
> + - adi,ad7467
> + - adi,ad7468
> + - adi,ad7475
> + - adi,ad7476
> + - adi,ad7476a
> + - adi,ad7477
> + - adi,ad7477a
> + - adi,ad7478
> + - adi,ad7478a
> + - adi,ad7495
> + - adi,ad7910
> + - adi,ad7920
> + - adi,ad7940
> + - ti,adc081s
> + - ti,adc101s
> + - ti,adc121s
> + - ti,ads7866
> + - ti,ads7867
> + - ti,ads7868
> + - lltc,ltc2314-14
> +
> + reg:
> + maxItems: 1
> +
> + vcc-supply:
> + description:
> + Main powersupply voltage for the chips, sometimes referred to as VDD on
> + datasheets. If there is no separate vref-supply, then this is needed
> + to establish channel scaling.
> +
> + vdrive-supply:
> + description:
> + Some devices have separate supply for their digital control side.
> +
> + vref-supply:
> + description:
> + Some devices have a specific reference voltage supplied on a different pin
> + to the other supplies. Needed to be able to establish channel scaling
> + unless there is also an internal reference available (e.g. ad7091r)
> +
> + spi-max-frequency: true
> +
> + adi,conversion-start-gpios:
> + description: A GPIO used to trigger the start of a conversion
maxItems: 1
With that,
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2021-04-09 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 16:23 [PATCH v2 0/2] iio:adc:ad7476: Regulator support and binding doc Jonathan Cameron
2021-04-05 16:23 ` [PATCH v2 1/2] iio:adc:ad7476: Handle the different regulators used by various parts Jonathan Cameron
2021-04-05 17:52 ` Lars-Peter Clausen
2021-04-05 21:37 ` kernel test robot
2021-04-05 16:23 ` [PATCH v2 2/2] dt-bindings:iio:adc:adi,ad7474: Add missing binding document Jonathan Cameron
2021-04-09 16: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=20210409160841.GA3735818@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=michael.hennerich@analog.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).