From: Jonathan Cameron <jic23@kernel.org>
To: Alex Lanzano <lanzano.alex@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Ramona Gradinariu <ramona.bolboaca13@gmail.com>,
Nuno Sa <nuno.sa@analog.com>,
Jagath Jog J <jagathjog1996@gmail.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: imu: add bmi270 bindings
Date: Sat, 7 Sep 2024 16:47:43 +0100 [thread overview]
Message-ID: <20240907164743.1cb7070e@jic23-huawei> (raw)
In-Reply-To: <20240906165322.1745328-2-lanzano.alex@gmail.com>
On Fri, 6 Sep 2024 12:52:50 -0400
Alex Lanzano <lanzano.alex@gmail.com> wrote:
> Add device tree bindings for the bmi270 IMU
>
> Signed-off-by: Alex Lanzano <lanzano.alex@gmail.com>
Hi Alex
One totally trivial thing inline. If nothing comes up in
driver I'll tidy this up whilst applying
Jonathan
> ---
> .../bindings/iio/imu/bosch,bmi270.yaml | 77 +++++++++++++++++++
> 1 file changed, 77 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/imu/bosch,bmi270.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/imu/bosch,bmi270.yaml b/Documentation/devicetree/bindings/iio/imu/bosch,bmi270.yaml
> new file mode 100644
> index 000000000000..7de35b9bfa2e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/imu/bosch,bmi270.yaml
> @@ -0,0 +1,77 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/imu/bosch,bmi270.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Bosch BMI270 6-Axis IMU
> +
> +maintainers:
> + - Alex Lanzano <lanzano.alex@gmail.com>
> +
> +description: |
> + BMI270 is a 6-axis inertial measurement unit that can measure acceleration and
> + angular velocity. The sensor also supports configurable interrupt events such
> + as motion, step counter, and wrist motion gestures. The sensor can communicate
> + I2C or SPI.
> + https://www.bosch-sensortec.com/products/motion-sensors/imus/bmi270/
> +
> +properties:
> + compatible:
> + const: bosch,bmi270
> +
> + reg:
> + maxItems: 1
> +
> + vdd-supply: true
> + vddio-supply: true
> +
> + interrupts:
> + minItems: 1
> + maxItems: 2
> +
> + interrupt-names:
> + minItems: 1
> + maxItems: 2
> + items:
> + enum:
> + - INT1
> + - INT2
> +
> + drive-open-drain:
> + description:
> + set if the specified interrupt pin should be configured as
pins
Even if they are configurable separately we've previously argued that
it is very unlikely a board designer would want one open drain
and the other push-pull. So simply making the description plural
should be enough.
> + open drain. If not set, defaults to push-pull.
> +
> + mount-matrix:
> + description:
> + an optional 3x3 mounting rotation matrix.
> +
> +required:
> + - compatible
> + - reg
> + - vdd-supply
> + - vddio-supply
> +
> +allOf:
> + - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + imu@68 {
> + compatible = "bosch,bmi270";
> + reg = <0x68>;
> + vdd-supply = <&vdd>;
> + vddio-supply = <&vddio>;
> + interrupt-parent = <&gpio1>;
> + interrupts = <16 IRQ_TYPE_EDGE_RISING>;
> + interrupt-names = "INT1";
> + };
> + };
next prev parent reply other threads:[~2024-09-07 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 16:52 [PATCH v2 0/2] Add I2C driver for Bosch BMI270 IMU Alex Lanzano
2024-09-06 16:52 ` [PATCH v2 1/2] dt-bindings: iio: imu: add bmi270 bindings Alex Lanzano
2024-09-07 9:24 ` Krzysztof Kozlowski
2024-09-07 15:47 ` Jonathan Cameron [this message]
2024-09-08 18:21 ` Alex Lanzano
2024-09-06 16:52 ` [PATCH v2 2/2] iio: imu: Add i2c driver for bmi270 imu Alex Lanzano
2024-09-07 16:08 ` Jonathan Cameron
2024-09-08 19:04 ` Alex Lanzano
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=20240907164743.1cb7070e@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jagathjog1996@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lanzano.alex@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=ramona.bolboaca13@gmail.com \
--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