From: Bobby Jones <rjones@gateworks.com>
To: Rob Herring <robh@kernel.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Mark Rutland <mark.rutland@arm.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: imu: add fxos8700 imu binding
Date: Fri, 11 Oct 2019 16:33:29 -0700 [thread overview]
Message-ID: <CALAE=UCcEd_pyjG+80EDBgGKsJfaCM0fvHAwEdnhf5G9-Ns+ig@mail.gmail.com> (raw)
In-Reply-To: <20191011135811.GA23962@bogus>
On Fri, Oct 11, 2019 at 6:58 AM Rob Herring <robh@kernel.org> wrote:
>
> On Thu, Oct 10, 2019 at 10:56:47AM -0700, Robert Jones wrote:
> > This adds documentation for the Freescale FXOS8700 Inertial Measurement Unit
> > device-tree bindings.
> >
> > Signed-off-by: Robert Jones <rjones@gateworks.com>
> > ---
> > .../devicetree/bindings/iio/imu/nxp,fxos8700.yaml | 69 ++++++++++++++++++++++
> > 1 file changed, 69 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/iio/imu/nxp,fxos8700.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/iio/imu/nxp,fxos8700.yaml b/Documentation/devicetree/bindings/iio/imu/nxp,fxos8700.yaml
> > new file mode 100644
> > index 0000000..d33a1cc
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/iio/imu/nxp,fxos8700.yaml
> > @@ -0,0 +1,69 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/iio/imu/fxos8700.yaml#
>
> Documentation/devicetree/bindings/iio/imu/nxp,fxos8700.yaml: $id:
> path/filename 'iio/imu/fxos8700.yaml' doesn't match actual filename
>
> Test your binding with 'make dt_binding_check'.
Sorry about that, I had tried running that check previously but was
struggling through some python environment/set-up problems.
Additionally I did not realize that my path was incomplete until I
read your github's readme line "Ensure ~/.local/bin is in the PATH". I
don't utilize the python install on my machine frequently so I'm not
sure if that should be obvious. It might be helpful to have that line
in the Documentation/devicetree/writing-schema.md as well.
Anyways I've got it running now.
>
>
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Freescale FXOS8700 Inertial Measurement Unit
> > +
> > +maintainers:
> > + - Robert Jones <rjones@gateworks.com>
> > +
> > +description: |
> > + Accelerometer and magnetometer combo device with an i2c and SPI interface.
> > + https://www.nxp.com/products/sensors/motion-sensors/6-axis/digital-motion-sensor-3d-accelerometer-2g-4g-8g-plus-3d-magnetometer:FXOS8700CQ
> > +
> > +properties:
> > + compatible:
> > + enum:
> > + - nxp,fxos8700
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + interrupts:
> > + maxItems: 2
> > +
> > + interrupt-names:
> > + maxItems: 2
> > + items:
> > + - const: INT1
> > + - const: INT2
>
> This doesn't match the example now. You need 'minItems: 1' if you need
> to support 1 or 2 interrupts. If it can be either one, then you need:
>
> items:
> enum: [ INT1, INT2 ]
I'm trying to compare against other .yaml examples in the tree but
without scouring datasheets to find a device with similar interrupt
capabilities I'm just guessing at how this should be defined.
The device has 2 interrupt pins as you've read (INT1 and INT2), and
0-2 of them can be used depending on what's been configured. Given
what you've explained so far would this be the proper definition?:
interrupts:
minItems: 1
maxItems: 2
interrupt-names:
minItems: 1
maxItems: 2
items:
enum:
- INT1
- INT2
Thanks
>
> > +
> > + drive-open-drain:
> > + type: boolean
> > +
> > +required:
> > + - compatible
> > + - reg
> > +
> > +examples:
> > + - |
> > + i2c {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + fxos8700@1e {
> > + compatible = "nxp,fxos8700";
> > + reg = <0x1e>;
> > +
> > + interrupt-parent = <&gpio2>;
> > + interrupts = <7 IRQ_TYPE_EDGE_RISING>;
> > + interrupt-names = "INT1";
> > + };
> > + };
> > + - |
> > + spi {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + fxos8700@1e {
> > + compatible = "nxp,fxos8700";
> > + reg = <0x1e>;
>
> I guess you could have SPI chip select # 30...
Absolutely, and definitely not a hasty copy and paste error :)
>
> > +
> > + interrupt-parent = <&gpio2>;
> > + spi-max-frequency = <1000000>
> > + interrupts = <7 IRQ_TYPE_EDGE_RISING>;
> > + interrupt-names = "INT1";
> > + };
> > + };
> > --
> > 2.9.2
> >
next prev parent reply other threads:[~2019-10-11 23:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 1:28 [PATCH 0/2] iio: imu: add support for FXOS8700 Robert Jones
2019-09-18 1:28 ` [PATCH 1/2] dt-bindings: iio: imu: add fxos8700 imu binding Robert Jones
2019-10-01 11:39 ` Rob Herring
2019-09-18 1:28 ` [PATCH 2/2] io: imu: Add support for the FXOS8700 IMU Robert Jones
2019-10-05 13:10 ` Jonathan Cameron
2019-10-10 1:25 ` [PATCH v2 0/2] iio: imu: add support for FXOS8700 Robert Jones
2019-10-10 1:25 ` [PATCH v2 1/2] dt-bindings: iio: imu: add fxos8700 imu binding Robert Jones
2019-10-10 13:23 ` Rob Herring
2019-10-10 1:25 ` [PATCH v2 2/2] iio: imu: Add support for the FXOS8700 IMU Robert Jones
2019-10-10 17:56 ` [PATCH v3 0/2] iio: imu: add support for FXOS8700 Robert Jones
2019-10-10 17:56 ` [PATCH v3 1/2] dt-bindings: iio: imu: add fxos8700 imu binding Robert Jones
2019-10-11 13:58 ` Rob Herring
2019-10-11 23:33 ` Bobby Jones [this message]
2019-10-14 13:37 ` Rob Herring
2019-10-10 17:56 ` [PATCH v3 2/2] iio: imu: Add support for the FXOS8700 IMU Robert Jones
2019-10-12 13:53 ` Jonathan Cameron
2019-10-14 18:33 ` Bobby Jones
2019-10-14 18:49 ` [PATCH v4 0/2] iio: imu: add support for FXOS8700 Robert Jones
2019-10-14 18:49 ` [PATCH v4 1/2] dt-bindings: iio: imu: add fxos8700 imu binding Robert Jones
2019-10-16 12:55 ` Rob Herring
2019-10-22 9:25 ` Jonathan Cameron
2019-10-14 18:49 ` [PATCH v4 2/2] iio: imu: Add support for the FXOS8700 IMU Robert Jones
2019-10-21 17:15 ` Bobby Jones
2019-10-22 9:25 ` 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='CALAE=UCcEd_pyjG+80EDBgGKsJfaCM0fvHAwEdnhf5G9-Ns+ig@mail.gmail.com' \
--to=rjones@gateworks.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh@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).