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 v7 0/2] Add an initial DT binding doc for ina3221
Date: Thu, 27 Sep 2018 13:54:04 -0700 [thread overview]
Message-ID: <20180927205406.21932-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
v6->v7:
* Refined the example in the binding doc (PATCH-1)
v5->v6:
* Removed status property and merged examples (PATCH-1)
* Added in[123]_enable sysfs nodes (PATCH-2)
v4->v5:
* Changed two property names of child node (PATCH-1)
* Changed the driver accordingly and simplified is_visible (PATCH-2)
v3->v4:
* Fixed one place in child DT node bindings (PATCH-1)
* Changed the driver accordingly and added is_visible (PATCH-2)
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 | 44 ++++
Documentation/hwmon/ina3221 | 2 +
drivers/hwmon/ina3221.c | 237 ++++++++++++++++--
3 files changed, 269 insertions(+), 14 deletions(-)
create mode 100644 Documentation/devicetree/bindings/hwmon/ina3221.txt
--
2.17.1
next reply other threads:[~2018-09-27 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 20:54 Nicolin Chen [this message]
2018-09-27 20:54 ` [PATCH v7 1/2] dt-bindings: hwmon: Add ina3221 documentation Nicolin Chen
2018-09-27 20:54 ` [PATCH v7 2/2] hwmon: ina3221: Read channel input source info from DT Nicolin Chen
2018-09-27 22:06 ` Guenter Roeck
2018-09-27 22:11 ` Nicolin Chen
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=20180927205406.21932-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.