From: Lucas Stankus <lucas.p.stankus@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
gregkh@linuxfoundation.org, linux-iio@vger.kernel.org,
linux-staging@lists.linux.dev,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: staging: iio: cdc: ad7746: add binding documentation for AD7746
Date: Thu, 22 Apr 2021 16:16:21 -0300 [thread overview]
Message-ID: <CACKVXZDtUync4HnScJnMEj=Gh7bukUUpnPrtE0w1PPgCZOHORg@mail.gmail.com> (raw)
In-Reply-To: <20210420193746.GA3632576@robh.at.kernel.org>
On Tue, Apr 20, 2021 at 4:37 PM Rob Herring <robh@kernel.org> wrote:
>
> On Sun, Apr 18, 2021 at 07:49:51PM -0300, Lucas Stankus wrote:
> > Add device tree binding documentation for AD7746 cdc in YAML format.
> >
> > Signed-off-by: Lucas Stankus <lucas.p.stankus@gmail.com>
> > ---
> >
> > A minor note about the adi,excitation-vdd-permille property. Jonathan
> > suggested the name to be adi,excitation-vdd-milicent, but I was unsure of
> > the milicent naming. With a quick search I found out that the common way to
> > call a thousandth is 'per mille'[1], but I didn't find any use of it in the
> > kernel documentation. Any thoughts about it?
>
> Seems okay to me.
>
> > [1] https://en.wikipedia.org/wiki/Per_mille
> >
> > .../bindings/iio/cdc/adi,ad7746.yaml | 73 +++++++++++++++++++
> > 1 file changed, 73 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/iio/cdc/adi,ad7746.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/iio/cdc/adi,ad7746.yaml b/Documentation/devicetree/bindings/iio/cdc/adi,ad7746.yaml
> > new file mode 100644
> > index 000000000000..a2a7eee674ba
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/iio/cdc/adi,ad7746.yaml
> > @@ -0,0 +1,73 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/iio/cdc/adi,ad7746.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: AD7746 24-Bit Capacitance-to-Digital Converter with Temperature Sensor
> > +
> > +maintainers:
> > + - Michael Hennerich <michael.hennerich@analog.com>
> > +
> > +description: |
> > + AD7746 24-Bit Capacitance-to-Digital Converter with Temperature Sensor
> > +
> > + Specifications about the part can be found at:
> > + https://www.analog.com/media/en/technical-documentation/data-sheets/ad7291.pdf
> > +
> > +properties:
> > + compatible:
> > + enum:
> > + - adi,ad7745
> > + - adi,ad7746
> > + - adi,ad7747
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + adi,excitation-vdd-permille:
> > + description: |
> > + Set VDD per mille to be used as the excitation voltage.
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + enum: [125, 250, 375, 500]
> > +
> > + adi,exca-output-en:
> > + description: Enables the EXCA pin as the excitation output.
> > + type: boolean
> > +
> > + adi,exca-output-invert:
> > + description: Inverts the excitation output in the EXCA pin.
> > + type: boolean
>
> 'invert' assumes I know what the non-inverted signal is. Sometimes that
> makes sense, but if you can define in terms of the inverse that would be
> better. For example, for a normally active low signal, name the property
> 'foo-active-high'.
Thanks for the feedback!
From reading the data sheet I couldn't quite grasp what would be an inverted
excitation output, but I don't have a lot of experience with CDCs. Maybe someone
with more experience could help out with a better suggestion.
>
> > +
> > + adi,excb-output-en:
> > + description: Enables the EXCB pin as the excitation output.
> > + type: boolean
> > +
> > + adi,excb-output-invert:
> > + description: Inverts the excitation output in the EXCB pin.
> > + type: boolean
> > +
> > +required:
> > + - compatible
> > + - reg
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + i2c {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + ad7746: cdc@48 {
> > + compatible = "adi,ad7746";
> > + reg = <0x48>;
> > + adi,excitation-vdd-permille = <125>;
> > +
> > + adi,exca-output-en;
> > + adi,exca-output-invert;
> > + adi,excb-output-en;
> > + adi,excb-output-invert;
> > + };
> > + };
> > +...
> > --
> > 2.31.1
> >
next prev parent reply other threads:[~2021-04-22 19:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 22:49 [PATCH v2 0/2] staging: iio: cdc: ad7746: add dt properties for capacitive channel setup Lucas Stankus
2021-04-18 22:49 ` [PATCH v2 1/2] dt-bindings: staging: iio: cdc: ad7746: add binding documentation for AD7746 Lucas Stankus
2021-04-20 19:37 ` Rob Herring
2021-04-22 19:16 ` Lucas Stankus [this message]
2021-04-22 20:56 ` Lars-Peter Clausen
2021-04-24 12:00 ` Jonathan Cameron
2021-04-24 11:54 ` Jonathan Cameron
2021-04-18 22:50 ` [PATCH v2 2/2] staging: iio: cdc: ad7746: use dt for capacitive channel setup Lucas Stankus
2021-04-24 12:11 ` Jonathan Cameron
2021-04-26 0:54 ` Lucas Stankus
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='CACKVXZDtUync4HnScJnMEj=Gh7bukUUpnPrtE0w1PPgCZOHORg@mail.gmail.com' \
--to=lucas.p.stankus@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).