From: Rui Miguel Silva <rui.silva@linaro.org>
To: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Shawn Guo <shawnguo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
Rui Miguel Silva <rui.silva@linaro.org>
Subject: [PATCH v3 1/6] iio: gyro: add DT bindings to fxas21002c
Date: Wed, 13 Mar 2019 18:39:57 +0000 [thread overview]
Message-ID: <20190313184002.2501-2-rui.silva@linaro.org> (raw)
In-Reply-To: <20190313184002.2501-1-rui.silva@linaro.org>
Add device tree bindings for the FXAS21002C gyroscope.
Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
---
.../bindings/iio/gyroscope/nxp,fxas21002c.txt | 26 +++++++++++++++++++
1 file changed, 26 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/gyroscope/nxp,fxas21002c.txt
diff --git a/Documentation/devicetree/bindings/iio/gyroscope/nxp,fxas21002c.txt b/Documentation/devicetree/bindings/iio/gyroscope/nxp,fxas21002c.txt
new file mode 100644
index 000000000000..68b4cd283d1d
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/gyroscope/nxp,fxas21002c.txt
@@ -0,0 +1,26 @@
+* NXP FXAS21002C Gyroscope device tree bindings
+
+http://www.nxp.com/products/sensors/gyroscopes/3-axis-digital-gyroscope:FXAS21002C
+
+Required properties:
+ - compatible : should be "nxp,fxas21002c"
+ - reg : the I2C address of the sensor or SPI chip select number for the
+ device.
+ - vdd-supply: phandle to the regulator that provides power to the sensor.
+ - vddio-supply: phandle to the regulator that provides power to the bus.
+
+Optional properties:
+ - reset-gpios : gpio used to reset the device, see gpio/gpio.txt
+ - interrupts : device support 2 interrupts, INT1 and INT2.
+ See interrupt-controller/interrupts.txt
+ - interrupt-names: should contain "INT1" or "INT2", the gyroscope interrupt
+ line in use.
+
+Example:
+
+gyroscope@20 {
+ compatible = "nxp,fxas21002c";
+ reg = <0x20>;
+ vdd-supply = <®_peri_3p15v>;
+ vddio-supply = <®_peri_3p15v>;
+};
--
2.20.1
next prev parent reply other threads:[~2019-03-13 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 18:39 [PATCH v3 0/6] iio: gyro: add fxas21002c driver Rui Miguel Silva
2019-03-13 18:39 ` Rui Miguel Silva [this message]
2019-03-14 19:09 ` [PATCH v3 1/6] iio: gyro: add DT bindings to fxas21002c Tomasz Duszynski
2019-03-18 8:28 ` Rui Miguel Silva
2019-03-13 18:39 ` [PATCH v3 2/6] iio: gyro: add core driver for fxas21002c Rui Miguel Silva
2019-03-16 16:29 ` Jonathan Cameron
2019-03-18 8:29 ` Rui Miguel Silva
2019-03-13 18:39 ` [PATCH v3 3/6] iio: gyro: fxas21002c: add i2c driver Rui Miguel Silva
2019-03-14 19:38 ` Tomasz Duszynski
2019-03-13 18:40 ` [PATCH v3 4/6] iio: gyro: fxas21002c: add spi driver Rui Miguel Silva
2019-03-14 19:31 ` Tomasz Duszynski
2019-03-13 18:40 ` [PATCH v3 5/6] ARM: dts: imx7s-warp: add fxas21002c gyroscope Rui Miguel Silva
2019-03-13 18:40 ` [PATCH v3 6/6] MAINTAINERS: add entry for fxas21002c gyro driver Rui Miguel Silva
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=20190313184002.2501-2-rui.silva@linaro.org \
--to=rui.silva@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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).