From: Rob Herring <robh@kernel.org>
To: Jacopo Mondi <jacopo+renesas@jmondi.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrea Merello <andrea.merello@gmail.com>,
Magnus Damm <magnus.damm@gmail.com>,
linux-iio@vger.kernel.org, linux-staging@lists.linux.dev,
Jacopo Mondi <jacopo@jmondi.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: staging: iio: imu: Document CEVA BNO08x
Date: Mon, 27 Jun 2022 16:25:22 -0600 [thread overview]
Message-ID: <20220627222522.GA3067718-robh@kernel.org> (raw)
In-Reply-To: <20220616100006.22045-2-jacopo+renesas@jmondi.org>
On Thu, Jun 16, 2022 at 12:00:05PM +0200, Jacopo Mondi wrote:
> From: Jacopo Mondi <jacopo@jmondi.org>
>
> Document CEVA BNO08x (080, 085 and 086) Sensor Hub.
>
> The BNO08X family (BNO080/85/86) is a System in Package (SiP) that
> integrates a triaxial accelerometer, triaxial gyroscope, magnetometer
> and a 32-bit ARM Cortex-M0+ microcontroller running CEVA's SH-2
> firmware.
>
> Datasheet:
> https://www.ceva-dsp.com/wp-content/uploads/2019/10/BNO080_085-Datasheet.pdf
>
> Signed-off-by: Jacopo Mondi <jacopo@jmondi.org>
> ---
> .../bindings/staging/iio/imu/ceva,bno08x.yaml | 63 +++++++++++++++++++
You expect this binding to change? If so, then why define the ABI. If
not, then why is it in staging? IOW, I don't really want additions to
bindings/staging/.
If this isn't in a .dts file and the driver isn't stable yet, then just
don't document it until it is.
> 1 file changed, 63 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/staging/iio/imu/ceva,bno08x.yaml
>
> diff --git a/Documentation/devicetree/bindings/staging/iio/imu/ceva,bno08x.yaml b/Documentation/devicetree/bindings/staging/iio/imu/ceva,bno08x.yaml
> new file mode 100644
> index 000000000000..f7d6ea6d9147
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/staging/iio/imu/ceva,bno08x.yaml
> @@ -0,0 +1,63 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/staging/iio/imu/ceva,bno08x.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: CEVA BNO080/85/86
> +
> +maintainers:
> + - Jacopo Mondi <jacopo@jmondi.org>
> +
> +description: |
> + CEVA BNO08x is a System in Package (SiP) that integrates a triaxial
> + accelerometer, triaxial gyroscope, magnetometer and a 32-bit ARM Cortex-M0+
> + microcontroller running CEVA's SH-2 firmware.
> +
> + The BNO08x family is documented at
> + https://www.ceva-dsp.com/product/bno080-085/
> + https://www.ceva-dsp.com/wp-content/uploads/2019/10/BNO080_085-Datasheet.pdf
> +
> + The SH-2 firmware reference is available at
> + https://cdn.sparkfun.com/assets/4/d/9/3/8/SH-2-Reference-Manual-v1.2.pdf
> + https://cdn.sparkfun.com/assets/7/6/9/3/c/Sensor-Hub-Transport-Protocol-v1.7.pdf
> +
> +properties:
> + compatible:
> + const: ceva,bno08x
Don't use wildcards in compatibles.
> +
> + reg:
> + maxItems: 1
> +
> + reset-gpios:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> + description:
> + Phandle to the GPIO connected to the chip H_INTN (Host Interrupt) pin.
> + The interrupt type shall be IRQ_TYPE_EDGE_FALLING.
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + bno080: imu@4b {
> + compatible = "ceva,bno08x";
> + interrupt-parent = <&gpio5>;
> + interrupts = <8 IRQ_TYPE_EDGE_FALLING>;
> + reg = <0x4b>;
> + };
> + };
> +
> --
> 2.35.1
>
>
prev parent reply other threads:[~2022-06-27 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220616100006.22045-1-jacopo+renesas@jmondi.org>
2022-06-16 10:00 ` [PATCH 1/2] dt-bindings: staging: iio: imu: Document CEVA BNO08x Jacopo Mondi
2022-06-27 22:25 ` Rob Herring [this message]
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=20220627222522.GA3067718-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrea.merello@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jacopo+renesas@jmondi.org \
--cc=jacopo@jmondi.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=magnus.damm@gmail.com \
/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).