From: Bhargav Joshi <j.bhargav.u@gmail.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@avionic-design.de>,
Lee Jones <lee@kernel.org>,
Shree Ramamoorthy <s-ramamoorthy@ti.com>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Dmitry Osipenko <digetx@gmail.com>,
Svyatoslav Ryhel <clamor95@gmail.com>,
Laxman Dewangan <ldewangan@nvidia.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
goledhruva@gmail.com, m-chawdhry@ti.com,
daniel.baluta@gmail.com, simona.toaca@nxp.com,
j.bhargav.u@gmail.com, mfd@lists.linux.dev,
Thierry Reding <treding@nvidia.com>,
linux-tegra@vger.kernel.org
Subject: [PATCH v2 2/4] regulator: dt-bindings: nvidia,tegra-regulators-coupling: Convert to DT schema
Date: Wed, 16 Sep 2026 18:41:27 +0530 [thread overview]
Message-ID: <20260916-ti-tps6586x-v2-2-f12cfdfb446c@gmail.com> (raw)
In-Reply-To: <20260916-ti-tps6586x-v2-0-f12cfdfb446c@gmail.com>
Convert NVIDIA Tegra Regulators Coupling from legacy text to DT schema.
Set additionalProperties true as this is shared schema.
Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
---
.../regulator/nvidia,tegra-regulators-coupling.txt | 65 ------------------
.../nvidia,tegra-regulators-coupling.yaml | 76 ++++++++++++++++++++++
2 files changed, 76 insertions(+), 65 deletions(-)
diff --git a/Documentation/devicetree/bindings/regulator/nvidia,tegra-regulators-coupling.txt b/Documentation/devicetree/bindings/regulator/nvidia,tegra-regulators-coupling.txt
deleted file mode 100644
index 4bf2dbf7c6cc..000000000000
--- a/Documentation/devicetree/bindings/regulator/nvidia,tegra-regulators-coupling.txt
+++ /dev/null
@@ -1,65 +0,0 @@
-NVIDIA Tegra Regulators Coupling
-================================
-
-NVIDIA Tegra SoC's have a mandatory voltage-coupling between regulators.
-Thus on Tegra20 there are 3 coupled regulators and on NVIDIA Tegra30
-there are 2.
-
-Tegra20 voltage coupling
-------------------------
-
-On Tegra20 SoC's there are 3 coupled regulators: CORE, RTC and CPU.
-The CORE and RTC voltages shall be in a range of 170mV from each other
-and they both shall be higher than the CPU voltage by at least 120mV.
-
-Tegra30 voltage coupling
-------------------------
-
-On Tegra30 SoC's there are 2 coupled regulators: CORE and CPU. The CORE
-and CPU voltages shall be in a range of 300mV from each other and CORE
-voltage shall be higher than the CPU by N mV, where N depends on the CPU
-voltage.
-
-Required properties:
-- nvidia,tegra-core-regulator: Boolean property that designates regulator
- as the "Core domain" voltage regulator.
-- nvidia,tegra-rtc-regulator: Boolean property that designates regulator
- as the "RTC domain" voltage regulator.
-- nvidia,tegra-cpu-regulator: Boolean property that designates regulator
- as the "CPU domain" voltage regulator.
-
-Example:
-
- pmic {
- regulators {
- core_vdd_reg: core {
- regulator-name = "vdd_core";
- regulator-min-microvolt = <950000>;
- regulator-max-microvolt = <1300000>;
- regulator-coupled-with = <&rtc_vdd_reg &cpu_vdd_reg>;
- regulator-coupled-max-spread = <170000 550000>;
-
- nvidia,tegra-core-regulator;
- };
-
- rtc_vdd_reg: rtc {
- regulator-name = "vdd_rtc";
- regulator-min-microvolt = <950000>;
- regulator-max-microvolt = <1300000>;
- regulator-coupled-with = <&core_vdd_reg &cpu_vdd_reg>;
- regulator-coupled-max-spread = <170000 550000>;
-
- nvidia,tegra-rtc-regulator;
- };
-
- cpu_vdd_reg: cpu {
- regulator-name = "vdd_cpu";
- regulator-min-microvolt = <750000>;
- regulator-max-microvolt = <1125000>;
- regulator-coupled-with = <&core_vdd_reg &rtc_vdd_reg>;
- regulator-coupled-max-spread = <550000 550000>;
-
- nvidia,tegra-cpu-regulator;
- };
- };
- };
diff --git a/Documentation/devicetree/bindings/regulator/nvidia,tegra-regulators-coupling.yaml b/Documentation/devicetree/bindings/regulator/nvidia,tegra-regulators-coupling.yaml
new file mode 100644
index 000000000000..248cc98b6af1
--- /dev/null
+++ b/Documentation/devicetree/bindings/regulator/nvidia,tegra-regulators-coupling.yaml
@@ -0,0 +1,76 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/regulator/nvidia,tegra-regulators-coupling.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: NVIDIA Tegra Regulators Coupling
+
+description:
+ NVIDIA Tegra SoC's have a mandatory voltage-coupling between regulators. Thus
+ on Tegra20 there are 3 coupled regulators and on NVIDIA Tegra30 there are 2.
+
+ Tegra20 voltage coupling On Tegra20 SoC's - there are 3 coupled
+ regulators:CORE, RTC and CPU. The CORE and RTC voltages shall be in a range
+ of 170mV from each other and they both shall be higher than the CPU voltage
+ by at least 120mV.
+
+ Tegra30 voltage coupling On Tegra30 SoC's - there are 2 coupled
+ regulators:CORE and CPU. The CORE and CPU voltages shall be in a range of
+ 300mV from each other and CORE voltage shall be higher than the CPU by N mV,
+ where N depends on the CPU voltage.
+
+maintainers:
+ - Dmitry Osipenko <digetx@gmail.com>
+ - Thierry Reding <treding@nvidia.com>
+
+properties:
+ nvidia,tegra-core-regulator:
+ description: designates regulator as the "Core domain" voltage regulator.
+ type: boolean
+
+ nvidia,tegra-rtc-regulator:
+ description: designates regulator as the "RTC domain" voltage regulator.
+ type: boolean
+
+ nvidia,tegra-cpu-regulator:
+ description: designates regulator as the "CPU domain" voltage regulator.
+ type: boolean
+
+additionalProperties: true
+
+examples:
+ - |
+ pmic {
+ regulators {
+ core_vdd_reg: core {
+ regulator-name = "vdd_core";
+ regulator-min-microvolt = <950000>;
+ regulator-max-microvolt = <1300000>;
+ regulator-coupled-with = <&rtc_vdd_reg &cpu_vdd_reg>;
+ regulator-coupled-max-spread = <170000 550000>;
+
+ nvidia,tegra-core-regulator;
+ };
+
+ rtc_vdd_reg: rtc {
+ regulator-name = "vdd_rtc";
+ regulator-min-microvolt = <950000>;
+ regulator-max-microvolt = <1300000>;
+ regulator-coupled-with = <&core_vdd_reg &cpu_vdd_reg>;
+ regulator-coupled-max-spread = <170000 550000>;
+
+ nvidia,tegra-rtc-regulator;
+ };
+
+ cpu_vdd_reg: cpu {
+ regulator-name = "vdd_cpu";
+ regulator-min-microvolt = <750000>;
+ regulator-max-microvolt = <1125000>;
+ regulator-coupled-with = <&core_vdd_reg &rtc_vdd_reg>;
+ regulator-coupled-max-spread = <550000 550000>;
+
+ nvidia,tegra-cpu-regulator;
+ };
+ };
+ };
--
2.55.0
next prev parent reply other threads:[~2026-09-16 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 13:11 [PATCH v2 0/4] regulator: dt-bindings: Tegra coupling DT conversions and cleanup Bhargav Joshi
2026-09-16 13:11 ` [PATCH v2 1/4] dt-bindings: mfd: ti,tps65910: Add wakeup-source and GPIO hogs Bhargav Joshi
2026-09-18 19:09 ` Rob Herring (Arm)
2026-09-16 13:11 ` Bhargav Joshi [this message]
2026-09-18 19:06 ` [PATCH v2 2/4] regulator: dt-bindings: nvidia,tegra-regulators-coupling: Convert to DT schema Rob Herring
2026-09-16 13:11 ` [PATCH v2 3/4] regulator: dt-bindings: Reference Tegra regulator coupling schema Bhargav Joshi
2026-09-18 19:06 ` Rob Herring
2026-09-16 13:11 ` [PATCH v2 4/4] regulator: dt-bindings: ti,tps6586x: Convert to DT schema Bhargav Joshi
2026-09-18 19:08 ` 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=20260916-ti-tps6586x-v2-2-f12cfdfb446c@gmail.com \
--to=j.bhargav.u@gmail.com \
--cc=broonie@kernel.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=goledhruva@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=mfd@lists.linux.dev \
--cc=robh@kernel.org \
--cc=s-ramamoorthy@ti.com \
--cc=simona.toaca@nxp.com \
--cc=thierry.reding@avionic-design.de \
--cc=thierry.reding@kernel.org \
--cc=treding@nvidia.com \
/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®