From: Jonathan Cameron <jic23@kernel.org>
To: "Nuno Sá" <nuno.sa@analog.com>
Cc: <linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexandru Ardelean <alexandru.ardelean@analog.com>,
Michael Hennerich <Michael.Hennerich@analog.com>
Subject: Re: [PATCH 5/5] dt-bindings: iio: Add adis16475 documentation
Date: Tue, 3 Mar 2020 21:10:45 +0000 [thread overview]
Message-ID: <20200303211045.31f977bb@archlinux> (raw)
In-Reply-To: <20200225124152.270914-6-nuno.sa@analog.com>
On Tue, 25 Feb 2020 13:41:52 +0100
Nuno Sá <nuno.sa@analog.com> wrote:
> Document the ADIS16475 device devicetree bindings.
>
> Signed-off-by: Nuno Sá <nuno.sa@analog.com>
One thing inline on the burst mode stuff.
Thanks,
Jonathan
> ---
> .../bindings/iio/imu/adi,adis16475.yaml | 130 ++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 131 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/imu/adi,adis16475.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/imu/adi,adis16475.yaml b/Documentation/devicetree/bindings/iio/imu/adi,adis16475.yaml
> new file mode 100644
> index 000000000000..c0f2146e000c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/imu/adi,adis16475.yaml
> @@ -0,0 +1,130 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/imu/adi,adis16475.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Analog Devices ADIS16475 and similar IMUs
> +
> +maintainers:
> + - Nuno Sá <nuno.sa@analog.com>
> +
> +description: |
> + Analog Devices ADIS16475 and similar IMUs
> + https://www.analog.com/media/en/technical-documentation/data-sheets/ADIS16475.pdf
> +
> +properties:
> + compatible:
> + enum:
> + - adi,adis16475-1
> + - adi,adis16475-2
> + - adi,adis16475-3
> + - adi,adis16477-1
> + - adi,adis16477-2
> + - adi,adis16477-3
> + - adi,adis16470
> + - adi,adis16465-1
> + - adi,adis16465-2
> + - adi,adis16465-3
> + - adi,adis16467-1
> + - adi,adis16467-2
> + - adi,adis16467-3
> + - adi,adis16500
> + - adi,adis16505-1
> + - adi,adis16505-2
> + - adi,adis16505-3
> + - adi,adis16507-1
> + - adi,adis16507-2
> + - adi,adis16507-3
> +
> + reg:
> + maxItems: 1
> +
> + spi-cpha: true
> +
> + spi-cpol: true
> +
> + spi-max-frequency:
> + maximum: 2000000
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + oneOf:
> + - const: sync
> + - const: direct-sync
> + - const: pulse-sync
> + - const: scaled-sync
> +
> + reset-gpios:
> + description:
> + Must be the device tree identifier of the RESET pin. If specified,
> + it will be asserted during driver probe. As the line is active low,
> + it should be marked GPIO_ACTIVE_LOW.
> + maxItems: 1
> +
> + adi,scaled-output-hz:
> + description:
> + This property must be present if the clock mode is scaled-sync through
> + clock-names property. In this mode, the input clock can have a range
> + of 1Hz to 128HZ which must be scaled to originate an allowable sample
> + rate. This property specifies that rate.
> + minimum: 1900
> + maximum: 2100
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - spi-cpha
> + - spi-cpol
> +
> +if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - adi,adis16500
> + - adi,adis16505-1
> + - adi,adis16505-2
> + - adi,adis16505-3
> + - adi,adis16507-1
> + - adi,adis16507-2
> + - adi,adis16507-3
> +
> +then:
> + properties:
> + clock-names:
> + oneOf:
> + - const: sync
> + - const: direct-sync
> + - const: scaled-sync
> +
> + adi,burst32-enable:
> + description:
> + Enable burst32 mode. In this mode, a burst reading contains calibrated
> + gyroscope and accelerometer data in 32-bit format.
Why is this in DT? Is it not a runtime decision
(ideally automatically selected)
> + type: boolean
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + adis16475: adis16475-3@0 {
> + compatible = "adi,adis16475-3";
> + reg = <0>;
> + spi-cpha;
> + spi-cpol;
> + spi-max-frequency = <2000000>;
> + interrupts = <4 IRQ_TYPE_EDGE_RISING>;
> + interrupt-parent = <&gpio>;
> + };
> + };
> +...
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f11262f1f3bb..f8ccc92ab378 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1015,6 +1015,7 @@ W: http://ez.analog.com/community/linux-device-drivers
> S: Supported
> F: drivers/iio/imu/adis16475.c
> F: Documentation/ABI/testing/sysfs-bus-iio-imu-adis16475
> +F: Documentation/devicetree/bindings/iio/imu/adi,adis16475.yaml
>
> ANALOG DEVICES INC ADM1177 DRIVER
> M: Beniamin Bia <beniamin.bia@analog.com>
next prev parent reply other threads:[~2020-03-03 21:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 12:41 [PATCH 0/5] Support ADIS16475 and similar IMUs Nuno Sá
2020-02-25 12:41 ` [PATCH 1/5] iio: imu: adis: Add Managed device functions Nuno Sá
2020-03-03 20:38 ` Jonathan Cameron
2020-03-04 17:28 ` Sa, Nuno
2020-02-25 12:41 ` [PATCH 2/5] iio: imu: adis: Add irq mask variable Nuno Sá
2020-03-03 20:40 ` Jonathan Cameron
2020-03-04 17:29 ` Sa, Nuno
2020-02-25 12:41 ` [PATCH 3/5] iio: adis: Add adis_update_bits() APIs Nuno Sá
2020-03-03 20:48 ` Jonathan Cameron
2020-03-04 17:32 ` Sa, Nuno
2020-02-25 12:41 ` [PATCH 4/5] iio: imu: Add support for adis16475 Nuno Sá
2020-03-03 21:08 ` Jonathan Cameron
2020-03-04 17:59 ` Sa, Nuno
2020-03-05 9:58 ` Sa, Nuno
2020-03-05 10:39 ` Lars-Peter Clausen
2020-03-07 11:25 ` Jonathan Cameron
2020-03-07 11:27 ` Jonathan Cameron
2020-02-25 12:41 ` [PATCH 5/5] dt-bindings: iio: Add adis16475 documentation Nuno Sá
2020-03-02 22:22 ` Rob Herring
2020-03-03 9:43 ` Sa, Nuno
2020-03-03 9:59 ` Sa, Nuno
2020-03-03 16:34 ` Rob Herring
2020-03-04 17:25 ` Sa, Nuno
2020-03-03 21:10 ` Jonathan Cameron [this message]
2020-03-04 18:00 ` Sa, Nuno
2020-03-05 10:34 ` Lars-Peter Clausen
2020-03-05 12:27 ` Sa, Nuno
2020-03-05 12:43 ` Lars-Peter Clausen
2020-03-05 13:04 ` Sa, Nuno
2020-03-07 11:33 ` Jonathan Cameron
2020-03-07 20:47 ` nunojsa
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=20200303211045.31f977bb@archlinux \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.ardelean@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nuno.sa@analog.com \
--cc=pmeerw@pmeerw.net \
--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 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.