From: Gokhan Celik <gokhan.celik@analog.com>
To: <outreachy@lists.linux.dev>
Cc: Gokhan Celik <gokhan.celik@analog.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Gokhan Celik <Gokhan.Celik@analog.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: [PATCH 2/2] dt-bindings: regulator: Add MAX77503 regulator bindings
Date: Mon, 21 Aug 2023 19:28:22 +0300 [thread overview]
Message-ID: <50b983f2eb74aab5947cf7721770983b51ffd949.1692634090.git.gokhan.celik@analog.com> (raw)
In-Reply-To: <cover.1692634090.git.gokhan.celik@analog.com>
Add bindings for MAX77503 buck converter.
Signed-off-by: Gokhan Celik <gokhan.celik@analog.com>
---
.../regulator/adi,max77503-regulator.yaml | 64 +++++++++++++++++++
1 file changed, 64 insertions(+)
create mode 100644 Documentation/devicetree/bindings/regulator/adi,max77503-regulator.yaml
diff --git a/Documentation/devicetree/bindings/regulator/adi,max77503-regulator.yaml b/Documentation/devicetree/bindings/regulator/adi,max77503-regulator.yaml
new file mode 100644
index 000000000000..0d351225e107
--- /dev/null
+++ b/Documentation/devicetree/bindings/regulator/adi,max77503-regulator.yaml
@@ -0,0 +1,64 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+# Copyright (c) 2023 Analog Devices, Inc.
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/regulator/adi,max77503-regulator.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Analog Devices MAX77503 Buck Converter
+
+maintainers:
+ - Gokhan Celik <Gokhan.Celik@analog.com>
+
+description: Analog Devices MAX77503 Buck Converter
+
+properties:
+ compatible:
+ enum:
+ - adi,max77503
+
+ reg:
+ description: I2C address of the device
+ items:
+ - enum: [0x1e, 0x24, 0x37]
+
+ regulator:
+ type: object
+ $ref: regulator.yaml#
+ additionalProperties: false
+ description: |
+ Buck regulator
+
+ properties:
+ regulator-name: true
+ regulator-always-on: true
+ regulator-boot-on: true
+ regulator-min-microvolt:
+ minimum: 800000
+ regulator-max-microvolt:
+ maximum: 5000000
+
+additionalProperties: false
+
+required:
+ - compatible
+ - reg
+
+examples:
+ - |
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ max77503@1e {
+ compatible = "adi,max77503";
+ reg = <0x1e>;
+ regulator{
+ regulator-name = "max777503-regulator";
+ regulator-min-microvolt = <800000>;
+ regulator-max-microvolt = <5000000>;
+ regulator-boot-on;
+ };
+ };
+ };
+
--
2.34.1
next prev parent reply other threads:[~2023-08-21 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 16:28 [PATCH 0/2] drivers: regulator: Add MAX77503 regulator driver and bindings Gokhan Celik
2023-08-21 16:28 ` [PATCH 1/2] drivers: regulator: Add MAX77503 regulator driver Gokhan Celik
2023-08-21 18:41 ` Krzysztof Kozlowski
2023-08-21 16:28 ` Gokhan Celik [this message]
2023-08-21 18:41 ` [PATCH 2/2] dt-bindings: regulator: Add MAX77503 regulator bindings Krzysztof Kozlowski
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=50b983f2eb74aab5947cf7721770983b51ffd949.1692634090.git.gokhan.celik@analog.com \
--to=gokhan.celik@analog.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--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).