From: Rob Herring <robh@kernel.org>
To: Bhargav Joshi <j.bhargav.u@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@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>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
goledhruva@gmail.com, m-chawdhry@ti.com, daniel.baluta@gmail.com,
simona.toaca@nxp.com, mfd@lists.linux.dev,
Thierry Reding <treding@nvidia.com>,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 2/4] regulator: dt-bindings: nvidia,tegra-regulators-coupling: Convert to DT schema
Date: Fri, 18 Sep 2026 14:06:05 -0500 [thread overview]
Message-ID: <20260918190605.GA1426069-robh@kernel.org> (raw)
In-Reply-To: <20260916-ti-tps6586x-v2-2-f12cfdfb446c@gmail.com>
On Wed, Sep 16, 2026 at 06:41:27PM +0530, Bhargav Joshi wrote:
> 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.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:
Separate paragraphs need '>'
> + 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.
> +
next prev parent reply other threads:[~2026-09-18 19:06 UTC|newest]
Thread overview: 14+ 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-16 13:18 ` sashiko-bot
2026-09-18 19:09 ` Rob Herring (Arm)
2026-09-16 13:11 ` [PATCH v2 2/4] regulator: dt-bindings: nvidia,tegra-regulators-coupling: Convert to DT schema Bhargav Joshi
2026-09-16 13:23 ` sashiko-bot
2026-09-18 19:06 ` Rob Herring [this message]
2026-09-16 13:11 ` [PATCH v2 3/4] regulator: dt-bindings: Reference Tegra regulator coupling schema Bhargav Joshi
2026-09-16 13:20 ` sashiko-bot
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-16 13:21 ` sashiko-bot
2026-09-18 19:08 ` Rob Herring (Arm)
2026-10-01 22:59 ` Thierry Reding
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=20260918190605.GA1426069-robh@kernel.org \
--to=robh@kernel.org \
--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=j.bhargav.u@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.