From: Zev Weiss <zev@bewilderbeest.net>
To: Rob Herring <robh+dt@kernel.org>, devicetree@vger.kernel.org
Cc: Zev Weiss <zev@bewilderbeest.net>,
openbmc@lists.ozlabs.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>, Arnd Bergmann <arnd@arndb.de>,
linux-hwmon@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: [PATCH 3/4] dt-bindings: Add power-efuse binding
Date: Thu, 17 Feb 2022 02:44:43 -0800 [thread overview]
Message-ID: <20220217104444.7695-4-zev@bewilderbeest.net> (raw)
In-Reply-To: <20220217104444.7695-1-zev@bewilderbeest.net>
This can be used to describe a power output supplied by a regulator
device that the system controls.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
---
.../devicetree/bindings/misc/power-efuse.yaml | 37 +++++++++++++++++++
1 file changed, 37 insertions(+)
create mode 100644 Documentation/devicetree/bindings/misc/power-efuse.yaml
diff --git a/Documentation/devicetree/bindings/misc/power-efuse.yaml b/Documentation/devicetree/bindings/misc/power-efuse.yaml
new file mode 100644
index 000000000000..cadce15d2ce7
--- /dev/null
+++ b/Documentation/devicetree/bindings/misc/power-efuse.yaml
@@ -0,0 +1,37 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/misc/power-efuse.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Generic power efuse device
+
+maintainers:
+ - Zev Weiss <zev@bewilderbeest.net>
+
+properties:
+ compatible:
+ const: power-efuse
+
+ vout-supply:
+ description:
+ phandle to the regulator providing power for the efuse
+
+ error-flags-cache-ttl-ms:
+ description:
+ The number of milliseconds the vout-supply regulator's error
+ flags should be cached before re-fetching them.
+
+required:
+ - compatible
+ - vout-supply
+
+additionalProperties: false
+
+examples:
+ - |
+ efuse {
+ compatible = "power-efuse";
+ vout-supply = <&efuse_reg>;
+ error-flags-cache-ttl-ms = <500>;
+ };
--
2.35.1
next prev parent reply other threads:[~2022-02-17 10:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 10:44 [PATCH 0/4] misc: Add power-efuse driver Zev Weiss
2022-02-17 10:44 ` [PATCH 1/4] hwmon: (pmbus) Add get_error_flags support to regulator ops Zev Weiss
2022-02-17 18:11 ` Guenter Roeck
2022-02-17 23:37 ` Zev Weiss
2022-02-18 0:02 ` Guenter Roeck
2022-02-18 0:23 ` Zev Weiss
2022-02-17 10:44 ` [PATCH 2/4] hwmon: (pmbus) lm25066: Add regulator support Zev Weiss
2022-02-17 10:44 ` Zev Weiss [this message]
2022-02-17 16:39 ` [PATCH 3/4] dt-bindings: Add power-efuse binding Rob Herring
2022-02-17 22:35 ` Rob Herring
2022-02-18 0:17 ` Zev Weiss
2022-02-17 10:44 ` [PATCH 4/4] misc: Add power-efuse driver Zev Weiss
2022-02-17 13:34 ` Greg Kroah-Hartman
2022-02-17 22:53 ` Zev Weiss
2022-02-17 18:14 ` [PATCH 0/4] " 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=20220217104444.7695-4-zev@bewilderbeest.net \
--to=zev@bewilderbeest.net \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.com \
--cc=lgirdwood@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=openbmc@lists.ozlabs.org \
--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).