From: Tom Levens <tom.levens@cern.ch>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Mike Looijmans <mike.looijmans@topic.nl>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hwmon@vger.kernel.org
Subject: [PATCH v3 2/3] hwmon: ltc2990: add devicetree binding
Date: Mon, 3 Jul 2017 06:28:59 +0200 [thread overview]
Message-ID: <1499056140-6064-2-git-send-email-tom.levens@cern.ch> (raw)
In-Reply-To: <1499056140-6064-1-git-send-email-tom.levens@cern.ch>
Add a devicetree binding for the ltc2990 hwmon driver.
Signed-off-by: Tom Levens <tom.levens@cern.ch>
---
.../devicetree/bindings/hwmon/ltc2990.txt | 36 ++++++++++++++++++++++
1 file changed, 36 insertions(+)
create mode 100644 Documentation/devicetree/bindings/hwmon/ltc2990.txt
diff --git a/Documentation/devicetree/bindings/hwmon/ltc2990.txt b/Documentation/devicetree/bindings/hwmon/ltc2990.txt
new file mode 100644
index 0000000..f92f540
--- /dev/null
+++ b/Documentation/devicetree/bindings/hwmon/ltc2990.txt
@@ -0,0 +1,36 @@
+ltc2990: Linear Technology LTC2990 power monitor
+
+Required properties:
+- compatible: Must be "lltc,ltc2990"
+- reg: I2C slave address
+- lltc,meas-mode:
+ An array of two integers for configuring the chip measurement mode.
+
+ The first integer defines the bits 2..0 in the control register. In all
+ cases the internal temperature and supply voltage are measured. In
+ addition the following input measurements are enabled per mode:
+
+ 0: V1, V2, TR2
+ 1: V1-V2, TR2
+ 2: V1-V2, V3, V4
+ 3: TR1, V3, V4
+ 4: TR1, V3-V4
+ 5: TR1, TR2
+ 6: V1-V2, V3-V4
+ 7: V1, V2, V3, V4
+
+ The second integer defines the bits 4..3 in the control register. This
+ allows a subset of the measurements to be enabled:
+
+ 0: Internal temperature and supply voltage only
+ 1: TR1, V1 or V1-V2 only per mode
+ 2: TR2, V3 or V3-V4 only per mode
+ 3: All measurements per mode
+
+Example:
+
+ltc2990@4c {
+ compatible = "lltc,ltc2990";
+ reg = <0x4c>;
+ lltc,meas-mode = <7 3>; /* V1, V2, V3, V4 */
+};
--
1.8.3.1
next prev parent reply other threads:[~2017-07-03 4:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 4:28 [PATCH v3 1/3] hwmon: ltc2990: refactor value conversion Tom Levens
2017-07-03 4:28 ` Tom Levens [this message]
2017-07-07 14:24 ` [PATCH v3 2/3] hwmon: ltc2990: add devicetree binding Rob Herring
2017-07-03 4:29 ` [PATCH v3 3/3] hwmon: ltc2990: support all measurement modes Tom Levens
[not found] ` <1499056140-6064-3-git-send-email-tom.levens-vJEk5272eHo@public.gmane.org>
2017-07-03 6:29 ` Mike Looijmans
[not found] ` <341b5c67-c013-5a7c-54b5-e8c2a7c168e7-Oq418RWZeHk@public.gmane.org>
2017-07-03 17:09 ` Guenter Roeck
2017-07-11 22:00 ` Tom Levens
2017-07-04 22:45 ` kbuild test robot
2017-07-08 15:45 ` [v3,1/3] hwmon: ltc2990: refactor value conversion Guenter Roeck
[not found] ` <20170708154515.GA6358-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2017-07-11 22:03 ` Tom Levens
2017-07-12 0:39 ` 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=1499056140-6064-2-git-send-email-tom.levens@cern.ch \
--to=tom.levens@cern.ch \
--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=mark.rutland@arm.com \
--cc=mike.looijmans@topic.nl \
--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).