From: Rob Herring <robh@kernel.org>
To: Nathan Rossi <nathan@nathanrossi.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
devicetree@vger.kernel.org, Nathan Rossi <nathan.rossi@digi.com>,
linux-hwmon@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, Jean Delvare <jdelvare@suse.com>
Subject: Re: [PATCH v4 2/3] dt-bindings: hwmon: ti,ina2xx: Add ti,shunt-gain property
Date: Tue, 2 Nov 2021 12:36:07 -0500 [thread overview]
Message-ID: <YYF3B+ztZ5uJMEuP@robh.at.kernel.org> (raw)
In-Reply-To: <20211102052754.817220-2-nathan@nathanrossi.com>
On Tue, 02 Nov 2021 05:27:54 +0000, Nathan Rossi wrote:
> From: Nathan Rossi <nathan.rossi@digi.com>
>
> Add a property to the binding to define the selected shunt voltage gain.
> This specifies the range and accuracy that applies to the shunt circuit.
> This property only applies to devices that have a selectable shunt
> voltage range via PGA or ADCRANGE register configuration.
>
> Signed-off-by: Nathan Rossi <nathan.rossi@digi.com>
> ---
> Changes in v2:
> - Added binding for shunt-gain
>
> Changes in v3:
> - Fix schema error, setting $ref to uint32
> - Improve the description to detail exactly how to define the property
> and how the property affects initial device configuration and
> calculation of values
> ---
> .../devicetree/bindings/hwmon/ti,ina2xx.yaml | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-11-02 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 5:27 [PATCH v4 0/3] Driver for TI INA238 I2C Power Monitor Nathan Rossi
2021-11-02 5:27 ` [PATCH v4 1/3] dt-bindings: hwmon: ti,ina2xx: Document ti,ina238 compatible string Nathan Rossi
2021-11-02 17:37 ` Rob Herring
2021-11-09 20:31 ` Guenter Roeck
2021-11-02 5:27 ` [PATCH v4 2/3] dt-bindings: hwmon: ti,ina2xx: Add ti,shunt-gain property Nathan Rossi
2021-11-02 17:36 ` Rob Herring [this message]
2021-11-09 20:32 ` Guenter Roeck
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=YYF3B+ztZ5uJMEuP@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nathan.rossi@digi.com \
--cc=nathan@nathanrossi.com \
--cc=robh+dt@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).