From: Jonathan Cameron <jic23@kernel.org>
To: Nishant Malpani <nish.malpani25@gmail.com>
Cc: robh+dt@kernel.org, dragos.bogdan@analog.com,
darius.berghe@analog.com, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: iio: gyro: Add DT binding doc for ADXRS290
Date: Mon, 20 Jul 2020 12:16:33 +0100 [thread overview]
Message-ID: <20200720121633.7a9e5cd7@archlinux> (raw)
In-Reply-To: <20200715092821.14625-1-nish.malpani25@gmail.com>
On Wed, 15 Jul 2020 14:58:21 +0530
Nishant Malpani <nish.malpani25@gmail.com> wrote:
> Add devicetree binding document for ADXRS290, a dual-axis MEMS gyroscope.
>
> Signed-off-by: Nishant Malpani <nish.malpani25@gmail.com>
> ---
> .../bindings/iio/gyroscope/adi,adxrs290.yaml | 52 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 53 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/gyroscope/adi,adxrs290.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/gyroscope/adi,adxrs290.yaml b/Documentation/devicetree/bindings/iio/gyroscope/adi,adxrs290.yaml
> new file mode 100644
> index 000000000000..a997d945fdb0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/gyroscope/adi,adxrs290.yaml
> @@ -0,0 +1,52 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +# Copyright 2020 Analog Devices Inc.
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/gyroscope/adi,adxrs290.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Analog Devices ADXRS290 Dual-Axis MEMS Gyroscope
> +
> +maintainers:
> + - Nishant Malpani <nish.malpani25@gmail.com>
> +
> +description: |
> + Bindings for the Analog Devices ADXRS290 dual-axis MEMS gyroscope device.
> + https://www.analog.com/media/en/technical-documentation/data-sheets/ADXRS290.pdf
> +
> +properties:
> + compatible:
> + enum:
> + - adi,adxrs290
I think we can use const here as only one item currently.
> +
> + reg:
> + maxItems: 1
> +
> + spi-max-frequency:
> + maximum: 5000000
> +
> + spi-cpol: true
> +
> + spi-cpha: true
> +
> +required:
> + - compatible
> + - reg
> + - spi-max-frequency
> + - spi-cpol
> + - spi-cpha
> +
> +examples:
> + - |
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + gyro@0 {
> + compatible = "adi,adxrs290";
> + reg = <0>;
> + spi-max-frequency = <5000000>;
> + spi-cpol;
> + spi-cpha;
> + };
> + };
> +...
> diff --git a/MAINTAINERS b/MAINTAINERS
> index dd02cfc410e8..0bb8ac90fba1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1103,6 +1103,7 @@ M: Nishant Malpani <nish.malpani25@gmail.com>
> L: linux-iio@vger.kernel.org
> S: Supported
> F: drivers/iio/gyro/adxrs290.c
> +F: Documentation/devicetree/bindings/iio/gyroscope/adi,adxrs290.yaml
>
> ANALOG DEVICES INC ASOC CODEC DRIVERS
> M: Lars-Peter Clausen <lars@metafoo.de>
next prev parent reply other threads:[~2020-07-20 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 9:28 [PATCH 2/2] dt-bindings: iio: gyro: Add DT binding doc for ADXRS290 Nishant Malpani
2020-07-20 11:16 ` Jonathan Cameron [this message]
2020-07-21 2:41 ` Rob Herring
2020-07-21 19:11 ` Nishant Malpani
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=20200720121633.7a9e5cd7@archlinux \
--to=jic23@kernel.org \
--cc=darius.berghe@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=dragos.bogdan@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.malpani25@gmail.com \
--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.