From: Eddie James <eajames@linux.ibm.com>
To: linux-hwmon@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
jdelvare@suse.com, linux@roeck-us.net, mark.rutland@arm.com,
robh+dt@kernel.org, Eddie James <eajames@linux.ibm.com>
Subject: [PATCH 1/2] dt-bindings: hwmon: Document ibm,cffps compatible string
Date: Wed, 9 Oct 2019 14:11:01 -0500 [thread overview]
Message-ID: <1570648262-25383-2-git-send-email-eajames@linux.ibm.com> (raw)
In-Reply-To: <1570648262-25383-1-git-send-email-eajames@linux.ibm.com>
Document this string that indicates that any version of the power supply
may be connected. In this case, the driver must detect the version
automatically.
Signed-off-by: Eddie James <eajames@linux.ibm.com>
---
Documentation/devicetree/bindings/hwmon/ibm,cffps1.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/hwmon/ibm,cffps1.txt b/Documentation/devicetree/bindings/hwmon/ibm,cffps1.txt
index 1036f65..d9a2719 100644
--- a/Documentation/devicetree/bindings/hwmon/ibm,cffps1.txt
+++ b/Documentation/devicetree/bindings/hwmon/ibm,cffps1.txt
@@ -5,6 +5,9 @@ Required properties:
- compatible : Must be one of the following:
"ibm,cffps1"
"ibm,cffps2"
+ or "ibm,cffps" if the system
+ must support any version of the
+ power supply
- reg = < I2C bus address >; : Address of the power supply on the
I2C bus.
--
1.8.3.1
next prev parent reply other threads:[~2019-10-09 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 19:11 [PATCH 0/2] hwmon: (pmbus/ibm-cffps) Add version detection capability Eddie James
2019-10-09 19:11 ` Eddie James [this message]
2019-10-15 22:32 ` [PATCH 1/2] dt-bindings: hwmon: Document ibm,cffps compatible string Rob Herring
2019-10-17 13:35 ` Guenter Roeck
2019-10-09 19:11 ` [PATCH 2/2] hwmon: (pmbus/ibm-cffps) Add version detection capability Eddie James
2019-10-17 13:36 ` 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=1570648262-25383-2-git-send-email-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--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=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).