From: Nicolin Chen <nicoleotsuka@gmail.com>
To: jdelvare@suse.com, linux@roeck-us.net, robh+dt@kernel.org,
mark.rutland@arm.com, corbet@lwn.net
Cc: afd@ti.com, linux-hwmon@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: [PATCH v3 0/2] Add an initial DT binding doc for ina3221
Date: Fri, 21 Sep 2018 15:32:14 -0700 [thread overview]
Message-ID: <20180921223216.634-1-nicoleotsuka@gmail.com> (raw)
This series adds a initial DT binding doc for ina3221. It defines
a child node to describe the input source of each ina3221 channel.
Then it changes the driver to handle the information properly.
Changelog
v2->v3:
* Fixed two places in DT bindings (PATCH-1)
v1->v2:
* Redefined DT bindings (detail in PATCH-1)
* Changed the driver code accordingly (detail in PATCH-2)
Nicolin Chen (2):
dt-bindings: hwmon: Add ina3221 documentation
hwmon: ina3221: Read channel input source info from DT
.../devicetree/bindings/hwmon/ina3221.txt | 38 ++++++
Documentation/hwmon/ina3221 | 1 +
drivers/hwmon/ina3221.c | 126 ++++++++++++++++--
3 files changed, 155 insertions(+), 10 deletions(-)
create mode 100644 Documentation/devicetree/bindings/hwmon/ina3221.txt
--
2.17.1
next reply other threads:[~2018-09-21 22:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 22:32 Nicolin Chen [this message]
2018-09-21 22:32 ` [PATCH v3 1/2] dt-bindings: hwmon: Add ina3221 documentation Nicolin Chen
2018-09-22 12:38 ` Guenter Roeck
2018-09-22 18:03 ` Nicolin Chen
2018-09-22 23:56 ` Guenter Roeck
2018-09-21 22:32 ` [PATCH v3 2/2] hwmon: ina3221: Read channel input source info from DT Nicolin Chen
2018-09-22 12:50 ` Guenter Roeck
2018-09-22 18:46 ` Nicolin Chen
2018-09-22 23:59 ` Guenter Roeck
2018-09-23 0:38 ` Nicolin Chen
2018-09-23 0:50 ` Nicolin Chen
2018-09-23 2:07 ` Guenter Roeck
2018-09-23 3:33 ` Nicolin Chen
2018-09-23 3:39 ` Nicolin Chen
2018-09-23 5:25 ` 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=20180921223216.634-1-nicoleotsuka@gmail.com \
--to=nicoleotsuka@gmail.com \
--cc=afd@ti.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--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=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).