From: Rob Herring <robh@kernel.org>
To: Sean Nyekjaer <sean@geanix.com>
Cc: jic23@kernel.org, linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] dt-bindings: iio: accel: fxls8962af: add bindings
Date: Thu, 15 Apr 2021 10:28:32 -0500 [thread overview]
Message-ID: <20210415152832.GA1433608@robh.at.kernel.org> (raw)
In-Reply-To: <20210415114614.1071928-2-sean@geanix.com>
On Thu, Apr 15, 2021 at 01:46:14PM +0200, Sean Nyekjaer wrote:
> Add devicetree binding for the NXP FXLS8962AF/FXLS8962AF
> accelerometer sensor.
>
> Signed-off-by: Sean Nyekjaer <sean@geanix.com>
> ---
> .../bindings/iio/accel/nxp,fxls8962af.yaml | 66 +++++++++++++++++++
> 1 file changed, 66 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/accel/nxp,fxls8962af.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/accel/nxp,fxls8962af.yaml b/Documentation/devicetree/bindings/iio/accel/nxp,fxls8962af.yaml
> new file mode 100644
> index 000000000000..8cf099c75d1f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/accel/nxp,fxls8962af.yaml
> @@ -0,0 +1,66 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/accel/nxp,fxls8962af.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NXP FXLS8962AF/FXLS8964AF Accelerometer driver
> +
> +maintainers:
> + - Sean Nyekjaer <sean@geanix.com>
> +
> +description: |
> + NXP FXLS8962AF/FXLS8964AF Accelerometer driver that supports
> + SPI and I2C interface.
> + https://www.nxp.com/docs/en/data-sheet/FXLS8962AF.pdf
> + https://www.nxp.com/docs/en/data-sheet/FXLS8964AF.pdf
> +
> +properties:
> + compatible:
> + oneOf:
> + - items:
> + - const: nxp,fxls8962af
> + - const: nxp,fxls8964af
> + - enum:
> + - nxp,fxls8962af
> + - nxp,fxls8964af
That's needlessly complicated. Either nxp,fxls8962af has a fallback or
it doesn't.
blank line needed here too.
> + reg:
> + maxItems: 1
> +
> + vdd-supply:
> + description: phandle to the regulator that provides power to the accelerometer
> +
> + spi-max-frequency: true
> +
> + interrupts:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + i2c0 {
> + /* Example for a I2C device node */
> + accelerometer@2a {
> + compatible = "nxp,fxls8962af";
> + reg = <0x62>;
> + interrupt-parent = <&gpio0>;
> + interrupts = <0 IRQ_TYPE_LEVEL_HIGH>;
> + };
> + };
> + - |
> + spi0 {
> + /* Example for a SPI device node */
> + accelerometer@0 {
> + compatible = "nxp,fxls8962af";
> + reg = <0>;
> + spi-max-frequency = <4000000>;
> + interrupt-parent = <&gpio0>;
> + interrupts = <0 IRQ_TYPE_LEVEL_HIGH>;
> + };
> + };
> --
> 2.31.0
>
next prev parent reply other threads:[~2021-04-15 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 11:46 [RFC PATCH 1/2] iio: accel: add support for FXLS8962AF/FXLS8964AF accelerometers Sean Nyekjaer
2021-04-15 11:46 ` [RFC PATCH 2/2] dt-bindings: iio: accel: fxls8962af: add bindings Sean Nyekjaer
2021-04-15 15:25 ` Rob Herring
2021-04-15 15:28 ` Rob Herring [this message]
2021-04-15 12:50 ` [RFC PATCH 1/2] iio: accel: add support for FXLS8962AF/FXLS8964AF accelerometers Lars-Peter Clausen
2021-04-15 17:53 ` Sean Nyekjaer
2021-04-15 15:10 ` Sa, Nuno
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=20210415152832.GA1433608@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=sean@geanix.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).