From: "Rob Herring (Arm)" <robh@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Svyatoslav Ryhel <clamor95@gmail.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH] regulator: dt-bindings: Add MAX20024 sd4
Date: Tue, 22 Sep 2026 16:21:39 -0500 [thread overview]
Message-ID: <20260922212140.1118832-1-robh@kernel.org> (raw)
Allow the MAX20024 extra sd4 regulator and its in-sd4 supply in the
MAX77620 regulator schema. The other DCDC and LDO names remain
unchanged.
Assisted-by: LLM
Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
---
.../bindings/regulator/maxim,max77620-regulator.yaml | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/regulator/maxim,max77620-regulator.yaml b/Documentation/devicetree/bindings/regulator/maxim,max77620-regulator.yaml
index 7118c34961ba..0f2901cab8af 100644
--- a/Documentation/devicetree/bindings/regulator/maxim,max77620-regulator.yaml
+++ b/Documentation/devicetree/bindings/regulator/maxim,max77620-regulator.yaml
@@ -10,17 +10,17 @@ maintainers:
- Svyatoslav Ryhel <clamor95@gmail.com>
description:
- Device has multiple DCDC(sd[0-3]) and LDOs(ldo[0-8]). The input supply
- of these regulators are defined under parent device node. Details of
- regulator properties are defined as child node under sub-node "regulators"
- which is child node of device node.
+ Device has multiple DCDC (sd[0-3], plus sd4 on MAX20024) and LDOs
+ (ldo[0-8]). The input supply of these regulators are defined under parent
+ device node. Details of regulator properties are defined as child node under
+ sub-node "regulators" which is child node of device node.
patternProperties:
- "^in-(sd[0-3]|ldo(0-1|2|3-5|4-6|7-8))-supply$":
+ "^in-(sd[0-4]|ldo(0-1|2|3-5|4-6|7-8))-supply$":
$ref: /schemas/types.yaml#/definitions/phandle
description: Input supply for DCDC or LDO
- "^(sd[0-3]|ldo[0-8])$":
+ "^(sd[0-4]|ldo[0-8])$":
type: object
$ref: /schemas/regulator/regulator.yaml#
unevaluatedProperties: false
--
2.53.0
next reply other threads:[~2026-09-22 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 21:21 Rob Herring (Arm) [this message]
2026-09-23 9:01 ` Svyatoslav Ryhel
2026-09-23 11:58 ` 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=20260922212140.1118832-1-robh@kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®