devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Rui Miguel Silva <rui.silva@linaro.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>,
	Shawn Guo <shawnguo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/5] iio: gyro: add DT bindings to fxas21002
Date: Wed, 6 Feb 2019 12:53:54 +0000	[thread overview]
Message-ID: <20190206125354.0000214e@huawei.com> (raw)
In-Reply-To: <20190205174333.17672-2-rui.silva@linaro.org>

On Tue, 5 Feb 2019 17:43:29 +0000
Rui Miguel Silva <rui.silva@linaro.org> wrote:

> Add device tree bindings for the FXAS21002 gyroscope.
> 
> Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
> ---
>  .../bindings/iio/gyroscope/fxas2100x.txt       | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/iio/gyroscope/fxas2100x.txt
> 
> diff --git a/Documentation/devicetree/bindings/iio/gyroscope/fxas2100x.txt b/Documentation/devicetree/bindings/iio/gyroscope/fxas2100x.txt
> new file mode 100644
> index 000000000000..df10a60aa533
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/gyroscope/fxas2100x.txt
> @@ -0,0 +1,18 @@
> +* NXP FXAS2100X Gyroscope device tree bindings
> +
> +http://www.nxp.com/products/sensors/gyroscopes/3-axis-digital-gyroscope:FXAS21002C
> +
> +Required properties:
> +  - compatible : should be "nxp,fxas21002"
> +  - reg : the I2C address of the sensor

Given you provide spi support that might need expanding upon...


> +  - vdd-supply: phandle to the regulator that provides power to the sensor.
> +  - vddio-supply: phandle to the regulator that provides power to the bus.
> +
> +Example:
> +
> +fxas21002@20 {
> +	compatible = "nxp,fxas21002";
> +	reg = <0x20>;
> +	vdd-supply = <&reg_peri_3p15v>;
> +	vddio-supply = <&reg_peri_3p15v>;
> +};

  reply	other threads:[~2019-02-06 12:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 17:43 [PATCH v2 0/5] iio: gyro: add fxas2100x driver Rui Miguel Silva
2019-02-05 17:43 ` [PATCH v2 1/5] iio: gyro: add DT bindings to fxas21002 Rui Miguel Silva
2019-02-06 12:53   ` Jonathan Cameron [this message]
2019-02-18 19:39   ` Rob Herring
2019-02-05 17:43 ` [PATCH v2 2/5] iio: gyro: fxas2100x: add core driver for fxas2100x gyroscope Rui Miguel Silva
2019-02-06 13:18   ` Jonathan Cameron
2019-02-07 15:32     ` Rui Miguel Silva
2019-02-05 17:43 ` [PATCH v2 3/5] iio: gyro: fxas2100x: add i2c driver Rui Miguel Silva
2019-02-06 13:19   ` Jonathan Cameron
2019-02-05 17:43 ` [PATCH v2 4/5] iio: gyro: fxas2100x: add spi driver Rui Miguel Silva
2019-02-05 17:43 ` [PATCH v2 5/5] ARM: dts: imx7s-warp: add fxas21002 gyroscope Rui Miguel Silva
2019-02-09 16:14 ` [PATCH v2 0/5] iio: gyro: add fxas2100x driver 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=20190206125354.0000214e@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --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=rui.silva@linaro.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).