From: Axel Haslam <ahaslam@baylibre.com>
To: broonie@kernel.org, lgirdwood@gmail.com, khilman@baylibre.com,
nsekhar@ti.com, david@lechnology.com, robh+dt@kernel.org
Cc: linux-kernel@vger.kernel.org, Axel Haslam <ahaslam@baylibre.com>,
devicetree@vger.kernel.org
Subject: [PATCH/RFC v2 2/3] regulator: fixed: dt: Allow an optional over current pin
Date: Thu, 3 Nov 2016 12:11:43 +0100 [thread overview]
Message-ID: <20161103111144.511-3-ahaslam@baylibre.com> (raw)
In-Reply-To: <20161103111144.511-1-ahaslam@baylibre.com>
Add support for an optional over current input pin which
can be used to send an over current event to the regulator
consumer.
Cc: devicetree@vger.kernel.org
Signed-off-by: Axel Haslam <ahaslam@baylibre.com>
---
Documentation/devicetree/bindings/regulator/fixed-regulator.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/regulator/fixed-regulator.txt b/Documentation/devicetree/bindings/regulator/fixed-regulator.txt
index 4fae41d..b145abb 100644
--- a/Documentation/devicetree/bindings/regulator/fixed-regulator.txt
+++ b/Documentation/devicetree/bindings/regulator/fixed-regulator.txt
@@ -11,6 +11,7 @@ If this property is missing, the default assumed is Active low.
- gpio-open-drain: GPIO is open drain type.
If this property is missing then default assumption is false.
-vin-supply: Input supply name.
+- over-current-gpios: Input gpio that signal an over current condition.
Any property defined as part of the core regulator
binding, defined in regulator.txt, can also be used.
@@ -26,6 +27,7 @@ Example:
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <1800000>;
gpio = <&gpio1 16 0>;
+ over-current-gpios = <&gpio1 18 0>;
startup-delay-us = <70000>;
enable-active-high;
regulator-boot-on;
--
2.10.1
next prev parent reply other threads:[~2016-11-03 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 11:11 [PATCH/RFC v2 0/3] regulator: handling of error conditions for usb drivers Axel Haslam
2016-11-03 11:11 ` [PATCH/RFC v2 1/3] regulator: core: Add new API to poll for error conditions Axel Haslam
2016-11-04 18:16 ` Applied "regulator: core: Add new API to poll for error conditions" to the regulator tree Mark Brown
2016-11-03 11:11 ` Axel Haslam [this message]
2016-11-03 11:11 ` [PATCH/RFC v2 3/3] regulator: fixed: Handle optional overcurrent pin Axel Haslam
2016-11-04 18:20 ` Mark Brown
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=20161103111144.511-3-ahaslam@baylibre.com \
--to=ahaslam@baylibre.com \
--cc=broonie@kernel.org \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.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).