devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: robh@kernel.org
Cc: krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, Frank.Li@nxp.com,
	Fabio Estevam <festevam@gmail.com>
Subject: [PATCH v2] dt-bindings: arm: cpus: Document pu-supply
Date: Sun,  7 Sep 2025 12:25:13 -0300	[thread overview]
Message-ID: <20250907152513.590218-1-festevam@gmail.com> (raw)

The i.MX6Q Reference Manual describes the three digital LDO regulators
as follows:

"10.4.1.1.1
Digital LDO Regulators
The integrated PMU includes three digital LDO regulators: LDO_ARM, LDO_PU, and
LDO_SOC. These regulators provide power to the ARM_Core power domain, the
combined VPU, IPU and GPU power domain, and the rest of the SoC logic (except
always-ON SNVS domain)."

imx6dl.dtsi uses the correct names to describe these supplies:

arm-supply = <&reg_arm>;
pu-supply = <&reg_pu>;
soc-supply = <&reg_soc>;

'arm-supply' and 'soc-supply' are already documented, but 'pu-supply' is not.

Document the 'pu-supply' property and set it to deprecated.
    
This fixes the following dt-schema warning:
 
cpu@1 (arm,cortex-a9): Unevaluated properties are not allowed ('pu-supply' was unexpected)

Signed-off-by: Fabio Estevam <festevam@gmail.com>
---
Changes since v1:
- Explain that PU is a valid name. (Krzysztof)

 Documentation/devicetree/bindings/arm/cpus.yaml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/devicetree/bindings/arm/cpus.yaml b/Documentation/devicetree/bindings/arm/cpus.yaml
index 4f1906d9fa68..c8a72fd02530 100644
--- a/Documentation/devicetree/bindings/arm/cpus.yaml
+++ b/Documentation/devicetree/bindings/arm/cpus.yaml
@@ -350,6 +350,10 @@ properties:
     deprecated: true
     description: Use 'cpu-supply' instead
 
+  pu-supply:
+    deprecated: true
+    description: Only for i.MX6Q/DL/SL SoCs.
+
   soc-supply:
     deprecated: true
     description: Only for i.MX6/7 Soc.
-- 
2.34.1


             reply	other threads:[~2025-09-07 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07 15:25 Fabio Estevam [this message]
2025-09-08  7:58 ` [PATCH v2] dt-bindings: arm: cpus: Document pu-supply Krzysztof Kozlowski
2025-09-08 20:48 ` Frank Li
2025-09-09  0:24 ` Rob Herring (Arm)

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=20250907152513.590218-1-festevam@gmail.com \
    --to=festevam@gmail.com \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=robh@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).