From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-i2c@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>, Wolfram Sang <wsa@kernel.org>,
Peter Rosin <peda@axentia.se>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Rob Herring <robh@kernel.org>,
Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>,
Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH v2 2/3] dt-bindings:iio:imu:invensense,mpu6050: txt to yaml conversion
Date: Sun, 13 Dec 2020 13:19:59 +0000 [thread overview]
Message-ID: <20201213131959.0974f197@archlinux> (raw)
In-Reply-To: <20201128173343.390165-3-jic23@kernel.org>
On Sat, 28 Nov 2020 17:33:42 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> As Rob Herring suggested, this no long requires the explicit
> i2c-gate binding, but instead just used i2c-controller.yaml
> directly.
>
> 2 prior examples combinded into one as a single example can show
> all of the binding elements as long as the right part is selected.
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Cc: Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>
> Cc: Wolfram Sang <wsa@the-dreams.de>
> Cc: Peter Rosin <peda@axentia.se>
> Link: https://lore.kernel.org/r/20201031181801.742585-3-jic23@kernel.org
Applied to the togreg branch of iio.git
> ---
> .../bindings/iio/imu/inv_mpu6050.txt | 67 ------------
> .../bindings/iio/imu/invensense,mpu6050.yaml | 103 ++++++++++++++++++
> 2 files changed, 103 insertions(+), 67 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/iio/imu/inv_mpu6050.txt b/Documentation/devicetree/bindings/iio/imu/inv_mpu6050.txt
> deleted file mode 100644
> index f2f64749e818..000000000000
> --- a/Documentation/devicetree/bindings/iio/imu/inv_mpu6050.txt
> +++ /dev/null
> @@ -1,67 +0,0 @@
> -InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS MotionTracking Device
> -
> -http://www.invensense.com/mems/gyro/mpu6050.html
> -
> -Required properties:
> - - compatible : should be one of
> - "invensense,mpu6000"
> - "invensense,mpu6050"
> - "invensense,mpu6500"
> - "invensense,mpu6515"
> - "invensense,mpu9150"
> - "invensense,mpu9250"
> - "invensense,mpu9255"
> - "invensense,icm20608"
> - "invensense,icm20609"
> - "invensense,icm20689"
> - "invensense,icm20602"
> - "invensense,icm20690"
> - "invensense,iam20680"
> - - reg : the I2C address of the sensor
> - - interrupts: interrupt mapping for IRQ. It should be configured with flags
> - IRQ_TYPE_LEVEL_HIGH, IRQ_TYPE_EDGE_RISING, IRQ_TYPE_LEVEL_LOW or
> - IRQ_TYPE_EDGE_FALLING.
> -
> - Refer to interrupt-controller/interrupts.txt for generic interrupt client node
> - bindings.
> -
> -Optional properties:
> - - vdd-supply: regulator phandle for VDD supply
> - - vddio-supply: regulator phandle for VDDIO supply
> - - mount-matrix: an optional 3x3 mounting rotation matrix
> - - i2c-gate node. These devices also support an auxiliary i2c bus. This is
> - simple enough to be described using the i2c-gate binding. See
> - i2c/i2c-gate.txt for more details.
> -
> -Example:
> - mpu6050@68 {
> - compatible = "invensense,mpu6050";
> - reg = <0x68>;
> - interrupt-parent = <&gpio1>;
> - interrupts = <18 IRQ_TYPE_EDGE_RISING>;
> - mount-matrix = "-0.984807753012208", /* x0 */
> - "0", /* y0 */
> - "-0.173648177666930", /* z0 */
> - "0", /* x1 */
> - "-1", /* y1 */
> - "0", /* z1 */
> - "-0.173648177666930", /* x2 */
> - "0", /* y2 */
> - "0.984807753012208"; /* z2 */
> - };
> -
> -
> - mpu9250@68 {
> - compatible = "invensense,mpu9250";
> - reg = <0x68>;
> - interrupt-parent = <&gpio3>;
> - interrupts = <21 IRQ_TYPE_LEVEL_HIGH>;
> - i2c-gate {
> - #address-cells = <1>;
> - #size-cells = <0>;
> - ax8975@c {
> - compatible = "ak,ak8975";
> - reg = <0x0c>;
> - };
> - };
> - };
> diff --git a/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml b/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml
> new file mode 100644
> index 000000000000..9268b6ca2afe
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml
> @@ -0,0 +1,103 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/imu/invensense,mpu6050.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS MotionTracking Device
> +
> +maintainers:
> + - Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>
> +
> +description: |
> + These devices support both I2C and SPI bus interfaces.
> +
> +properties:
> + compatible:
> + enum:
> + - invensense,iam20680
> + - invensense,icm20608
> + - invensense,icm20609
> + - invensense,icm20689
> + - invensense,icm20602
> + - invensense,icm20690
> + - invensense,mpu6000
> + - invensense,mpu6050
> + - invensense,mpu6500
> + - invensense,mpu6515
> + - invensense,mpu9150
> + - invensense,mpu9250
> + - invensense,mpu9255
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + spi-max-frequency: true
> +
> + vdd-supply: true
> + vddio-supply: true
> +
> + mount-matrix: true
> +
> + i2c-gate:
> + $ref: /schemas/i2c/i2c-controller.yaml
> + unevaluatedProperties: false
> + description: |
> + These devices also support an auxiliary i2c bus via an i2c-gate.
> +
> +allOf:
> + - if:
> + not:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - invensense,mpu9150
> + - invensense,mpu9250
> + - invensense,mpu9255
> + then:
> + properties:
> + i2c-gate: false
> +
> +additionalProperties: false
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + imu@68 {
> + compatible = "invensense,mpu9250";
> + reg = <0x68>;
> + interrupt-parent = <&gpio3>;
> + interrupts = <21 IRQ_TYPE_LEVEL_HIGH>;
> + mount-matrix = "-0.984807753012208", /* x0 */
> + "0", /* y0 */
> + "-0.173648177666930", /* z0 */
> + "0", /* x1 */
> + "-1", /* y1 */
> + "0", /* z1 */
> + "-0.173648177666930", /* x2 */
> + "0", /* y2 */
> + "0.984807753012208"; /* z2 */
> + i2c-gate {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + magnetometer@c {
> + compatible = "ak,ak8975";
> + reg = <0x0c>;
> + };
> + };
> + };
> + };
> +...
next prev parent reply other threads:[~2020-12-13 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 17:33 [PATCH v2 0/3] dt-bindings: yaml conversion of i2c-gate and IIO users Jonathan Cameron
2020-11-28 17:33 ` [PATCH v2 1/3] dt-bindings:i2c:i2c-gate: txt to yaml conversion Jonathan Cameron
2020-12-08 21:31 ` Rob Herring
2020-11-28 17:33 ` [PATCH v2 2/3] dt-bindings:iio:imu:invensense,mpu6050: " Jonathan Cameron
2020-12-13 13:19 ` Jonathan Cameron [this message]
2020-11-28 17:33 ` [PATCH v2 3/3] dt-bindings:iio:gyro:invensense,mpu3050: txt to yaml format conversion Jonathan Cameron
2020-12-13 13:20 ` 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=20201213131959.0974f197@archlinux \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=jmaneyrol@invensense.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=wsa@kernel.org \
--cc=wsa@the-dreams.de \
/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).