From: Mikko Perttunen <mperttunen@nvidia.com>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Thierry Reding <treding@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: tegra: Add core supply for Tegra114 boards
Date: Wed, 30 Sep 2026 17:50:31 +0900 [thread overview]
Message-ID: <9C0coc-qQg-ICz_OVjO0Yg@nvidia.com> (raw)
In-Reply-To: <CAPVz0n02==Zq3sZvW3p_pPs7RUASvP0koWNjsAZY289gqnNxxw@mail.gmail.com>
On Wednesday, September 30, 2026 3:48 PM Svyatoslav Ryhel wrote:
> ср, 30 вер. 2026 р. о 07:11 Mikko Perttunen <mperttunen@nvidia.com> пише:
> >
> > After commit 4cc90d4c043e ("ARM: tegra: Configure Tegra114 power
> > domains"), a core-supply property is required in the PMC node.
> > Label the core regulator on Dalmore, NVIDIA SHIELD and Tegra Note 7
> > and add the property.
> >
> > Fixes: 4cc90d4c043e ("ARM: tegra: Configure Tegra114 power domains")
> > Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
> > ---
> > This skips TF701T since there is already a patch on the mailing list for
> > it. Tested on Dalmore, but not on TN7 or SHIELD Portable.
> > ---
> > arch/arm/boot/dts/nvidia/tegra114-dalmore.dts | 4 +++-
> > arch/arm/boot/dts/nvidia/tegra114-roth.dts | 4 +++-
> > arch/arm/boot/dts/nvidia/tegra114-tn7.dts | 4 +++-
> > 3 files changed, 9 insertions(+), 3 deletions(-)
> >
>
> Thank you for catching this!
>
> Tested-by: Svyatoslav Ryhel <clamor95@gmail.com> # Tegratab/TN7
> Reviewed-by: Svyatoslav Ryhel <clamor95@gmail.com>
Thanks for testing!
prev parent reply other threads:[~2026-09-30 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 4:11 Mikko Perttunen
2026-09-30 6:48 ` Svyatoslav Ryhel
2026-09-30 8:50 ` Mikko Perttunen [this message]
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=9C0coc-qQg-ICz_OVjO0Yg@nvidia.com \
--to=mperttunen@nvidia.com \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--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®