From: sashiko-bot@kernel.org
To: "Bhargav Joshi" <j.bhargav.u@gmail.com>
Cc: lee@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, mfd@lists.linux.dev
Subject: Re: [PATCH v2 2/4] regulator: dt-bindings: nvidia,tegra-regulators-coupling: Convert to DT schema
Date: Wed, 16 Sep 2026 13:23:50 +0000 [thread overview]
Message-ID: <20260916132350.DEA431F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260916-ti-tps6586x-v2-2-f12cfdfb446c@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] regulator: dt-bindings: merged headers and missing spaces in description
--
commit c698037c054c9372f8a8e2ee437ab89f8f0611c7
Author: Bhargav Joshi <j.bhargav.u@gmail.com>
regulator: dt-bindings: nvidia,tegra-regulators-coupling: Convert to DT schema
Convert NVIDIA Tegra Regulators Coupling from legacy text to DT schema.
Set additionalProperties true as this is shared schema.
> 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
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/nvidia,tegra-regulators-coupling.yaml
> @@ -0,0 +1,76 @@
[ ... ]
> +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
[Severity: Low]
Could the formatting in this description be adjusted to better reflect the
original text binding?
Currently, the old section headers like "Tegra20 voltage coupling" and
"Tegra30 voltage coupling" are merged directly into the sentences, creating
awkward phrasing like "Tegra20 voltage coupling On Tegra20 SoC's".
Additionally, is it possible to add a space after "regulators:" in both the
Tegra20 and Tegra30 paragraphs to improve readability?
> + 300mV from each other and CORE voltage shall be higher than the CPU by N mV,
> + where N depends on the CPU voltage.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260916-ti-tps6586x-v2-0-f12cfdfb446c@gmail.com?part=2
next prev parent reply other threads:[~2026-09-16 13:23 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 [this message]
2026-09-18 19:06 ` Rob Herring
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=20260916132350.DEA431F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j.bhargav.u@gmail.com \
--cc=lee@kernel.org \
--cc=mfd@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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