From: "Andrew F. Davis" <afd@ti.com>
To: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Corbet <corbet@lwn.net>
Cc: devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Andrew
Subject: [PATCH v4 0/2] Add support for INA3221 Triple Current/Voltage Monitors
Date: Tue, 31 May 2016 13:37:09 -0500 [thread overview]
Message-ID: <20160531183711.9048-1-afd@ti.com> (raw)
Hello all,
This series adds support for the INA3221 Triple Current/Voltage Monitor.
Changes from v3:
- minor fixups from comments
- rebased on v4.7-rc1
Changes from v2:
- changed alarms to work on current
- added of_match_table
- other small fixups/typos
Changes from v1:
- rearranged and renumbered sysfs enteries
- added reading alert bits to sysfs
- removed internal power calculation
- added DT setting of shunt resistors
- various other minor fixups
Thanks,
Andrew
Andrew F. Davis (2):
hwmon: Define binding for the INA3221 hwmon driver
hwmon: Add support for INA3221 Triple Current/Voltage Monitors
.../devicetree/bindings/hwmon/ina3221.txt | 19 +
Documentation/hwmon/ina3221 | 35 ++
drivers/hwmon/Kconfig | 11 +
drivers/hwmon/Makefile | 1 +
drivers/hwmon/ina3221.c | 451 +++++++++++++++++++++
5 files changed, 517 insertions(+)
create mode 100644 Documentation/devicetree/bindings/hwmon/ina3221.txt
create mode 100644 Documentation/hwmon/ina3221
create mode 100644 drivers/hwmon/ina3221.c
--
2.8.3
next reply other threads:[~2016-05-31 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 18:37 Andrew F. Davis [this message]
2016-05-31 18:37 ` [PATCH v4 1/2] hwmon: Define binding for the INA3221 hwmon driver Andrew F. Davis
2016-05-31 18:37 ` [PATCH v4 2/2] hwmon: Add support for INA3221 Triple Current/Voltage Monitors Andrew F. Davis
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=20160531183711.9048-1-afd@ti.com \
--to=afd@ti.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.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).