From: Jonathan Cameron <jic23@kernel.org>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<dlechner@baylibre.com>, <nuno.sa@analog.com>, <andy@kernel.org>,
<manuel.stahl@iis.fraunhofer.de>, <~lkcamp/patches@lists.sr.ht>,
<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: iio: gyroscope: invensense,itg3200: add binding
Date: Sat, 31 May 2025 18:26:43 +0100 [thread overview]
Message-ID: <20250531182643.78a54688@jic23-huawei> (raw)
In-Reply-To: <20250530175649.000005d0@huawei.com>
On Fri, 30 May 2025 17:56:49 +0100
Jonathan Cameron <Jonathan.Cameron@huawei.com> wrote:
> On Tue, 27 May 2025 17:55:28 -0300
> Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com> wrote:
>
> > There is no txt file for it, add yaml for invensense,itg3200 gyroscope.
> >
> > Signed-off-by: Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com>
> > ---
> > Originally I`ve added @Jonathan as the binding maintainer due another thread
> > but @Krzysztof mentioned at v1: "...this should be someone interested in the hardware".
> > I`m not sure who might be this person in this case, a reasonable choice would be
> > the original author of the driver, but looks like his last patch is from a
> > long time ago [2] but I`ll ping here.
> >
> > Dear @Manuel Stahl, I`ve noticed that since the driver was added,
> > there was no binding doc for it and this is what this patch is addressing.
> > In this case, a maintainer ref is required inside the .yaml file and I would
> > like to ask if I can add you in this case.
> > I would appreciate your comment or suggestion over this topic.
>
> Manuel has not been active for quite a while. You never know though!
>
> Fall back to me if needed given I end up seeing all these changes anyway.
>
> I can make that change whilst applying.
>
Tweaked to change this and add the note from Krzysztof to the commit
message. Applied
Thanks,
Jonathan
> Jonathan
>
> >
> > Tks all and regards.
> >
> > Changelog:
> > v2:
> > - removed the register map link; there is no datasheet available at public ref. At [1],
> > it is just a product overview, so we can`t use it;
> > - add supplies and external clocks (I`ve used as ref iio/gyroscope/invensense,mpu3050.yaml);
> > - add the author of the driver as the maintainer of this file but I`m CC him in
> > order to get his opinion about it;
> > - adding some CC missing at v1;
> >
> > v1: https://lore.kernel.org/linux-devicetree/20250515002817.81863-1-rodrigo.gobbi.7@gmail.com/
> >
> > [1] https://invensense.tdk.com/products/motion-tracking/3-axis/itg-3200/
> > [2] https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/?qt=author&q=Manuel+Stahl
> > ---
> > .../iio/gyroscope/invensense,itg3200.yaml | 59 +++++++++++++++++++
> > 1 file changed, 59 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/iio/gyroscope/invensense,itg3200.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/iio/gyroscope/invensense,itg3200.yaml b/Documentation/devicetree/bindings/iio/gyroscope/invensense,itg3200.yaml
> > new file mode 100644
> > index 000000000000..4b2f9a57c6ea
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/iio/gyroscope/invensense,itg3200.yaml
> > @@ -0,0 +1,59 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/iio/gyroscope/invensense,itg3200.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Invensense ITG-3200 Gyroscope
> > +
> > +maintainers:
> > + - Manuel Stahl <manuel.stahl@iis.fraunhofer.de>
> > +
> > +description: |
> > + Triple-axis, digital output gyroscope with a three 16-bit analog-to-digital
> > + converters (ADCs) for digitizing the gyro outputs, a user-selectable internal
> > + low-pass filter bandwidth, and a Fast-Mode I2C.
> > +
> > +properties:
> > + compatible:
> > + const: invensense,itg3200
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + vdd-supply: true
> > +
> > + vlogic-supply: true
> > +
> > + interrupts:
> > + maxItems: 1
> > +
> > + mount-matrix:
> > + description: an optional 3x3 mounting rotation matrix.
> > +
> > + clocks:
> > + maxItems: 1
> > +
> > + clock-names:
> > + items:
> > + - const: ext_clock
> > +
> > +required:
> > + - compatible
> > + - reg
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/interrupt-controller/irq.h>
> > + i2c {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + gyroscope@68 {
> > + compatible = "invensense,itg3200";
> > + reg = <0x68>;
> > + interrupt-parent = <&gpio2>;
> > + interrupts = <24 IRQ_TYPE_EDGE_FALLING>;
> > + };
> > + };
>
prev parent reply other threads:[~2025-05-31 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 20:55 [PATCH v2] dt-bindings: iio: gyroscope: invensense,itg3200: add binding Rodrigo Gobbi
2025-05-28 6:22 ` Krzysztof Kozlowski
2025-05-30 16:56 ` Jonathan Cameron
2025-05-31 17:26 ` Jonathan Cameron [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=20250531182643.78a54688@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.stahl@iis.fraunhofer.de \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=rodrigo.gobbi.7@gmail.com \
--cc=~lkcamp/patches@lists.sr.ht \
/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