From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org, soc@kernel.org
Cc: Jon Hunter <jonathanh@nvidia.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Aaron Kling <webgeek1234@gmail.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] Revert "arm64: tegra: Add interconnect properties for Tegra210"
Date: Thu, 18 Dec 2025 12:56:12 +0100 [thread overview]
Message-ID: <aUPrVFWKfFYmuwhB@orome> (raw)
In-Reply-To: <20251217104744.184153-1-jonathanh@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
On Wed, Dec 17, 2025 at 10:47:44AM +0000, Jon Hunter wrote:
> Commit 59a42707a094 ("arm64: tegra: Add interconnect properties for
> Tegra210") populated interconnect properties for Tegra210 and this is
> preventing the Tegra DRM driver from probing successfully. The following
> error is observed on boot ...
>
> drm drm: failed to initialize 54240000.dc: -517
>
> For now revert this change, until a fix is available.
>
> Fixes: 59a42707a094 ("arm64: tegra: Add interconnect properties for Tegra210")
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra210.dtsi | 24 ------------------------
> 1 file changed, 24 deletions(-)
Hi Arnd,
this is the only patch that I think we need in v6.19 for now, so do you
want me to send a PR or would you rather pick this up directly?
Here's a link to the patchwork for this, for convenience:
https://patchwork.ozlabs.org/project/linux-tegra/patch/20251217104744.184153-1-jonathanh@nvidia.com/
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-18 11:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 10:47 [PATCH] Revert "arm64: tegra: Add interconnect properties for Tegra210" Jon Hunter
2025-12-17 18:20 ` Aaron Kling
2025-12-17 20:42 ` Aaron Kling
2025-12-18 12:00 ` Thierry Reding
2025-12-18 19:07 ` Aaron Kling
2025-12-19 10:59 ` Jon Hunter
2025-12-19 18:03 ` Aaron Kling
2026-01-05 20:27 ` Nicolas Chauvet
2026-01-07 19:50 ` Aaron Kling
2026-01-08 15:53 ` Nicolas Chauvet
2025-12-18 11:56 ` Thierry Reding [this message]
2026-01-15 9:50 ` Jon Hunter
2026-01-15 16:41 ` Arnd Bergmann
2026-01-16 12:12 ` 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=aUPrVFWKfFYmuwhB@orome \
--to=thierry.reding@gmail.com \
--cc=arm@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=soc@kernel.org \
--cc=webgeek1234@gmail.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